Hello i would like to bring something to your attention. I’m not sure if this has already been reported.
Now… Using the latest version of CSC i figured this out 100% for myself i tested it and everything your free to test it if you dont think its true everything i run it everything checked full clean all box’s checked prefetches ETC… now after the restart 2 new optional windows updates come back like it may have erased importent system files and it wants me to reinstall the updates… updates include…
Windows Media Player 11 (for Windows Media Center Edition 2005)
Update Rollup for Windows XP Media Center Edition 2005 (KB925766)
K now of course there is a solution on the windows update help site i follow the directions…
Tells me stop the windows update service and delete temp files in software distrubution folder then everything works… but its just annoying i have to do this everytime i run CSC!?
If you checked everything, this also means Prefetch Application Cache and Filter Entries, and by checking these options you receive a warning message : “By checking this option your operating system may be affected. Use it at your own risk !” for Prefetch and “Some applications that are related with filter entries could be damaged! Use it at your own risk!”. This means that those options are only for advanced users who can select what to clean form the scanning results list, as they see fit. If you don’t know exactly what will be cleaned using those options, leave them out of the selection for scanning.
The problem I ran into on two laptops, one running XP Home SP3 and the other running Vista Business SP1, is that the warning message for Filter Entries DIDN’T come up because Filter Entries was checked by default after updating the program from within from the previous version. It was supposed to be unchecked by default, but it wasn’t. This has to be a programming flaw because it has happened to me on two different computers now, both running Office XP. This problem of Filter Entries being checked by default did not happen when updating to the latest version from within the CSC program on our two Vista Ultimate desktops running Office 2007.
If the user doesn’t pay close attention and just goes by what the release notes say, they will learn the hard way when certain programs such as Microsoft Office XP, require reinstallation of a feature when an Office program is first opened after CDC cleaning. After discovering this flaw, I unchecked Filter Entries, and then when I rechecked it is when I did finally get the warning message “Some applications that are related with filter entries could be damaged! Use it at your own risk!”. Filter Entries being checked after updating from within the program apparently does not always happen. But it should not ever happen, because you think you are safe when cleaning with CDC, but then you find out that you are not because something was checked by default that wasn’t supposed to be.
We tried every possible scenario , with options checked by default and then all options selected in Disk Cleaner, and there weren’t any windows update problems, or errors reported after cleaning with CSC. Please post ( attach ) your CDC and CRC log files so we can analyze them.
The second log belongs to CSC, we need the CRC log which is located in Program Files\Comodo\System Cleaner\crc.log. You could attach the file to a message you post, no need to post the entire log here.
In the CDC log please observe the section with the results after scanning, which cand be found only if you check Prefetch Application Cache, and most important the line "[ 10.05.09 16:19:45 ] C:\WINDOWS\Prefetch\WUPDMGR.EXE-2F30BEAB.pf ". As I told you in my first response, by checking these options you receive a warning message : “By checking this option your operating system may be affected. Use it at your own risk !”. So after scanning Prefetch files you have to know exactly what to select for cleaning and what to clean, otherwise you will find yourself in situations like these. That was a Windows Update Manager related file “WUPDMGR.EXE”, which after deletion probably caused that scenario with those 2 updates. The purpose of the warning messages is to avoid issues like that and those options are only for advanced users.