Microsoft updates the Windows Update Experience: You can hit pause now

Microsoft has devised a solution to the problem of Windows Updates that break customer devices – users are now able to pause them for as long as they like. In a post at the end of last week, Aria Hanson, a principal product manager lead at Microsoft, described "improvements to the Windows Update experience" that were rolling …

[Jou (Mxyzptlk)]

So now we have a choice!

Between being fucked or getting fucked?

[Excused Boots]

Re: So now we have a choice!

Subtle difference, but an important one.

[David Hicklin]

Re: So now we have a choice!

Now all they need to do is to make the fixes individually selectable and we will be back to where we were.

Only still missing the QA of course !

[chivo243]

Shortly?

shortly after they are released? I usually waited 8 days. Plenty of time to see if others report issues, and test before deployment. I remember denying quite a few updates in WSUS thanks to El Reg reporting issues.

[cd]

Been able to do this for decades, simply by not using their products.

[Pascal Monett]

Why are you commenting here ?

Don't you have some Linux feed to contribute to ?

Or are you just masturbating to your pseudo superiority ?

[Anonymous Coward]

For decades now, Microsoft's marketing strategy has leaned heavily on making people think they don't have other options while elevating fears of the unknown held by potential switchers.

Classic example of manufactured consensus. Certain situations are Windows-only. Most aren't. The number of Windows-only things is falling with each passing year.

We switched out a lot of our backend to make BYOD a thing. It results in higher user satisfaction, and with the Macs, many fewer tickets. BYOD fans are usually pretty serious about their choice, and a lot of that comes down to Windows suckage. The main driving factor was a productivity gap: a device (usually a laptop) which someone only wants to touch for work is frequently left behind. Commissioned employees do better with devices they have readily available for when opportunity knocks. When the Microsoft device sucks so bad that a lot of people don't want to touch it unless they have to, that becomes a problem for management.

One could list 100 examples of toxic Windows behavior which can only be fixed by switching (or occasionally, hacking your system at great time expense for no guarantee the fix holds).

[Doctor Syntax]

Why are you commenting here ? etc

The fact remains that Linux provides an example of how to do updates unobtrusively. It has provided that example for many years now. It is inexcusable that Microsoft hasn't looked and learned but has, instead, trained its users to accept clunky updating as just an inevitable aspect of running a computer and that granting some user control over its intrusiveness becomes a news story.

[NapTime ForTruth]

Pseuperiority, surely.

[Anonymous Coward]

Pshirley shirley ?

[Gene Cash]

Yeah thanks, buddy boy...

I run Linux at home, but I'm paid to put up with Windows at work.

Frankly, my dear, I don't give a damn. If Windows scrags itself, I still get paid while someone else sorts it. If they want more productivity, they can give me a real OS.

[CA Dave]

This isn't quite the flex you think it is.

[Antron Argaiv]

Ahh! The "Windows Update Experience".

End of the work day, time to head home. Shut down the PC...what's this? "Don't turn off your PC, Windows is updating"

F*ck. Hope they hurry or I'll miss my train.

Yeah, not one of their brightest moments. So glad I'm retired.

[Those who don't want to hear about Linux may stop reading here]

I get a little red dot in the status panel, telling me I have an update available...which I can examine before installing. Unless it updates the kernel, no restart is required, and even if one is, I have a choice of when to do it. How hard is this, Microsoft? If a bunch of scraggly hackers, led by a penguin, can manage to build a decent OS, why can't you?

[AndrueC]

End of the work day, time to head home. Shut down the PC...what's this? "Don't turn off your PC, Windows is updating"

F*ck. Hope they hurry or I'll miss my train.

Why would you miss your train? Windows doesn't require you to hover over the update process like a mother hen. Just leave the office and let Windows update itself then shut itself down. It even works with a laptop - just close the lid and leave it to update itself because it won't enter sleep if it's updating.

Now granted the PC might not work when you reboot it in the morning but that's a different problem :)

[AndrueC]

Update: The plot thickens and becomes unclear. Like Windows itself :)

A laptop that supports S0 (Modern Standby) will definitely not care if you close the lid during an update. S0 isn't really 'sleep' it's just power save mode and all manner of tasks can and will start, stop and continue to run as the OS sees fit. Windows Update can not only continue during S0 but can actually download and install updates during S0.

