Missing CD driver USB support issues with windows 7

I guess since no one wants to read over my Boot.wim

I'll ask the question of is it desirable and/or necessary to install these updates into the boot.wim ? Should I be importing Host drivers from a windows 10 installation into the windows 7 Boot.wim ? Should I be importing windows 10 host drivers into windows 7 at all ?

kb4474419-v3 = SHA-2 Code Signing Support needed for modern drivers,
Kb2864202 = Needed for generic USB drivers
kb2670838 = graphic capabilities update needed for video games Tales of Vesperia etc.
kb4490628 = Servicing Stack Needed for all kinds of things to work.
kb2834140 = Needed to fix issues with kb2670838 = graphic capabilities update
KB2990941-v3 = Nvme support needed unless you want to use exclusively Samsung Nvme drives which have their own driver.
KB3004394-v2 = Root Certificates Needed for Https to work among other things.

These updates all seem fairly low level needed for the system to work kind thing.
 
George King said:
Never do it, this will totaly breaks your image! Unless you open related INF and find if driver cames from 7 era, but this is very rare.
Click to expand...

Ah, I figured windows wouldn't use the drivers if it didn't need to, that may the problem with my last image. I guess I really got to build a windows 7 that works with NTlite as the windows those windows 10 drivers are useless to me.

Thanks :)

Clanger said:
i have a rule, if i am building a 7 image i build on a 7 host, 8.1 image 8.1 host, 10 image 10 host.
Click to expand...

I wish I could, None of my copies of windows 7 will run NTlite it fails to load on 3 copies of windows 7 due to no kb4474419-v3 = SHA-2 Code Signing Support needed for modern drivers, and that update will not install no matter what I do.

On the 4th machine it gives me an error 87 invalid parameter (cause unknown) If I could do it on windows 7 I wouldn't be wearing 3 layers of gloves and using windows 10 ;)
 
im certain i havnt got kb4474419-v3 installed on this 7 system and ntlite runs ok. unless its in 3125574.
 
telemetry but that can be sorted with removals, i forget how.
there is a nag screen that 7 is eol, again thats easily sorted. not part of 3125574.
 
Clanger said:
telemetry but that can be sorted with removals, i forget how.
there is a nag screen that 7 is eol, again thats easily sorted. not part of 3125574.
Click to expand...

I'll test it out, good to know the nag screen isn't a part of that update, which update has the nag screen if you know so I can avoid it ?
 
You must log in or register to reply here.
Back
Top