Hyper-V driver problems on a VM created by Hyper-V

Windows 10 User

Active Member
I used NTLite and a Windows 10 19041.1 Enterprise x64 pt-pt image to create a new image and used it to do a clean install on the host and on a VM created by Hyper-V and Windows doesn't install a driver in "System devices" and Windows doesn't install a driver in "System devices" and a hidden driver shows up in "Other devices" as "Unknown device" on Device Manager on the VM. According to what I searched, the first driver is Hyper-V Virtual Machine Bus Provider and the latter is Microsoft Hyper-V Virtual Machine Bus. If I uninstall both drivers on Device Manager and click on the "Scan for hardware changes" setting, Hyper-V Virtual Machine Bus Provider driver isn't reinstalled unlike the Hyper-V Virtual Machine Bus one (which shows up as "Unknown device" again).
 

Attachments

  • Captura de Ecrã (2).png
    Captura de Ecrã (2).png
    79.5 KB
  • Captura de Ecrã (4).png
    Captura de Ecrã (4).png
    75.6 KB
  • Captura de Ecrã (6).png
    Captura de Ecrã (6).png
    90.7 KB
  • Captura de Ecrã (7).png
    Captura de Ecrã (7).png
    87.3 KB
  • preset.xml
    30.6 KB
Last edited:

nuhi

NTLite developer
Staff member
The file C:\Windows\INF\setupapi.dev.log will contain more info on the driver install error.
If it's not clear, zip and attach it here after triggering the issue one more time to have it at the end of file.

That said, try enabling Windows Hypervisor Platform feature as well, and Components - Compatibility - HyperV just in case (I tested and no difference, but still nice to have something you need protected for future updates).

Don't see anything related to hyperv removed.
 

Windows 10 User

Active Member
The file C:\Windows\INF\setupapi.dev.log will contain more info on the driver install error.
If it's not clear, zip and attach it here after triggering the issue one more time to have it at the end of file.

That said, try enabling Windows Hypervisor Platform feature as well, and Components - Compatibility - HyperV just in case (I tested and no difference, but still nice to have something you need protected for future updates).

Don't see anything related to hyperv removed.

I still have this problem after enabling Windows Hypervisor Platform and checking the Hyper-V compatibility. The setupapi.dev.log file is attached as follows.
 

Attachments

  • setupapi.dev.log
    7.2 KB
Top