Card on fire

[Walter Bright via Digitalmars-d]

On 7/15/2016 12:16 PM, Meta wrote:
> On Friday, 15 July 2016 at 05:10:29 UTC, Walter Bright wrote:
>> I'm excluding the pain of Windows reinstall, as it took 14 hours of sitting
>> there blankly "checking for updates". I wonder what it was possibly doing that
>> took 14 hours (the disk was fresh, there was nothing to transmit to the NSA).
>
> It's a known Windows issue:
> http://www.infoworld.com/article/3069693/microsoft-windows/windows-7-update-scans-taking-forever-kb-3153199-may-solve-the-problem.html

The article is full of "seems to work", "may work", and "some say it didn't work".

You'd think Microsoft could attach a debugger to it, figure out exactly why, and 
fix it. It's staggering how this goes unnoticed and unfixed.


> I had the exact same problem after reinstalling Windows 7 a few months ago.

I've had the problem every time I reinstall Windows 7, on different machines. I 
learned that you had to disable it going to sleep when doing this, else it will 
never ever complete.