February 10, 2016

Yay, Microsoft

I wonder whether Microsoft has done something to the Update Server that makes it respond more slowly now to Win 7 users? I'm updating one of my computers now. It took 15 minutes to figure out what patches it needed. Total 251 MB. Ten minutes of downloading and it's only half done.

I bet Win 10 users don't see delays like that.

Posted by: Steven Den Beste in Computers at 03:44 PM | Comments (6) | Add Comment
Post contains 64 words, total size 1 kb.

1 I was upgrading an old notebook to Windows 10 a couple of weekends back.

After three hours waiting for the install process to find the latest updates, I wiped it and started the install again with updates disabled.

(Windows 10 isn't bad once you have it installed - certainly better than 8 - but the upgrade process is awful.)

Posted by: Pixy Misa at February 10, 2016 03:55 PM (PiXy!)

2 Ugh.  I much prefer 8.1 to 10.  Every time I've tried the upgrade to 10 it's broken things.  That'll be fixed eventually, but for the moment I've got the download and update blocked.

Posted by: Ben at February 10, 2016 04:12 PM (AoLFQ)

3

There is only one thing I hate about Windows 10, and it's enough that I haven't upgraded all my boxes to it yet: the forced updates.

"Restart Required-Click here to schedule restart for updates"  Fuck you, this is my computer and I'll install updates and restart when I'm good and damn ready.

It's like having a government computer at home.  It's the IT department's world, and we're all just squirrels looking for a nut.

Posted by: CatCube at February 10, 2016 07:18 PM (fa4fh)

4 It's only happened a couple of times, but sometimes Microsoft rolls out a patch that bricks a bunch of computers. With automatic update being mandatory, if they ever do that to Win 10, they are going to piss off a looot of people.

Posted by: Steven Den Beste at February 10, 2016 07:58 PM (+rSRq)

5

Another obnoxious aspect of this particular update is that once it's installed something called ".Net Optimizer" goes CPU bound, or nearly so, for about 15 minutes.

I'm running the update now for my main machine. It has four cores and they're all hyperthreaded. I wonder how bad it'll be?

Posted by: Steven Den Beste at February 10, 2016 08:55 PM (+rSRq)

6 They probably don't, but that's because Microsoft hasn't spent years releasing millions of patches for various architectures, bugs, and exploits for Windows 10 yet, and - the real catch - being forced to determine which patches you have installed, still need to install, and need to be suspended momentarily so other patches can be installed, all without sending any information about your computer to Microsoft (for which there are still a lot of watchdogs champing at the bit to sue the money out of Bill Gates the moment Microsoft gets caught doing anything that is clearly stated in the EULA).
Windows 10 gives itself a lot more latitude, especially since Microsoft is now buddies with the Obama Administration, and has been richly but quietly rewarded for it with legal favors for nearly a decade. This makes the process a LOT faster than having to first download the entire gigabyte-long list of all code variants for the patches you requested for every system architecture that has ever existed, have your computer check every one of them to decide for itself which one it needs and how it has to be applied, because some hardware is more difficult to patch than others, and some even requires a special process usually involving a reboot and changes to BIOS settings.

Posted by: Tatterdemalian at February 11, 2016 06:30 AM (4njWT)

Hide Comments | Add Comment

Enclose all spoilers in spoiler tags:
      [spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)

At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.

How to put links in your comment




What colour is a green orange?




10kb generated in CPU 0.0, elapsed 0.0145 seconds.
22 queries taking 0.0098 seconds, 25 records returned.
Powered by Minx 1.1.6c-pink.