Strange routing in windows?

Question

Samba

Scheme - two laptops with Win10 connected to home Wi-Fi (say 192.168.0.0/24). It was necessary to download about 300GB of photos, and I stupidly connected the computers with a patch, registering ip in the network networks (say 10.10.10.1/30) without gateways . I went via SMB to a neighboring laptop (say, from 10.10.10.1 to 10.10.10.2) and began to merge data. After some time, I noticed that there was no speed (gig networks). I tried turning off Wi-Fi and the speed was as advertised. Subnets do not overlap.
Maybe someone has already encountered this and already has some kind of logical explanation for what is happening?
There are no screenshots, but the stand is not a problem to assemble.

Answer 1

It seems to me that SMB3 is to blame for everything. Obviously, all client Windows (7,8,10) can be SMB3 clients. Perhaps 10 can also be an SMB3 server. And SMB3 also includes such a feature as:
Perhaps, when there are several links and they are different in speed, then there are some difficulties in synchronizing these several transmission streams, and accordingly, the speed drops to the speed of the slowest of the channels.

Answer 2

I found a big clue. But first I'll tell you a fact - Windows can route "directly connected networks" through another network card. I repeated the stand, since there is a record of this action in the office.
In short, according to the old school, I included copper in a 100Mbps switch. Most likely, Windows saw that it was 100 Mbps on network cards, and 150 Mbps on wi-fi, and entered these values ​​somewhere, building a route through the air. Seeing a low speed, I tried to turn on the copper directly (without a switch), the LAN went up. The speed did not increase (2-4 Mbps), turning off wi-fi, Windows went along the normal route with a gigabit uplink.