Windows 10


The SSD issue with the Anniversary version seems like a good marketing tool for saying YES to “forced updates”, or?


Almost glad that the update’s repeatedly failed on my PC now, lol :P


Is that article suggesting that just having an SSD is causing issues with the anniversary update? I have 2 SSDs and a data drive on this machine, and 1 SSD and a data drive on 2 more PCs in this house, AND I moved my two laptops to SSDs. All are running Windows 10 and only the laptops haven’t been updated yet to anniversary edition. Clearly there is more to it than just having an SSD. As they say in the article:

Our question is this: given that the Anniversary Update has been available for months via the Windows Insider programme, how does something as significant as this sneak through to the stable release?

It didn’t “sneak through”. There is something else going on.


What SSD issue? I’ve installed it on 5 computers with SSDs, and I’ve had no issues whatsoever.


This one:

Edit: oh phooey, Bal’s link didn’t come through. This:


Awesome, it hits some people with SSD C:\ and programs on separate drives, and it happens some time after you update. So it could happen to you, or me, at any time, just a giant “fuck off, will you?” from out of nowhere. Looking forward to that.


You know, in IT the golden rule is never run bleeding edge, ‘n-1’ FTW.

MS comes along with Win10 and says ‘fuck you, you will have our patch when we tell you, whether you like it or not’. Then shit fucks up for a bunch of customers. Who’s surprised?


There’s nothing stopping people - especially IT admins - from deferring upgrades like this or even controlling the updating schedule entirely just like they always have.

For ordinary consumers who don’t change any settings, most haven’t even started getting the update yet since it’s rolling out very slowly, especially to help catch issues like this.

So the biggest audience of people being hit by these bugs? People who are deliberately seeking it out by opening the update page and manually installing it or even getting the Upgrade Assistant tool to force it sooner than Windows Update is offering it to you.


This forced upgrade thing is awful. I never took these big updates as they rolled out… now I get the update whenever MS feels I must take it.


I got the upgrade prompt yesterday. My immediately apparent options were to either install then and there, or defer to some time no more than 48 hours later.


In Settings there’s a “defer updates” toggle you can enable at any time before updates are detected. But yes, once your PC has downloaded and prepared it for installation, the only thing you can do is delay the restart.


From what I read when I enabled, defer updates gives you a roughly quarterly update? I got prompted to restart the day after Anniversary went live and I was surprised when it was some unrelated patches.


Defer Updates still allows the monthly cumulative updates to come through, but it delays the feature updates like 1511 / 1607. Don’t recall how long though.


I wonder if the bluescreen issue 1511 introduced for me has been fixed yet.

OTOH, I will never know, because I cannot have the DX stack bluescreening my machine.


Ed Bott has written instructions on how to completely turn off Cortana in Windows 10 Anniversary Update. You now need a registry hack as there’s no longer a UI option for that.


One of the main reasons why I am not running Win 10 and still have a working OS basically…


I recently started using Windows Update MiniTool and strongly prefer it. It’s essentially a GUI shell around the built-in powershell update commands, so no funny business here.


Lots of words about DPI scaling improvements in the anniversary update, along with an acknowledgement of what they plan to improve next:


I still can’t figure out why MS doesn’t use Apple’s solution; render up to a very high resolution, then scale back down to native DPI. Yes, it wastes some GPU cycles but it always works and looks pretty good.


That’s…not how it works. Think it through.

The “render up to a very high resolution” is the problem Windows applications face in the first place. Old applications which don’t properly tie into the high-DPI hooks the OS offers, combined with some limitations in the OS itself which weren’t addressed until the anniversary update that the blog explains.