What are these "Unknown Devices" suddenly showing up?

[Sonicmojo]

Just built out a new Win 11 24H2 PRO iso with my usual modest updates and changes. I try to leave as much alone as possible when using NTLite and by no means am I hacking the ISO to it's smallest micro size

Just installed this one to a 2021 ASUS ProART z490 CREATOR 10G board.

In this first test run I grabbed all the drivers from the ASUS site And updated the BIOS. Once I ran all the driver thru - I was left with these
oddball devices - which I have never seen before, know nothing about nor do I have any idea how they were detected.

Microsoft Hyper-V Virtual Machine Bus Provider ROOT\VMBUS\0000 This device is not working properly because Windows cannot load the drivers required for this device.

Microsoft Hyper-V PCI Server ROOT\VPCIVSP\0000 This device is not working properly because Windows cannot load the drivers required for this device.

Microsoft Hyper-V Virtual Disk Server ROOT\STORVSP\0000 This device is not working properly because Windows cannot load the drivers required for this device.

I do not have any virtualization turned on within the BIOS of this board nor any VT-D or anything else that could be related to this. Nor do I want any virtualization/hosting capability on this specific box.

Now - I DID choose to include the Hyper-V Management Tools within my NT Lite ISO (to manage other servers and VMs) - but would adding something simple like Hyper-V Manager - suddenly kick off the need for these devices? I removed these tools but these oddball "devices" remain.

A bit stumped here on whether this an ISO issue, a hardware device I have turned on by mistake or what.

Any tips would be appreciated.

Sonic.

 

[garlin]

To support Hyper-V VM's, Windows includes a default set of kernel drives to handle HW virtualization.

If you've removed the base Hyper-V features from Windows, then those drivers obviously don't work any more. It's safe to remove the Hyper V drivers if you don't intend to have Hyper-V in your install image.

 

[Sonicmojo]

To support Hyper-V VM's, Windows includes a default set of kernel drives to handle HW virtualization.

If you've removed the base Hyper-V features from Windows, then those drivers obviously don't work any more. It's safe to remove the Hyper V drivers if you don't intend to have Hyper-V in your install image.

Makes sense. But if this is by default - why did I not get any drivers in the first place?

These errors are tripping because Win 11 cannot find a driver to load (hence Unknown Device) - meaning - I do not have them.

What should I be doing (or NOT doing) in my NT Lite image to ensure the drivers DO come along and these devices install correctly?

S

 

[Sonicmojo]

Just a quick update - built another Win 11 install ISO and the only change made was to remove the Hyper-V "Optional Features" (see below).

Installed this to the new machine moments ago and these oddball "unknown devices" are nowhere to be found. This is clearly an NT Lite issue.

nuhi

Please see if you can look into this specific scenario:

If a user selects these specific "optional" Windows features within a typical Windows 11 24H2 Pro build:

View attachment 13763

And builds out their ISO per usual - upon install Windows will expose three Unknown Devices in Device Manager - with no possible way to know what drivers they need and no way to install them either.

I tried everything I could think of - until I finally just deleted these 3 devices outright - which actually worked (unbelievable).

Anyhoo - something is definitely funky with this obscure user case.

Logically - IF a user does want these specific optional features - and that choice means there ARE devices needed for this choice - Windows should install the drivers for these devices as part of it's standard setup. The user should not have to go on a wild goose chase like I did.

Cheers.

S