anybody interested in further reducing the size of the Driverstore Repository?
#1
Posted 19 May 2023 - 03:00 PM
#2
Posted 25 May 2023 - 01:51 PM
I'm certainly interested. What are your thoughts?
#3
Posted 25 May 2023 - 06:04 PM
first of all, sorry for not replying any earlier, but the threads have not been updated for a while, so I have no knowledge of anybody following unless I come back in. which I have just done. u can have my thoughts and facts and/or Virgus' procerures, if u like.
1) my thoughts are that u should copy ur driverstore folder someplace else first, just in case something goes wrong, and then try deleting as much as possible from inside the file repository, after having taken ownership of the folder.
2) my facts are that u should now use a pnputil script by virgus, making sure it points to the copy of the whole driverstore file repository that u have copied someplace else early on - this will restore some or all vital files for the system to restart ok. if the system does not restart, which means that the script has copied some and not all the vital info back to the driverstore file repository, u should copy the remnant subfolders from "someplace else" to the driverstore file repository in question, restart the computer and repeat the pnputil operation, which will complete ok this time. u will have twigged that u need some dual boot or other to do it all; I have plenty vhds to do it from and jostle back and forth between them, that is why it sounds so simple by the way I put it.
3) as for the detailed pnputil script writing procedures, pls ask virgus as I haven't got the slightest idea.
#4
Posted 12 June 2023 - 01:11 AM
within the driverstore repository, one can also make the nvidia driver subfolder all the smaller with a regfile that will also forceinstall every new version without using any further space than a few hundred megs. I have found out that for graphic acceleration and blender (and even nvidia encoding) to work one does not need all that plethora of files and folders that would amount to 1.70gb (required by the installation of the driverpack only). of course, it is a force-install procedure, so u cannot (yet, at least) expect the driver to appear as installed, but with a little manual replacement of the crucial files in the driverstore repository and windows\system32 subfolders the new version is active de facto. the regfile must be made from a system where the new version is conventionally installed, though, and all this should be carried out on a per-version basis. the most important gains of it all, at least for the time being, are low disk space usage and a much neater registry when nvidia successive installations that have accumulated through the months or years are gotten rid of in seconds. we hope that this empirical approach that has been the only one possible so far will pave the way for a more orthodox automation of the procedure. pls feel free to ask how it is done.
Also tagged with one or more of these keywords: windows 10, windows 11
Groups →
Windows Extreme →
Windows 7 →
How can I dual boot Windows 10 and Windows 7 on a Surface Book 2?Started by nar , 30 Jul 2020 windows 10, windows 7, dual boot |
|
|
||
bsod
Groups →
Windows Extreme →
Windows 10 →
BSOD Crashes Windows 10 since May UpdateStarted by wimb , 07 Jun 2020 bsod, crash, update, windows 10 |
|
|
||
Boot methods & tools →
Boot from LAN →
RFI - Widnows 10 Iscsi sysprep.Started by moriarty , 06 May 2020 ipxe, iscsi, windows 10, sysprep and 1 more... |
|
|
||
Boot methods & tools →
Boot from USB / Boot anywhere →
USB-Stick mounted as Fixed Or as RemovableStarted by wimb , 07 Aug 2019 usb, fixed, removable, windows 10 |
|
|
||
Answered
uefi
Boot methods & tools →
Boot from USB / Boot anywhere →
Linux_MULTIStarted by wimb , 22 Apr 2019 uefi, grub4dos, linux, grub2 and 1 more... |
|
|
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users