This project has moved...
The same great solution that has helped thousands of users has moved to GitHub for ease of management. See you there!
Related Articles
This project has moved...
The same great solution that has helped thousands of users has moved to GitHub for ease of management. See you there!
Related Articles
* Please try a lower page number.
* Please enter only numbers.
Glad this guide was helpful.
Unfortunately, this didn't work for me. Stage 3 started checking for updates, on my computer, and ran for 12 hours before I finally decided to kill the process. I have been working on this problem for weeks, trying the above and others (Fixit50123,sfc and various KBxxxx.msu), but nothing works. Every KBxxxxxx.msu I try gets stuck "checking for updates." Even after two completely clean installs of Win 7 x64 I cannot get Update to run and my DataStore.edb rebuilds itself to a massive 976MB. I need a more aggressive fix.
This is a very aggressive fix; in fact, the most aggressive that I know of. Did you follow the article carefully, in order?
Deleting the SoftwareDistribution folder and running the Fix-It will enable the any KBxxxxxxx that you download to install correctly. Also, before running any KBxxxxxx, try checking the service statuses as noted above.
Thank you!!
I tried may things for 5 hours before I meet you...
It works.... very well...
Unfortunately, this didn't work for me. Stage 3 started checking for updates, on my computer, and ran for 12 hours before I finally decided to kill the process. I have been working on this problem for weeks, trying the above and others (Fixit50123,sfc and various KBxxxx.msu), but nothing works. Every KBxxxxxx.msu I try gets stuck "checking for updates." Even after two completely clean installs of Win 7 x64 I cannot get Update to run and my DataStore.edb rebuilds itself to a massive 976MB. I need a more aggressive fix.if you use kb3102810 do it network unplugged, because the "fix" trigger windows update agent which for whatever reason will try to connect to microsoft update server and then... trigger the dreaded loop.