Workaround to Attach Block and USB Devices to Win Qube(s) Under 4.2

[apparatus]

@tempmail

I think this is wrong path to follow. If things work under some terms, and under the other it doesn’t work, then it’s about the terms.

My setup:
Qubes OS 4.2 with latest current-testing dom0 updates and without any patched files (stubdom-rootfs/etc).
Windows 10 installed in a HVM qube with 4GiB memory and 4 VCPUs using the latest official MSDN WIndows 10 English image:

$ sha256sum en-us_windows_10_consumer_editions_version_22h2_updated_july_2024_x64_dvd_3245b006.iso 
2eda4701d3e4061eccfdf0ad264b69392e67e2a29fef9eb7d7a57150b08e87e0  en-us_windows_10_consumer_editions_version_22h2_updated_july_2024_x64_dvd_3245b006.iso

Windows 10 with latest updates installed and without any custom system config modifications or software installed.

@tempmail

Here, it’s all about Qubes 4.2, since everything worked under 4.1.

I disagree, because it works for me in Qubes OS 4.2 so I don’t see how this is Qubes OS 4.1 vs Qubes OS 4.2 issue.
Maybe there are some more issues that appeared in Qubes OS 4.2 that are not present in Qubes OS 4.1 but not the ones that we are talking about.

@tempmail

As @fsflover said on the other topic

@fsflover

… A high-quality guide must be verified at least by two independent users, perhaps with showing successful logs.

So, we saw no one but you your tips to work. The OP is still waiting another user to reproduce it, so it could be confirmed.

We can wait for more people to come and check it in their Qubes OS 4.2 then before trying to trace the issue further.