Can't install CheckSUR (System Update Readiness Tool) --- (log+screencast)

[deleted01022019]

Hello everyone,

I'm having stubborn corruption issues on my Windows 7 Ultimate 64bit. I have tried hard to solve this for almost 2 weeks now, without success..
I'm a bit surprised/offended to find myself being forced to resort to specialized forums like this one to fix my problem because I usually always find a way of my own. But this time I will need you guys.

My problem is very similar to zac1 on this thread, whom receive great help from Rkinner: Windows 7 will not update - Geeks to Go Forums
I'm fairly good at digging into Windows OS so I'll be able to follow your instruction very easily, without having you to be extremely detailed and to describe any common IT terms.


Problem
========
- Corrupt system files which leads to problem installing/uninstalling applications, windows update, ssd firmware, basically anything that require deeper system's integration.
- sfc scan find corrupt files but can't fix them all.



Troubleshoot done so far
========================
- Scanned for presence of any malwares/virus/rootkit. Result --> none
- Uninstalled/Reinstalled corrupt applications Result --> Sucess, but had to uninstall the dirty way (Revo uninstaller and manual registry left-over removal)
- Installed all missing .NET Framework & Visual C++ Redistributables
- Registry scan/clean (CCleaner, Little Registry Cleaner, and such) Result --> Many problem found/fixed, without real improvement.
- sfc scan (sfc /scannow)
- checkdisk scan (chkdsk /f /v /r /x /b)
- Reset system's default permission using Tweaking.com's tools (and some manual manipulation)



