When using the driver integration feature, I select the folder full of inf files instead of individual drivers, as the nvidia and realtek driver packages have dozens of them. However, when integrating them, NTlite creates instances of each inf file in the resulting FileRepository that is more or less the size of a standard nvidia manual driver install that is then archived to FileRepository; roughly 950MB - except its now 950MB multiplied by all the INF files in the nvidia driver install folder! Same thing for the RealTek. A normally 8GB Win10 install size on disk becomes >80GB!! Obviously this is not the end result anybody would want - and I'm not sure what is the fix?
Integrating NVidia and Realtek drivers blows up Windows 10 image by 70GB, all in DriverStore\FileRepository. Each NVidia inf has a >900MB folder
- Thread starter Fragbert
- Start date
George King
Active Member
When integrating add only latest drivers. On running system clean driverstore using script
Code:
https://www.ntlite.com/community/index.php?threads/driverstore-cleaner-script-or-anything-else.1528/post-12944Tharri, not a helpful or constructive reply.
I am integrating just a single version of NVIDIA's drivers as well as RealTek. I don't care there is a new updated one each week, I just want a Win10 install ISO that has something current enough to work with new NV and RT hardware. On a live system, that will take approximately 900MB and 200MB respectively in FileRepository if I install them manually. Instead, it seems each inf in the NV and RT install folder used to integrate via NTLite/DISM explodes the FileRep with folders of those INF filenames, each taking up those 900MB and 200MB figures, to the tune of 70GB.
George - I am only adding the latest driver from NVidia and Realtek. I don't think this is as much an NTLite issue as it is DISM in general and how integrating drivers is supposed to work. Win10 install with pre-loaded method = 70GB FileRepository - whereas Win10 install with just manually installing the very same NVidia driver post install yields just a 900MB addition to FileRepository (which is normal). Using a post-install cleanup script for the driverstore is fixing the space issue, but not the root cause; I just want to integrate the latest NVidia driver release to an offline image and not have it stupidly take up 70GB instead of the 900MB it's supposed to.
I am integrating just a single version of NVIDIA's drivers as well as RealTek. I don't care there is a new updated one each week, I just want a Win10 install ISO that has something current enough to work with new NV and RT hardware. On a live system, that will take approximately 900MB and 200MB respectively in FileRepository if I install them manually. Instead, it seems each inf in the NV and RT install folder used to integrate via NTLite/DISM explodes the FileRep with folders of those INF filenames, each taking up those 900MB and 200MB figures, to the tune of 70GB.
George - I am only adding the latest driver from NVidia and Realtek. I don't think this is as much an NTLite issue as it is DISM in general and how integrating drivers is supposed to work. Win10 install with pre-loaded method = 70GB FileRepository - whereas Win10 install with just manually installing the very same NVidia driver post install yields just a 900MB addition to FileRepository (which is normal). Using a post-install cleanup script for the driverstore is fixing the space issue, but not the root cause; I just want to integrate the latest NVidia driver release to an offline image and not have it stupidly take up 70GB instead of the 900MB it's supposed to.
A workaround (for now) is I opted to choose to install a specific driver (select a single inf) for both NVidia and Realtek from their respective driver installation folders; nv_dispi.inf and HDXPCEE4.inf. Their installation folders all have many more infs but seem to reference identical hardware. I then continued to use the "select folder" method for all other drivers (mostly an intel dump of chipset infs, plus LAN, SATA/RAID, etc) and none of those had any problems and were added to the FileRepository properly (no extra space vs a live install of the same drivers).
My install media is a naked, kosher pull of Win10 2004 x64 direct from MS using their ISO download/creation tool. The only thing I do in NTLite is convert the ESD to a WIM, remove all other versions other than PRO, and then install the drivers. For whatever insane reason, NTLite will create dozens of 900+MB directories for each additional inf file from the latest NVidia driver package and place them in the FileRepository reaching >70GB in size. There has to be a more intelligent way of integrating NV's infs? Note I am *NOT* singling out NTLite as the culprit, this could very well be a DISM fundamental behavior problem.
My install media is a naked, kosher pull of Win10 2004 x64 direct from MS using their ISO download/creation tool. The only thing I do in NTLite is convert the ESD to a WIM, remove all other versions other than PRO, and then install the drivers. For whatever insane reason, NTLite will create dozens of 900+MB directories for each additional inf file from the latest NVidia driver package and place them in the FileRepository reaching >70GB in size. There has to be a more intelligent way of integrating NV's infs? Note I am *NOT* singling out NTLite as the culprit, this could very well be a DISM fundamental behavior problem.