Reasons to hate Windows, volume whatever

[womzilla]

So Windows was nagging me to install the latest security upgrade--an upgrade for Internet Explorer 6, which I --almost-- never use. Rather than tell it "forget about this update", I figure that --almost-- is reason enough to get take the update even though I know I'll have to reboot my machine afterwards. (If a Windows Update requires a reboot, a popup window will nag you every 15 minutes until you reboot.)

So, I take the upgrade. I reboot my machine and walk away. Five minutes later, I come back... to discover that I had somewhere along the line scheduled "on the next restart" a disk scan for my secondary internal hard drive, D:. Argh--can't use the computer until that's done. So I do some tasks around the house, figuring it will be done in an hour. I check back in... and it's also running a chkdsk on my 500 GB external hard drive. On which I ran a chkdsk less than a week ago.

The whole escapade kept me away from my computer for over five hours, time when I really wanted to be working on Tales of the Arabian Nights. Argh! Argh! ARGH!

Anyway, it's back now. But geez.

Comments

[cattitude.livejournal.com]

Come! Join us on the Linux side. It is your dessstiny.

[womzilla.livejournal.com]

Every year Microsoft makes that decision easier....

[montoya.livejournal.com]

1. I have never had that disk scan thing occur. If that's something you configured yourself, it seems silly to blame Microsoft for it. NTFS is a resilient filesystem, and there's no neeed to be running scandisk that regularly.

2. When Vista needs an Update-inspired reboot, you can have it delay for 4 hours instead of just 15 minutes.

[womzilla.livejournal.com]

I had a minor crash on the external drive last week--that's why I ran chkdsk on it then. Without intending to, I apparently set the "run a scan when the machine reboots" flag. But I know that I rebooted while I was trying to run the chkdsk last week, so apparently just rebooting and running chkdsk wasn't enough to un-set the flag several days ago.

The other reason to be upset at Microsoft specifically was that I could find no way I could abort the scan short of power-cycling the machine, and I wasn't sure that wouldn't cause serious problems on the disk.

[filkerdave.livejournal.com]

I loaded WinXP SP3.

It took 2 days to get the machine in some bare semblance of booting up again.