Feature to Scan for and Compare Old Drivers?

JBish

New Member
Messages
25
Reaction score
2
Once scanned... Compare to newer drivers being installed... And then an option to delete (Uncheck) the old before new ones will install... If that makes sense...
 
You can do that after you've installed updated drivers on a live install.
Or just use Windows DiskClean "Cleanup systemfiles" witch same time clean up WinSxS folder without breaking WU.
I know of this and have used for awhile now... This would make it easier to JUST upgrade the drivers in a build, without keeping all the outdated ones still install in the final build. If the outdated drivers are not installed from the door... No need to do an extra step after installing.
 
You can do it now, integrate/install the new driver, and delete the old one in NTLite. It requires a little searching on the Components page, but it only takes 20 seconds.

For an image, when a new driver version is available, I replace the version in the preset, and only the latest version is integrated.
 
I dont know how many drivers you're integrating, but it wouldn't take me 20seconds...lol... 50-60 drivers going into mine each time... IF building a new image... Sure I can remove them each from the install and then add the newer drivers... I've put together 1 build for all my systems, all current drivers etc, those change every few weeks to newer.. Actually the function of remove older drivers as Driver Store explorer does... It scans and you can remove "old" drivers
 
I'm integrating 7, maybe 8 in total, not counting the sub-drivers (multiple .inf files for the same driver) which are always in my preset, so that doesn't change.
I'm deleting many more, maybe ten times as many.

It takes a long time the very first time, sorting the drivers, etc... but after that, there's nothing left to do.
It takes me 20 seconds to modify the line in the preset now, and maybe another 20 when MS adds a new driver that I don't need with a CU

But 50, 60 drivers...
 
I'm integrating 7, maybe 8 in total, not counting the sub-drivers (multiple .inf files for the same driver) which are always in my preset, so that doesn't change.
I'm deleting many more, maybe ten times as many.

It takes a long time the very first time, sorting the drivers, etc... but after that, there's nothing left to do.
It takes me 20 seconds to modify the line in the preset now, and maybe another 20 when MS adds a new driver that I don't need with a CU

But 50, 60 drivers...
The one build I build/use... Supports all the ROG STRIX AM4 ITX motherboards... From the b450i to the crosshair impact viii and also the crosshair formula viii... There's only 3 updates (not drivers) needed after install... Store is another issue... Tons after install...
:cool::cool::D:D
 

Attachments

Last edited:
Ah yes, if it's for multiple machines, the drivers will accumulate.
Although for the same platform/chipset, some must be common.
 
Ah yes, if it's for multiple machines, the drivers will accumulate.
Although for the same platform/chipset, some must be common.
Makes it easy yes initially, but updating that many drivers is why I asked about scanning and removing old before compiling another build.

:)
 
I know of this and have used for awhile now... This would make it easier to JUST upgrade the drivers in a build, without keeping all the outdated ones still install in the final build. If the outdated drivers are not installed from the door... No need to do an extra step after installing.
Just to say - it's like build a snowman up the hill if theres snow.
Drivers are released regularly in addition to the ones WU updates after you log in.
It's a waste of time since drivers are updated regularly.
And the gamer fanatics will probably figure it out themselves depending on their graphics cards.
Just saying.
 
Once scanned... Compare to newer drivers being installed... And then an option to delete (Uncheck) the old before new ones will install... If that makes sense...
If you want my opinion.
It's acctually possible like WU integrated updates.
But it need a second load of NTL and a DISM cleanup to remove outdated updates and drivers.
And depending on the facts, I think NUHI (the developer) decides for itself what is worth spending time on.
It's not about unchecking - it's learning how NTL work.
 
Anyway, was just a thought... New features are usually always good if it makes the work flow easier or faster IMO...

Ya"ll be safe
 
Back
Top