Yuri Benditovich

@ddaney-fungible Sorry, by mistake I swapped them when read

Thank you for the report. I suspect that because the usbdk is defined as system service and not as as boot service. I can't recommend any workaround right now except...

@owenstake Did the system ask you to reboot when you tried to istall the USBDK?

@owenstake Are you able to build your own usbdk driver? If so, may be I can suggest some change.

@owenstake I suggest to try one thing: After UsbDK installation do not reboot. Enter regedit HKLM->System->CurrentControlSet->Service->UsbDK, edit the 'Start' and create the 'Group' like that:  Then reboot Does it...

@owenstake As far as I understand, your system is in fact something like Windows To Go (WTG). If so, probably it should follow the same recommendations as MSFT sets for...

Test "NICStrictPropertyValidation" with this driver passed on of 2025 HCK setup (@kostyanf14 ) QE do not succeed to pass it (the test does not find the log)

@madmax01 This should work assuming you have balloon driver installed on the guest. With build 240 and later and earlier. Look in device manager under "system devices" -> "virtio balloon...

Just did a smoke test with Fedora 36, libvirt-8.1.0-2.fc36, qemu qemu-6.2.0-17.fc36, 8GB/7GB, driver 228, works, hmp 'info balloon' returns 7G after boot

### **Win1122H2**: #### rss test: FAILED: [0] LibProtocolDriver: Install protocol driver failed. Failed to create/register Protocol driver with NDIS FAILED: [0] Unable to create Library Open object! FAILED: [88888] Failed...