New
#51
I did uninstall. It'll BREAK my system? Ok please tell me about CC Cleaner which I use religiously.
Need Help for update KB947821/80240016
-
-
New #52
CCLeaner is fine - so long as you DON'T use the registry cleaner!
Please tell me which updates are now failing, and with what error code?
-
New #53
The registry cleaner is the ONLY feature I use with CC Cleaner. Please explain why it's bad. How else could I fix the unused things that are left in registry ... besides manually? Are these things really not problems at all? I always wonder if a product is really doing what it says it's supposed to do or if it's a sham.
The only update failing is the KB2631813. The error code is 8024200D
-
New #54
My earlier response seems to have 'got lost in the post'!
ALL registry cleaners run the risk of removing links in the registry that are required. VERY few actually do anything except test for dead-end links, and almost none test to see whether a link is actually going to the right place (simply because that's an almost impossible task - there may be many valid places for a registry link to go, but only one will be right at any given time, and that may change depending on settings in and outside the registry).
There is no size problem with the WinXP+ registry - unlike the Win9x registry which did have some severe size limitations. The size of the registry is almost irrelevant to the speed of a properly running machine - although it may make thre or four whole seconds difference to the boot-time! :)
Registry 'fragmentation is pretty much an urban myth - the registry is a compressed file held in memory, and may display lots of space in a regedit window or other display, but there ain't none in RAM!
A perfect - or even very good - 'Cleaner' would need to have detailed knowledge of every bit of software that is (or even might be) installed on a given machine. Such knowledge would have to be updated daily - and would probably be a database bigger than the OS itself!
In short - they ALL tend to create more problems than they solve in the long term.
MS12-004: Description of the security update for DirectShow: January 10, 2012
Please run the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)
Then zip the CheckSUR.log and CheckSUR.persist.log files and attach it to your reply.
The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
-
New #55
0x8024200D is usually solved by installing the update from the web :) But a CheckSUR log never hurts.
If your computer is 32 bit (x86), download and install this: Download: Security Update for Windows 7 (KB2631813) - Microsoft Download Center - Download Details
If your computer is 64 bit (x64), download and install this: Download: Security Update for Windows 7 for x64-based Systems (KB2631813) - Microsoft Download Center - Download Details
Tom
-
New #56
Noel, nothing personal but I tried Tom's fix first becuz it was the easier one. I'm all set now! The stubborm update is now updated. Thank you for sticking with me for all this time and explaining some things to me!
After it installed, I unhid the problem update (I wondered how that install would effect that hidden file) and manually checked for updates and it told me that everything was updated!
Tom, big thanks for the help!
-
-
Quote
But you're welcome nonetheless.
Related Discussions