"The install class is not present or is invalid." (VMware driver)

frewys

frewys

Member
Messages
53
Reaction score
9
Hi

Been going nuts all day trying to build a VM machine.

When I try to add the VMware driver pack it goes great except tfor he graphics where it stops and rollbacks the previously installed drivers and asks me to install it manually. When I try to do that I get the error in the title.

Attached is my preset file
I only removed components active
Windows 11 LTSC 24H2
 
Last edited:
The original preset XML (minus any user passwords or license key) is the preferred file format for posting. A full XML can be used by someone else to duplicate your last NTLite session.

My guess is you removed driver_vmxnet3.inf (or another base driver) from the image, and now VMware's annoyed. Try it without any driver removals.
 
garlin said:
The original preset XML (minus any user passwords or license key) is the preferred file format for posting. A full XML can be used by someone else to duplicate your last NTLite session.

My guess is you removed driver_vmxnet3.inf (or another base driver) from the image, and now VMware's annoyed. Try it without any driver removals.
Click to expand...
Thanks for replying

That is an ethernet driver. It would mess up the graphics driver like that?

The interesting thing it seems to be no one with this issue before on the forum.

Worth a shot I guess. And trying to keep all drivers.

Will post the XML for convenience
 
There's two options when working with VM's. If you don't integrate the VM's guest drivers into the image, then Windows first recognizes the VM's "generic" devices that it emulates. After manually applying the guest extensions, you switch to the preferred drivers.

But in this scenario, there could be a driver conflict. You're adding the driver set (not individual drivers). Do you know which driver it's complaining about? Most of the time you leave intact whatever drivers VMware contributed to the default Windows image.

I install Windows images all day on my VMware Workstation, and apply the guest extensions. Never seen your error before, but then I don't remove VMware or Hyper-V virtual devices if I expect to run on those platforms.
 
garlin said:
There's two options when working with VM's. If you don't integrate the VM's guest drivers into the image, then Windows first recognizes the VM's "generic" devices that it emulates. After manually applying the guest extensions, you switch to the preferred drivers.

But in this scenario, there could be a driver conflict. You're adding the driver set (not individual drivers). Do you know which driver it's complaining about? Most of the time you leave intact whatever drivers VMware contributed to the default Windows image.

I install Windows images all day on my VMware Workstation, and apply the guest extensions. Never seen your error before, but then I don't remove VMware or Hyper-V virtual devices if I expect to run on those platforms.
Click to expand...
I am in Asia. It's after midnight and getting a little tired. Trying to make sense of what you are saying. Probably makes more sense tomorrow morning

But I did click compatibility for VMware. Didn't do it for Hyper-V though but that should not be needed for a VMware machine?

Thanks again and back tomorrow :)
 
frewys said:
Hi

Been going nuts all day trying to build a VM machine.

When I try to add the VMware driver pack it goes great except tfor he graphics where it stops and rollbacks the previously installed drivers and asks me to install it manually. When I try to do that I get the error in the title.

Attached is my preset file
I only removed components active
Windows 11 LTSC 24H2
Click to expand...
Tested and I see something, will let you know which dependency is it tomorrow and add it to the VMWare compatibility.
 
nuhi said:
Tested and I see something, will let you know which dependency is it tomorrow and add it to the VMWare compatibility.
Click to expand...
That is amazing. Thank you Nuhi you are a legend!
Used your software since the great nlite days (until your disappearance) but had a looooong break with some short random tries.

I hope you don't keep me in suspense for too long ;)
 
Thank you, let's keep it short then :)

Display Policy Service - needed for VMWare Guest windows autosizing - this one was ID-ed for my pains.
QoS removal was breaking, or just causing a question mark in the device management on the network card (recent regression).
Fix uploaded, it was a generic one, should have all fixed, unless I mis-tested something in the last pass.

Please try the new version, let me know if you have remaining issues.
 
nuhi said:
Thank you, let's keep it short then :)

Display Policy Service - needed for VMWare Guest windows autosizing - this one was ID-ed for my pains.
QoS removal was breaking, or just causing a question mark in the device management on the network card (recent regression).
Fix uploaded, it was a generic one, should have all fixed, unless I mis-tested something in the last pass.

Please try the new version, let me know if you have remaining issues.
Click to expand...
Thank you both as I have added your driver and the display policy server. (I updated NTlite to the latest and clicked VMware support but it didn't add the Display policy service so added it manually. Also was not sure what QoS you were referring to so added them all or if that was even what you suggested) Also tried to add some more drivers like Display and Computer.

Unfortunatly. Still the same issue . Playing some more with it..

Edit:
I was playing around with it and found a nested drivers section I completely missed under Hardware Support - Individual devices (advanced). Added Display and some other drivers and that seems to have done it :)
 
Last edited:
frewys said:
Thank you both as I have added your driver and the display policy server. (I updated NTlite to the latest and clicked VMware support but it didn't add the Display policy service so added it manually. Also was not sure what QoS you were referring to so added them all or if that was even what you suggested) Also tried to add some more drivers like Display and Computer.

Unfortunatly. Still the same issue . Playing some more with it..

Edit:
I was playing around with it and found a nested drivers section I completely missed under Hardware Support - Individual devices (advanced). Added Display and some other drivers and that seems to have done it :)
Click to expand...
OK, great. Yes, the c_display.inf and display.inf in your preset are an obvious issue - haven't looked at it manually as the test passed.
As to how the last test of mine after fixing QoS/Network cleanup didn't trigger the display.inf issue is a bit puzzling.
Reran it now with just those INFs removed and VMWare SVGA 3D device is present as not installed in the device manager, which would make me search for those.

Those support INFs should be locked by VMWare compatibility chained from the kept drivers, will improve on that.
Yes, hardware support individual devices support should be avoided - it's small anyway - only useful if you want to lock the devices towards some type of devices.

Btw you don't have to keep Display Policy Service if you don't use VMWare Guest window resizing in VMWare Workstation for example.
The QoS removal was fixed, no need to keep that either. That fix was a legit issue with networking cleanup.
You can basically use your original preset, just keep individual devices support or target even only the display ones as I don't see other quirks in the device manager after removing all of them.

Thank you for the feedback.
 
nuhi said:
OK, great. Yes, the c_display.inf and display.inf in your preset are an obvious issue - haven't looked at it manually as the test passed.
As to how the last test of mine after fixing QoS/Network cleanup didn't trigger the display.inf issue is a bit puzzling.
Reran it now with just those INFs removed and VMWare SVGA 3D device is present as not installed in the device manager, which would make me search for those.

Those support INFs should be locked by VMWare compatibility chained from the kept drivers, will improve on that.
Yes, hardware support individual devices support should be avoided - it's small anyway - only useful if you want to lock the devices towards some type of devices.

Btw you don't have to keep Display Policy Service if you don't use VMWare Guest window resizing in VMWare Workstation for example.
The QoS removal was fixed, no need to keep that either. That fix was a legit issue with networking cleanup.
You can basically use your original preset, just keep individual devices support or target even only the display ones as I don't see other quirks in the device manager after removing all of them.

Thank you for the feedback.
Click to expand...
Thank you for all your help and guidance

Looking forward to be back to my old nlite days.

Having some issues with my autounattend file I am working on now

Glad we got this sorted though :)
 
You must log in or register to reply here.
Back
Top