![]() However, installing it manually on both of the above mentioned computers did nothing for reducing the length of time they would sit there "checking for updates".ĭoes anyone here know what actually causes this and how to fix it? It's extremely frustrating when a simple re-install that should only take an hour or two takes nearly a whole weekend.Įventually both machines must have found an update that fixed the problem, because "checking for updates" times would drastically drop from hours to about 10 minutes. Lots of tech support forums reference patch KB3050265, which is supposed to address this exact problem. During this time, there was little-to-no hard drive activity, so it was tough to tell what the hell it was even doing. The first time I saw this, I thought the update manager had crashed or locked up, but upon further investigation I discovered that wuauserv was churning away and slowly gobbling up system memory. After that, the computer just sits there "checking for updates" for hours before finally returning an install list. Upon first startup of the OS (and after installing a network driver where necessary) I fire up Windows Update and begin a manual check. I've encountered this problem twice in past three months on two freshly installed, legitimate copies of Windows 7 w/ SP1. ![]() ![]() I feel like this question is asked on every online forum in the world, but every "solution" I find always reads like some crackpot's holistic cure for the common cold. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |