#Ntlite remove drivers install
#Ntlite remove drivers driver
#Ntlite remove drivers windows 10
#Ntlite remove drivers iso

Server editions of the same versions, excluding support for component removals and feature configuration.

#Ntlite remove drivers install

IF I am in Components > Drivers and sift through the long list to find Exportables.īut I'm not sure what to do with them after that for a clean Windows install to see them.Supports Windows 11, 10, 8.1 and 7, x86 and 圆4, live and image. So now I see that I can export the Exportable drivers to a folder somewhere on my computer. It has vendor names, and mentions inf files.īut the List doesn't actually 'capture' the sys files (and maybe dlls) that my drivers need.

#Ntlite remove drivers windows 10

They did NOT install in the clean Windows 10 installation.

I thought that this would be enough for my clean install of Windows to find the exportable drivers and load them during the install so that everything would be up and running after setup completed.īut, no. I thought I was being especially clever when I told NTLite to integrate the drivers into the pre-boot environment too.

#Ntlite remove drivers driver

They showed up in NTLite on the driver page and I thought, 'Cool!'

#Ntlite remove drivers iso

Then, when I loaded the clean iso for a clean install of Windows, I imported my Hardware List. So before I made a wim for the clean install, I loaded my current running Win10 in NTLite Live.įrom there I went to the Drivers page, and I exported my Live drivers to a Hardware List. (Like the Intel chipset inf update, Intel NVME driver, etc.) And, besides, that, over the past year, I've manually found and installed more current drivers than the ones that came with the Dell. My Dell has drivers unique to Dell that came preinstalled. I installed a clean Windows 20H2 on my Dell Box. Specifically, I didn't use the 'Export drivers' feature.īut surely there must be a way for NTLite to gather up all the Exportable drivers in one click and save them for future use? Because I have about 40 'exportable' drivers that I would have to find manually. This is harder - or perhaps 'more tedious' - than I expected.

Or, as I think about it, is that what Windows already does when you do a Host Refresh but don't keep anything? (I have assumed that it wipes everything out and installs Windows from scratch. (Although that might be difficult, since I will often see nVidia and stuff in Services, implying that their installers touched the Registry.) Like my Hauppauge USB-TV stick? Or sometimes these installers ask you questions.) I am looking for an easier (lazier) way to capture the drivers that are currently in use in a Live Windows and slipping those into a wim.Īlternatively, if there was a way to do a 'pseudo-clean' Host Refresh, where, say, NTLite let Windows keep my drivers but replaced everything else with a fresh (but Lite'd) Registry), that would work too. (Although some of those installers might not work with NTLite here. I know that I could trudge through my Downloads folder and manually add drivers to NTLite.

Can it then collect all the active drivers for my hardware and put them in a folder (similar to the Upload folder) so that when I work offline on a fresh Windows wim, I can point NTLite to this folder so that NTLite will automatically integrate all my drivers in a new wim? Like 'capturing' active drivers? When I run a Live version of NTLite, NTLite seems to know what hardware I have. (Some that were 'forced' - like forcing Windows to use Intel's NVME driver for my WDBlue NVME.) And let's say that my Dell is already running Win10 and that, over the years, I have already manually downloaded and installed the latest drivers. So, let's say that I want to do a bare metal (re)install of Win10 on a Dell.