Jump to content

Bryce Nesbitt

Experienced Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by Bryce Nesbitt

  1. These are huge, and Nvida's drivers never clean up after themselves. I've been using this for a few years now, works good.
  2. See also https://superuser.com/questions/82578/can-i-delete-the-folder-c-windows-installer-patchcache
  3. Would Ccleaner be interested in starting to clean NVIDIA log files? I have gigabytes of MessageBus_xxxxx.log.0 files, each 10 megabytes long. With scintillating stuff like: #0(W)[2021-09-22 01:10:00,801]{4}<MessageBus_18524_0x54DBD20> PerformReadCompletion on handle 3056 read error: 109 #0(D)[2021-09-22 01:10:00,803]{4}<MessageBus_18524_0x54DBD20> PerformDisconnectCompletion on handle 3056 for status 109 with pendingCount remaining: 0. #0(D)[2021-09-22 01:10:00,803]{4}<MessageBus_18524_0x54DBD20> PerformDisconnectCompletion on handle 3056 calling OnPipeDisconnect. #0(I)[2021-09-22 01:10:00,803]{4}<MessageBus_18524_0x54DBD20> Pipe Disconnect (109) from Broadcaster. #0(I)[2021-09-22 01:10:00,803]{4}<MessageBus_18524_0x54DBD20> Notifying peers of disconnect from Broadcaster. #0(D)[2021-09-22 01:10:00,803]{4}<MessageBus_18524_0x54DBD20> PipeEndpoint https://www.nvidia.com/en-us/geforce/forums/geforce-experience/14/304256/huge-amount-of-log-files/ See also https://www.howtogeek.com/342322/why-does-nvidia-store-gigabytes-of-installer-files-on-your-hard-drive/ and https://darkling.poppameth.com/nvidia-display-driver-cleanup-ccleaner/
  4. So what I see are large windows installation files, and not just in windows.old, that cccleaner is not giving any hints about. What could cccleaner in theory do about those files?
  5. On my system c:\Windows\Installer is nearly 20 GB. Is there anything Piriform can do, a modern version of patchcleaner? Would Microsoft cooperate with Priform on cleanup technology for this folder?
  6. I used to use "PatchCleaner" to get the garbage out of c:\Windows\Installer. I suggest that CCleaner is a good place to put this functionality back! "The directory c:\Windows\Installer is a protected system folder that becomes only visible if you disable the "hide protected operating system files (Recommended)" option in the Folder options. Depending on the age of the system, these orphaned files may take up a considerable amount of space (the most I have seen is 17 Gigabyte)." The windows operating system holds a list of current installers and patches, that can be accessed via WMI calls, (Windows Management Instrumentation ). PatchCleaner obtains this list of the known msi/msp files and compares that against all the msi/msp files that are found in the c:\Windows\Installer directory. Anything that is in the folder but not on the windows provided list is considered an orphaned file and is tagged to be moved or deleted" See: https://www.ghacks.net/2015/12/13/patchcleaner-remove-orphan-windows-installer-files-to-free-up-disk-space/ https://www.homedev.com.au/Free/PatchCleaner
  7. Interesting, good point. The Dr. Watson logs though don't seem to be locked.
  8. I like this because it can make for a two step clean: step one, move files. Step 2, actually delete them.
  9. CCCleaner is great. I've found a few more megabytes that cleaner maybe could address. Can anyone confirm these are big files on their setups also? 1) DrWatson logs. Dr Watson is a Microsoft system service that logs crashes, and keeps huge logs \Documents and Settings\All Users\Documents\DrWatson\user.dmp -- 104,005 Kb \Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log - 25,919 Kb Start "Dr Watson" from the run menu with "drwtsn32". 2) WindowsUpdate.log -- 1,468 Kb on my Windows 2000 box, with history going back to the dark ages. 3) WINNT/ShellIconCache -- Huge file, probably full of bloat. 4) WINNT/$Unist$Update$Shellc$ files. CCCleaner seems to leave a few of these.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.