Hi Bruce,
I have found a way to reproduce your example in a way that seems independent from backend and network speed:
rclone mount --network-mode --bwlimit=1M -vv myOneDrive:testfolder/ Z:
The test folder has this well-known content:
rclone.exe lsl OneDrive:testfolder/
2064016 2022-11-02 17:24:07.000000000 rclone-v1.60.0-windows-amd64/README.html
1698677 2022-11-02 17:24:07.000000000 rclone-v1.60.0-windows-amd64/README.txt
50587 2022-11-02 17:24:07.000000000 rclone-v1.60.0-windows-amd64/git-log.txt
1918740 2022-11-02 17:24:07.000000000 rclone-v1.60.0-windows-amd64/rclone.1
47669760 2022-11-02 17:24:07.000000000 rclone-v1.60.0-windows-amd64/rclone.exe
To reproduce, first open Explorer and select the "rclone-v1.60.0-windows-amd64" folder and press Enter. Then select an ordinary file in the listing while being careful not to hover the mouse over the line with rclone.exe. Then use the arrow keys to select rclone.exe and wait a few seconds, then I see a period of approximately 30 seconds where the cursor becomes busy and Explorer shows "Not Responding" on and off.
I am using Windows 11 without any fancy addons and can confirm that it doesn't help to turn off thumbnails or built-in antivirus. It does improve the experience to add --vfs-cachemode=full, but it still takes 30 seconds from selection before you can right-click without freezing Explorer. Seems like Windows insists on reading app. 15MB which causes rclone to toggle between reading the head and tail of the exe file (if I am reading the log correctly).
It puzzles me that Windows does this in --network-mode, so there may be an issue with rclone. I have not been able to find a way to verify that Windows indeed sees the mount as networked (that is possibly slow with high latency and drop outs).
Perhaps somebody with better insight can reproduce and shed some light on this.