There are still laptops around that don't support S0 though. The one I'm currently typing this on is an example. I've mentioned it before - it's a seven year old HP that is happily running Win11. Now I can't currently find anything definitive for S3 and Windows Update. If the laptop does enter S3 the updates will be paused because S3 is 'turn everything other than RAM refresh off' and ain't no task going to run in that mode.

But I also know three things for sure for my laptop:

* The laptop can bring itself out of sleep and install updates all by itself. This doesn't surprise me - presumably Windows Update just creates a task that wakes the laptop up at some point.

* If I close the lid after the update process starts that process will complete. The computer will need to be manually started afterwards (ie; opening the lid doesn't cause it to boot up it up like it normally wakes from sleep) but the update will have been applied. So this suggests that Windows Update is capable of blocking sleep in order to let it finish what it's doing.

* Sometimes after an update that didn't require a restart this laptop will appear not to have entered sleep. The login window will appear far more quickly than when it's coming out of sleep. So I think this confirms that Windows Update can block sleep- at least on this HP.

[Jou (Mxyzptlk)]

Try those two... Suspend (first $false = no wait, second $false = allow wake up events. The second $false option is actually "Disable Disable Wake Up Events", typical Microsoft like group policies):

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Add-Type -AssemblyName System.Windows.Forms;[System.Windows.Forms.Application]::SetSuspendState('Suspend', $false, $false)"

Hibernate works without powershell:

C:\Windows\System32\shutdown.exe /h

[Antron Argaiv]

Well, if I close the lid and walk off, the laptop loses internet. Does Windows need internet for this update? Who knows? Is this (employer supplied) laptop one of those that you can do that successfully with? Has Corporate IT configured it so updates will work if you close the lid and walk off? Who knows?

One of the things I have learned through years of working with Windows as a user, is: don't do *anything* that might disturb it when it's modifying itself. Yeah, it's *supposed* to be OK, but just because you got away with closing the lid and walking off, and it successfully finished the update last time, doesn't mean you won't be confronted with a borked machine when you open the lid again *this* time.

And if it's so smart, how come Windows can't do its updates in the backgound? And as long as we're wishing, revert if it fails, and try again? Ever get anything helpful when you reply "yes" to the question about Windows helping you to resolve some problem? Me neither.

Anyway, not my problem any more. Retired, and Windows is almost entirely a thing of the past for me.

[Jou (Mxyzptlk)]

> One of the things I have learned through years of working with Windows as a user, is: don't do *anything* that might disturb it when it's modifying itself.

That is universal. There is no OS liking this. Literally none.

[CA Dave]

This doesn't make sense. You could click Update and Shut Down in the power menu, or lock it down and turn off the monitor. Then just go home.

[Erix]

It kind of does when you have a company laptop you have to take with you. Your options at the end of the day:

(a) start the update, wait, waste your time (it will always take longer than the estimated time) and maybe miss the train

(b) start the update, close the laptop, pack up and risk it melting down in your backpack

(c) suspend or hibernate (if allowed by admin) and be faced with the same choice tomorrow

None of the options sound like fun when you're about to knock off...

[Antron Argaiv]

This guy gets it.

Several times I have opened my backpack at home and found a very warm laptop with a dead battery. Guess I closed the lid and walked off too fast...

[Jou (Mxyzptlk)]

Add the obvious "rolling back update, please wait" here...

[DJV]

I'll just leave this here:

Windows Update Blocker

[chivo243]

Re: I'll just leave this here:

The last point is good: https://www.makeuseof.com/best-windows-registry-tricks-worth-trying/

Stop automatic Windows updates

Update on your terms, not Microsoft’s

I don't mind mucking about in the registry.

[VBF]

Re: I'll just leave this here:

Been using something similar on 4 PCs for the last year - especially when I take my travel laptop away with me and don't want to fight with an errant update on holiday!

I think this was originally on MUO but just pauses updates for any amount of time you choose:

Windows 11 pause update delay

Modifying the Windows Registry

This method allows for a longer than standard pause, potentially for years, by changing a specific registry value.

1. Open Registry Editor:

2. Navigate to the Key:

In the Registry Editor, go to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings.

3. Find or Create the Value:

Look for a value named FlightSettingsMaxPauseDays. If it doesn't exist, right-click on the Settings folder, select New, then DWORD (32-bit) Value, and name it exactly FlightSettingsMaxPauseDays.

4. Set the New Value:

Double-click FlightSettingsMaxPauseDays and change its "Value data" to a significantly higher number, such as 365 for a year, and select Decimal.

5. Restart your PC:

After making the change, restart your computer for the new setting to take effect. The Windows Update settings page will then reflect the extended pause period.

[Anonymous Coward]

Re: I'll just leave this here:

It's unfortunate that this has to exist like so many of the other Windows hacks, from going without a Microsoft account to stamping out advertising and telemetry.

Windows is loaded down with so many antifeatures that it creates a real time burden for people who think their device belongs to them and should work how they want.

But it's not just the time burden. It's also the feeling of needing to be on constant patrol to make sure no antifeatures slip past when the user is doing something better than having to police their own system. And then there's no guarantee something won't slip past and only make itself known once the problem has started (or the data has already been exfiltrated).

[Matt Collins]

A step backwards

Admittedly not from a great place, but I know people who will just keep punting it down the road... and then one day get bitten hard

[Anonymous Coward]

Re: A step backwards

This, the frequency isn't the problem...the clunky stone age mechanism that exhausts your CPU that makes your machine unusable is.

[Matt Collins]

Re: A step backwards

Another problem is the requirement to reboot. People don't want their working state lost - yes, there are some programs that restore their state, but many don't. I find it odd that Microsoft have reportedly just introduced a mechanism to avoid many of the reboots and now this???

[notyetanotherid]

Re: A step backwards

And having a setting for "Notify me when a reboot is required to finish updating", which is studiously ignored when set to "Off", so all those Windows-based signage displays have a big reboot prompt obscuring part of the screen every few weeks.

[Kerfufflinator]

Wait, is this really new? I thought you could already stop them indefinitely or for a period of time...

[jdiebdhidbsusbvwbsidnsoskebid]

Not indefinitely but in Windows 10 you could pause them for a while - 35 days sounds familiar to me. This sounds just the same. I hope noone at Microsoft spent much time on this "enhancement".

[Kerfufflinator]

Actually yeah, you're right, it's up to 35 days, there is no indefinite option. But setting active hours is a thing. And I am on win 11, without this latest update.

[ThatOne]

> Not indefinitely but in Windows 10 you could pause them for a while

My laptop came with Win11 and it has always allowed to pause updates for a while (didn't check for how long, since I don't use it (Win11 that is, not the laptop...)).

That been said, what would had been really convenient, would be to be able to give it a weekday (like "Saturday") and a time (like 3 o'clock in the morning) to do its updates...

_{I have a vague recollection that old Windowses did indeed work like that. Oh well, everything was better back then...}

[frankyunderwood123]

update permanently…

… by removing windows.

It’s been a year since my last windows install was removed from my dual boot linux gaming rig and 14 years since it was my primary OS.

Luckily at my workplace I’ve been using macOS since 2013.

This I’ve found to be the most effective way to update windows for me personally, I’m sure others have similar successes at updating windows…

[Bebu sa Ware]

Pox Tuesday…

"O frabjous day! Callooh! Callay!"

Windows victims may now choose the day of the week or indeed of the month on which Microslop is invited to bugger their devices.

That this facility has been made available suggests a line has been crossed and something has snapped within the slop factory. The loss of skills and failure of slopatronics to replace those skills probably means situation is now irretrievable.

[Blackjack]

So basically they are giving the users the choice BACK of picking if and when to update like in Windows 7? That's good now how a about a turn off button for Copilot?

[Roland6]

>” now how a about a turn off button for Copilot?”

Prefer an uninstall all button, paired with a “no reinstall” tickbox.

[Pascal Monett]

"These improvements are the direct result of your feedback"

So, said improvements are not the result of your efforts to improve the quality of your output ?

Yeah, didn't think so either.

[Anonymous Coward]

No no no no...they have totally misunderstood the problem.

The problem updates happening at weird times, the problem is the update mechanism is crap. Updates shouldn't interrupt you whether they're running or not. They should be transparent, they shouldn't bring your system to it's knees and they shouldn't be all up in your face like a crack infused Jack Russell. They should be quick, out of your way, but still happening.

I think Microsoft execs need to take some of their money and go to a fine dining restaurant and observe how the waiters operate. That's how a good update mechnism should work. Always present, always attentive, never interrupting your dinner, always out of your way. Seamless.

Instead they seem to have taken the Swiss Tony approach to updates.

Windows Updates are like making love with a beautiful woman, first you surprise her when she steps out of the shower, throw her over the bed, give her 30 minutes to an hour of intense activity, occasionally slapping her round the face whilst calling her a bitch.

[Anonymous Coward]

Updates shouldn't interrupt you whether they're running

Just look in the Windows Update gorup policies. And if they are set by your sysadmin, and they are wrong, the problem is not Windows, is your sysadmin.

My systems are set to let users who know what they are doing install updates when they are ready. Usually at shutdown - but that can be deferred to if needed.

Windows can also wake up and install updates when the PC is not in use - but one size doesn't fit all, and someone has to configure updates as needed.

But since the average sysadmin is usually lazy, they won't do their work, and won't change defaults, that has been changed to update early.

[Anonymous Coward]

Re: Updates shouldn't interrupt you whether they're running

"My systems are set to let users who know what they are doing install updates when they are ready"

Sure, but this is not permitted if you are forced to abide by certain levels of stupid cybersecurity compliance. Especially if you want to handle certain kinds of contracts, work with certain moronic customers etc etc...there is a lot of ringpiece sniffing that goes on when contracts are being negotiated and compliance is one of the shortcuts to getting that done and dusted quickly.

"But since the average sysadmin is usually lazy"

I think we can give sysadmins a pass on this one, Windows Update is objectively shit, no matter how you configure it or what policies you have set...and most of the time the way Windows Update is configured for an organisation is defined by their level of compliance, not what a sysadmin would like to do.

Also on the subject of laziness and sysadmins, one of the core tenets of systems administration is to follow "least administrative effort" when it comes to configuration and maintenance...for several reasons. Firstly, efficiency...that one is obvious...secondly, security...because least administrative effort means less human error, smaller attack surfaces (because less opportunity to take advantage of a sysadmin in the middle of something etc)...and also it reduces costs because complex custom configurations are usually much harder to audit and verify, takes more time and therefore makes compliance more difficult therefore more expensive.

A good sysadmin is a sysadmin that makes the fewest moves. Systems administration is not Minecraft, you're not building a world to reign over...it's Chess...it's all strategy and rules.

The best changes any sysadmin can make, are the ones they can avoid. Never confuse a sysadmin that chooses to do nothing with a sysadmin being lazy. It can happen, but it's not as common as you think.

Finally, don't confuse systems administration with user support...sysadmins are not Tron, they don't fight for the users. Sysadmins are there to manage and maintain the system. The desktop boys can deal with all the shit from Barbara in accounts...that's not my job, that's a conflict of interest.

[mw_foot]

Hotpatch

Microsoft are trying to get away from reboots via hotpatch.. Its a shame you need a licence which means home users are shafted.

Last months Cumulative Updates seems to not like WSUS at all.

Given that WSUS is deprecated I’m

not surprised.

Pausing updates can be problematic when Cyber Essentials wants you patched up in 14 days.

[Ken Hagan]

Re: Hotpatch

"Pausing updates can be problematic when Cyber Essentials wants you patched up in 14 days."

If this is one of the updates that borks your system, why not just classify it as malware, rather than an update? Does CE want you to apply viruses within 14 days of their appearance in the wild?

(And if it doesn't bork your system, 14 days is probably long enough to discover that.)

[Excused Boots]

Re: Hotpatch

Cyber Essentials is a box-ticking exercise. And yes they really aren't bothered whether or not the ‘update’ borks your system enough to put you out of business, you ‘patch’ your systems within two weeks of the update being released, yes/no? Because that is their criteria for compliance.

Just lie, everyone does.

[herberts ghost]

Good IT governance is to NEVER take an update until you have had time to hear the screams of people with auto update.

This is a must in businesses like banking.

Such pauses should be mandatory for all vendors everywhere, but especially Microsoft, which seems to be more of a drsk than intruders. (Thankyou MS marketing).

[RockyKoer]

RockyDog

As 25+ years Windows user, I paused my updates this year by switching to ZorinOS. What took me lo long!?!?

[[e-mail]]

It is awkward.

Windows Update Experience is more like a Colonoscopy Experience than anyone wants to think about.