Generated logs: *list of all generated log files (*all done with elevated administrator privilege:
===============
- sfc scan ---> https://www.dropbox.com/s/h24h371z1ynjgxv/sfc scan log.txt (or see attached file)
- chkdsk scan ---> https://www.dropbox.com/s/7e45yw9e7j9dpgw/chkdsk.txt (or see attached file)
- OTL scan ---> can't complete a scan because of infinite loop on the AppData directory ---> http://screencast.com/t/C83Rut1Bnqgt
- CheckSUR ---> can't install the System Update Readiness Tool either but was able to get some log: https://www.dropbox.com/s/ld02wwmlv1b8k7n/CbsPersist_20140313224512.cab (file is too big to attach)
- SFCFix 2.1.4.0 by niemiro --> https://www.dropbox.com/s/3xtnphhfszt7x5u/SFCFix.txt (or see attached file)






Here's what happen when I try to install CheckSUR --> screencast.com/t/U7SNiLXY
As you can see I can extract the content of the installer... is there something I can do with those extracted file ? I tried but its a mess of multiple cab files...


Also, I just cleared my event viewer log to do a fresh monitoring of that CheckSUR install.
here's what I got: ---> screencast.com/t/o5QemdgspC

 

[niemiro]

Hello, and welcome to Sysnative!

Really well done for what you have tried already, and for writing up so well what those things well. Thank you.

For the purposes of future reference (it doesn't matter now), I would like to discuss these two minor points:

- Reset system's default permission using Tweaking.com's tools (and some manual manipulation)

Please don't do this again The reason why I say this is that these permissions reset fixes have been floating around since Windows XP's time. The permissions model changed dramatically with Windows Vista, but the fixes were never updated, and are pedalled for Windows Vista and above. For Windows XP, they're fine. For Windows Vista and above, they're not. But why? not, I hear you ask. The reason is simply security. With Windows XP, permissions were a bit of a bolt on to the security model. They allowed system admins finer control over who could edit/whatever certain files. In Windows Vista, they are the security model. Permissions are far more complex, and the security of system files is now no longer tied into whether the active account is an admin (Microsoft know that too many people run as admin by default), but whether the current context (may not be the same as current user) has the right to alter that file. Permissions are restricted by ownership, ownership is restricted by administratorship. But when the permissions are reset (I would call it "destroyed") by this tweaking.com tool, or by various subinacl scripts (here, there's nothing wrong with the tool, only how it's being used), etc. etc. (there are lots of such tools), virtually any unknown script or user can change system files, and I guess I don't need to stress to you how bad that is. It's a massive security risk, so please don't do it again :) [actually, it's not quite that bad, it's a high risk but low prevalence threat so there's not much malware out searching for it so it's not really an issue. It's only really a problem if you've got a disgruntled employee/whatever on your network]. [SFCFix by contrast spents a great deal of its time and source coding ensuring that permissions/ownership are always restored to exactly how they should be].

Second, OTL is now an outdated and discontinued tool. However, it's not yet necessarily to be completely abandoned yet, as it's one of the easier/most publicly documented tools. Just something to keep in the back of your mind when using, especially when you run into bugs.


Right, now let's get down to business. I've looked over your logs very carefully, and really see very little in the way of an explanation for the SURT failing. I want to dig further. HDD condition from chkdsk log looks fine, and you have a couple of missing files in your SFC report, but I don't see them as serious issues in any way to be honest. I'll fix them in a bit, but I don't see them as an explanation for your problems.


There are two distinct stages to a SURT run. The first is to extract all replacement files currently in its payload (this actually accounts for the majority of the processing time). Let's say a certain security catalog file is corrupt, SURT needs a good copy to replace it with. SURT carries a lot of these file in a complex set of .cab files, but first it needs to extract them. It's second stage is a corruption detection/repair stage.

I'm not sure which stage it's failing at for you, but I want to find out. What we're going to do is bypass the first stage. The SURT won't be able to repair file system corruptions, but that doesn't bother me, if I get the log I can use SFCFix to make the repair.

Look at your extracted SURT files. Do you see a CheckSURPackage.exe file? If you do, move onto step 2. Otherwise follow step 1.

Step 1: Download attached KBExtractor 2.0 (a tool of my own creation). Place the .exe file on your Desktop, then drag and drop the SURT on to the .exe. Release, and allow the extraction to occur. When complete, a folder will open. Go up one directory level, then open the "Windows6.1-KB947821-v31-x64.msu" folder. Find CheckSURPackage.exe.

Step 2: Download attached KBExtractor 2.0 (a tool of my own creation). Place the .exe file on your Desktop, then drag and drop CheckSURPackage.exe on to the .exe. Locate checksur.exe, and copy it to your Desktop.

Step 3: Open a command prompt on your Desktop, and run checksur.exe /scannow

Let it complete, note down any failure, collect C:\Windows\Logs\CBS\CheckSUR.persist.log when complete if it exists then upload.

I may provide one further step in a couple of hours, but this should be enough to be getting on with.

Richard

EDIT: How much free space do you have on your various SSDs/HDDs?

 

[deleted01022019]

A reply from Niemiro himself :) Great !
Thansk for you time niemiro, you have no idea how much i appreciate your help !

Hello, and welcome to Sysnative!
Please don't do this again The reason why I say this is that these permissions reset fixes have been floating around since Windows XP's time. The permissions model changed dramatically with Windows Vista, but the fixes were never updated, and are pedalled for Windows Vista and above. For Windows XP, they're fine. For Windows Vista and above, they're not. But why? not, I hear you ask. The reason is simply security. With Windows XP, permissions were a bit of a bolt on to the security model. They allowed system admins finer control over who could edit/whatever certain files. In Windows Vista, they are the security model. Permissions are far more complex, and the security of system files is now no longer tied into whether the active account is an admin (Microsoft know that too many people run as admin by default), but whether the current context (may not be the same as current user) has the right to alter that file. Permissions are restricted by ownership, ownership is restricted by administratorship. But when the permissions are reset (I would call it "destroyed") by this tweaking.com tool, or by various subinacl scripts (here, there's nothing wrong with the tool, only how it's being used), etc. etc. (there are lots of such tools), virtually any unknown script or user can change system files, and I guess I don't need to stress to you how bad that is. It's a massive security risk, so please don't do it again :) [actually, it's not quite that bad, it's a high risk but low prevalence threat so there's not much malware out searching for it so it's not really an issue. It's only really a problem if you've got a disgruntled employee/whatever on your network]. [SFCFix by contrast spents a great deal of its time and source coding ensuring that permissions/ownership are always restored to exactly how they should be].

THANKS so much for that explanation of the use of such permission reset tools. People who create those should take the responsability to update them or at least inform their user of such essential information ! Thanks for sharing.

Second, OTL is now an outdated and discontinued tool. However, it's not yet necessarily to be completely abandoned yet, as it's one of the easier/most publicly documented tools. Just something to keep in the back of your mind when using, especially when you run into bugs.

I'll take note of it.

Look at your extracted SURT files. Do you see a CheckSURPackage.exe file?

Yes

Step 2: Download attached KBExtractor 2.0 (a tool of my own creation). Place the .exe file on your Desktop, then drag and drop CheckSURPackage.exe on to the .exe. Locate checksur.exe, and copy it to your Desktop.

Where can I find that KBExtractor 2.0 tool ? I can't find it in attachement.

EDIT: How much free space do you have on your various SSDs/HDDs?

128Gb free out of 238Gb - it's a SSD --> Samsung SSD 840 PRO Seri (238 GB)
By the way, I think it might be relevent to let you know that I have also issue updating this SSD's firmware (Samsung released a new firmware somewhere back in the end of 2013). The SSD run very fine without it, I just can't update the firmware .. Their GUI (Samsung magician) ask me to disable RAPID mode (a feature of the Samsung SSD) 2014-03-15_0828 - jngkrlr's library I will try again, but I remember having trouble getting magician to detect that disabled RAPID mode.

This said. I'll be waiting for the link to download your tool (KBExtractor 2.0)
Thanks !

 

[niemiro]

You're more than welcome!

I've tried many times to argue with the creators/users of those permissions reset tools. Sadly, it's got me nowhere.


Anyway, let me know how the SSD firmware update goes/whether or not it succeeds this time. There are a whole raft of potential issues especially the older SSD firmware can cause (manufacturers have been hitting the bugs hard the last couple of years though. Three years ago SSDs were horrendously buggy, now they're more stable than buggy). Let me know how it goes.


As for KBExtractor, yes, I forgot to upload it ;p

See attached (we hope!)

Richard

 

[deleted01022019]

You're more than welcome!

I've tried many times to argue with the creators/users of those permissions reset tools. Sadly, it's got me nowhere.


Anyway, let me know how the SSD firmware update goes/whether or not it succeeds this time. There are a whole raft of potential issues especially the older SSD firmware can cause (manufacturers have been hitting the bugs hard the last couple of years though. Three years ago SSDs were horrendously buggy, now they're more stable than buggy). Let me know how it goes.

The firmware update failed again. But this time I have monitored the failure with Event viewer..
here's what I get:
- Simple screenshot of failure --> 2014-03-15_0908 - jngkrlr's library
- Detailed log (3 entries): https://www.dropbox.com/s/w72v1qnshg9msc0/Failed Disable Samsung RAPID mode log.txt (or see attached file)

------------------------------------------

KBExtractor scan result : 2014-03-15_0922 - jngkrlr's library
KBExtractor scan log: https://www.dropbox.com/s/m0gvgs7xmfffvrb/CheckSUR.zip (or see attached)

 

[deleted01022019]

done . see previous post

 

[niemiro]

Windows Installer error code 1605 is....not usually a good sign.

Can you please start a command prompt, and get me a dir listing of C:\Windows\Installer folder.

Thank you.

Richard

 

[niemiro]

OK, on the CheckSUR.log: those missing files are exactly the same as those from SFC (at least we get a match!). I will get them sorted shortly (the .log file's a bit more complex). They do not (as far as I am aware) offer any explanation of your continued problems.

Secondly, given the fact that SURT completed, suggests an extraction problem. We can delete all pre-extracted files, and give it another shot soon too (I'm currently in the middle of coding a bug-fix and I don't want to lose my train of thought too much), but that still doesn't explain "why". Problem relating to your SSD, especially a firmware issue , looking more likely by the minute.

Get me that Installer folder listing, then I'll have a think and get back to you on our next course of action.

Richard

 

[deleted01022019]

Windows Installer error code 1605 is....not usually a good sign.

Can you please start a command prompt, and get me a dir listing of C:\Windows\Installer folder.

Thank you.

Richard

C:\Windows\Installer>dir
Volume in drive C has no label.
Volume Serial Number is 1011-3382


Directory of C:\Windows\Installer


03/10/2014 03:59 AM 26,112 107c06.msi
02/21/2003 11:43 AM 5,922,304 11d2bd.msi
10/30/2013 02:52 AM 8,179,712 152c9.msp
11/09/2013 09:20 AM 7,577,600 176edc.msp
03/18/2010 08:29 PM 872,448 1816ea.msi
07/09/2012 04:52 AM 1,531,904 1dabe.msi
10/31/2013 06:35 AM 26,079,232 20c795.msp
10/05/2013 03:40 AM 143,360 2dc46.msi
10/05/2013 03:40 AM 143,360 2dc4b.msi
10/05/2013 03:39 AM 143,360 2dc50.msi
10/05/2013 03:39 AM 143,360 2dc55.msi
10/30/2013 05:08 AM 151,552 2dc5a.msi
10/30/2013 05:08 AM 151,552 2dc5f.msi
10/30/2013 05:09 AM 151,552 2dc64.msi
10/30/2013 05:08 AM 151,552 2dc69.msi
09/23/2012 11:47 PM 2,385,920 3000e7.msi
12/21/2013 03:58 AM 19,824,640 3000e8.msp
07/29/2008 07:14 PM 153,600 550b9a.msi
03/07/2014 08:55 AM 27,488,256 6c3d3.msi
03/12/2014 09:48 PM 292,148,224 70eeb7.msi
03/11/2014 03:26 PM 82,714,624 71c7a7.msi
09/12/2013 08:44 AM 1,544,192 7b1033.msi
01/07/2013 02:56 PM 8,030,720 8ae3fd.msi
03/13/2014 12:45 AM 434,176 94b6ad.msi
03/10/2014 02:35 AM 3,981,312 9a825.msi
03/10/2014 02:35 AM 806,912 9a82a.msi
03/10/2014 02:35 AM 2,383,872 9a82f.msi
03/10/2014 02:35 AM 806,912 9a834.msi
03/10/2014 02:35 AM 2,371,584 9a839.msi
03/10/2014 02:35 AM 811,008 9a83e.msi
03/10/2014 02:35 AM 2,371,584 9a843.msi
03/10/2014 02:35 AM 2,375,680 9a848.msi
03/10/2014 02:35 AM 2,375,680 9a84d.msi
03/10/2014 02:35 AM 2,396,160 9a852.msi
03/10/2014 02:35 AM 2,371,584 9a857.msi
03/10/2014 02:35 AM 2,367,488 9a85c.msi
03/10/2014 02:35 AM 2,375,680 9a861.msi
03/10/2014 02:35 AM 1,851,392 9a866.msi
03/10/2014 02:35 AM 1,855,488 9a86b.msi
03/10/2014 02:35 AM 1,839,104 9a870.msi
03/10/2014 02:35 AM 806,912 9a875.msi
03/10/2014 02:35 AM 974,848 9a87a.msi
03/10/2014 02:35 AM 806,912 9a87f.msi
03/10/2014 02:35 AM 2,670,592 9a884.msi
03/10/2014 02:35 AM 2,392,064 9a889.msi
03/10/2014 02:35 AM 1,585,152 9a890.msi
03/10/2014 02:35 AM 29,888,512 9a8a4.msi
08/08/2008 02:46 PM 242,176 a5a34.msi
11/07/2007 08:12 AM 232,960 a5a39.msi
08/08/2008 02:11 PM 232,960 a5a3f.msi
11/07/2007 08:53 AM 242,176 a5a46.msi
09/23/2005 07:48 AM 2,483,200 a5a4b.msi
09/23/2005 03:32 AM 4,022,784 a5a50.msi
02/19/2011 11:08 PM 163,840 a5a77.msi
02/19/2011 10:57 PM 177,664 a5a93.msi
12/02/2006 02:20 AM 3,227,648 f87cf.msi
03/11/2014 03:27 PM <DIR> {090931D6-A2F4-11E3-AD9C-00163E98E7D0}
03/07/2014 08:55 AM <DIR> {1845470B-EB14-4ABC-835B-E36C693DC07D}
03/12/2014 09:49 PM <DIR> {1F91344A-B963-4431-89E8-4F80DEE282BE}
03/13/2014 12:28 AM <DIR> {22800204-9E53-45C7-B6F3-5BB0F1C1A147}
03/10/2014 02:38 AM <DIR> {90150000-0011-0000-1000-0000000FF1CE}
03/10/2014 02:35 AM <DIR> {90150000-001F-0409-1000-0000000FF1CE}
03/10/2014 02:35 AM <DIR> {90150000-001F-040C-1000-0000000FF1CE}
03/10/2014 02:35 AM <DIR> {90150000-001F-0C0A-1000-0000000FF1CE}
03/10/2014 02:35 AM <DIR> {90150000-006E-0409-1000-0000000FF1CE}
03/10/2014 02:36 AM <DIR> {90150000-00C1-0000-1000-0000000FF1CE}
03/07/2014 06:38 AM <DIR> {AC76BA86-7AD7-1033-7B44-AB0000000001}
56 File(s) 569,585,152 bytes
11 Dir(s) 137,352,278,016 bytes free


C:\Windows\Installer>

 

[deleted01022019]

I'm currently trying to burn the firmware update (the iso version) from that link --> Samsung SSD (Solid State Drive) 840 series | Samsung SSD Website
to a cd.

[TABLE="class: radiusTbl tdBorder, width: 960"]
[TR]
[TD="class: bgFirst bgGray, bgcolor: #F4F4F4"]840 PRO[/TD]
[TD]DXM06B0Q[/TD]
[TD]DXM06B0Q[/TD]
[/TR]
[/TABLE]

 

[deleted01022019]

ssd firmware update complete (used the boot disk method): 2014-03-15_1015 - jngkrlr's library
I'll make another chkdsk and sfc scan and post the logs here. brb

 

[niemiro]

ssd firmware update complete (used the boot disk method): 2014-03-15_1015 - jngkrlr's library
I'll make another chkdsk and sfc scan and post the logs here. brb

Excellent! Just as a quick test, can you now install the SURT normally or not?

 

[deleted01022019]

ssd firmware update complete (used the boot disk method): 2014-03-15_1015 - jngkrlr's library
I'll make another chkdsk and sfc scan and post the logs here. brb

Excellent! Just as a quick test, can you now install the SURT normally or not?

SURT installation still fail

 

[deleted01022019]

chkdsk log -->

 

[deleted01022019]

sfc scan log
detailed (full CBS log file) --> https://www.dropbox.com/s/dshqrfrvrtxvgln/CBS.log
filtered --> https://www.dropbox.com/s/9t1ashilbpl64r0/sfcdetails.txt (or see attached)


pretty much same result here..

So, to resume, we got this list of files to be fixed right ?
Desktop.ini
MSDTC.LOG
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..soundthemes-savanna_31bf3856ad364e35_6.1.7600.16385_none_8501e89d0b011992
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..oundthemes-heritage_31bf3856ad364e35_6.1.7600.16385_none_5872c0830d0c4747
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..-soundthemes-sonata_31bf3856ad364e35_6.1.7600.16385_none_201752c112c5078c
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..undthemes-cityscape_31bf3856ad364e35_6.1.7600.16385_none_5b48f43248490503
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..undthemes-afternoon_31bf3856ad364e35_6.1.7600.16385_none_2a05e57d5ab3659e
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..oundthemes-festival_31bf3856ad364e35_6.1.7600.16385_none_121f20b55f0bde68
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-shell-soundthemes-raga_31bf3856ad364e35_6.1.7600.16385_none_2fe300bf8e73cdbd
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..-soundthemes-quirky_31bf3856ad364e35_6.1.7600.16385_none_e55404efe49bb9cb
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..undthemes-landscape_31bf3856ad364e35_6.1.7600.16385_none_7a83a914edc3de49
(f) CSI Payload File Missing 0x00000000 Desktop.ini amd64_microsoft-windows-s..ndthemes-characters_31bf3856ad364e35_6.1.7600.16385_none_08da32b0fdad9220

...

CheckSUR install from standalone installer still fail (Windows6.1-KB947821-v32-x64.msu)
However, remember that I was able to extract the content of that installer file... couldnt we use those to make the CheckSUR install ?

Also this is the 64bit version installler, should I try the 32bit version ?

Take your time btw, i know that you might be busy, im just being be pro-active in the process
see you later

 

[NoelDP]

One comment, if I may?? (Please feel free to slap me down!)

The fact that the majority of the affected files are Desktop.ini files gives me the impression that some sort of system cleanup tool has been used, and it's ignored the ACLs, and broken the system fairly efficiently.

Can I ask what tool it was that was used? - I would suspect something from either the Wise or IoBit stables, but it's not a symptom I've seen elsewhere.

 

[deleted01022019]

One comment, if I may?? (Please feel free to slap me down!)

The fact that the majority of the affected files are Desktop.ini files gives me the impression that some sort of system cleanup tool has been used, and it's ignored the ACLs, and broken the system fairly efficiently.

Can I ask what tool it was that was used? - I would suspect something from either the Wise or IoBit stables, but it's not a symptom I've seen elsewhere.

Hi Noel.

Well you will want to slap me for this but... I have used a lot of "GUI" cleaning "tool" in the last weaks (I never use those on a daily basis but since I wasnt able to fix my corrupt system, I just allowed me to give a try... maybe I should'nt have.

Anyway here are some of the tools I've used recently :
RegCure Pro (by ParetoLogic)
SystemNinja
Advanced Uninstaller PRO
Revo Uninstaller Pro
Macecraft jv16 Powertool
CCleaner (with CCEnhancer) <-- I don't use their registry tool anymore... nor do I with any other tool
Little Registry Cleaner
adwcleaner
Junkware Removal Tool (JRT) by Thisisu
Rkill (by BleepingComputer)
TDSSKiller & rkill (live rootkit remover)
Some sysinternals tool like Sdelete
Simple icon fixer --> Téléchargements - Utilitaire - Simple Icon Fixer
Malwarebytes Anti-Malware PRO
JavaRa

wow looking at this list... it's a shame :S

 

[deleted01022019]

by the way.. Noel , Niemiro (im open to remote desktop sessions with you if you think taking a look live could help in the troubleshoot... just saying

 

[niemiro]

One comment, if I may?? (Please feel free to slap me down!)

The fact that the majority of the affected files are Desktop.ini files gives me the impression that some sort of system cleanup tool has been used, and it's ignored the ACLs, and broken the system fairly efficiently.

Can I ask what tool it was that was used? - I would suspect something from either the Wise or IoBit stables, but it's not a symptom I've seen elsewhere.

Really good spot Noel, I missed that. Thank you. What do you think about the C:\Windows\Installer folder as well?


@mrksys:
You C:\Windows\Installer folder has about ~50 files and directories in it, and I tend to use the approximate estimate that a system should have ~500. On top of those numbers, your system matches all the symptoms for an Installer folder corruption. I don't know what's caused it (but one of those many cleanup tools is a distinct possibility - BTW, do you know why I/many other experts would always recommend immediate discontinuation of their use? Have you read enough online now to know about this & not to use them again, or would you like me to discuss them a bit further?)

For a very brief rundown, registry cleaners are never wise. With all the millions of registry keys on a system, a couple of hundred deletions makes absolutely no difference. It will be a completely non-noticeable effect. On top of this, these tools, often produced by slightly suspect programming teams, compete for the most deletions, because that's how they sell themselves. The risk of a mistake is high (even with CCleaner, which has an amazing brand reputation but really is no better than the rest - and I've personally seen multiple systems crippled by CCleaner (along with many other tools too, but CCleaner is not really that much safer)), so you run a high risk with no benefit. Even just the *theory* of registry cleaning is unsafe.

What about registry defragmenting? Here, the *theory* is safe, as no registry data is being modified. However, the benefit will be minimal, and the number of times I've seen them go wrong.....
I would strongly recommend avoiding registry defragmenting, simply because of the risks of it going wrong.

Temp file cleaning though is beneficial and almost 100% safe. Don't become obsessive about it, but occasionally is a good thing here. The most important thing though is to find a tool that's safe and not overly aggressive (for example, deleting prefetch will initially cause a slowdown of your computer whilst it's regenerated, and has no long term benefit because Windows will clear out old stuff by itself - the only bits still there are the prefetch files still in common use, so why delete them?)

Disk cleanup's good: Delete files using Disk Cleanup - Microsoft Windows Help

Select only "Temporary files" in my opinion. Especially, it is my opinion that unless you are particularly short on space, not to run "Windows Update Cleanup". You will then lose your ability to uninstall a lot of updates, which can prove useful in some circumstances.

Probably run this once ever two months or something. Then if you want a deep clean, perhaps once every six months or so, I would recommend TFC: TFC - Temp File Cleaner by OldTimer - Geeks to Go Forums

Be aware that TFC's a bit more aggressive, it deletes temporary internet cache files and the like, but that's perhaps not a bad thing if done sparingly. It's a much safer/less aggressive tool than most others though, which is why I like it (and use it myself).


Back on topic, I would suggest going through each of those cleaner tools (BTW, I have never yet come across somebody with so many on one system, you hold that record ), look through their backups/logs, and see if you can find any C:\Windows\Installer files in the backups, or evidence for deletion in the logs. Sadly, most don't backup deleted files (otherwise no space is saved), but we can try......

Richard

 

[NoelDP]

The following are snake-oil at best, and snake-venom at worst...
RegCure Pro (by ParetoLogic)
SystemNinja
Advanced Uninstaller PRO
Little Registry Cleaner

The other vary between the very good (MBAM) and 'iffy' but generally OK (CCLeaner) - one (jv16) is a high-power tool best not used unless you know exactly what you're doing.