Oct 31 2019 04:08 AM
Oct 31 2019 04:08 AM
Recently we have paused a quality update for Windows 10 because of an issue with one of our application. After that issue was solved we hit the resume button in the update ring in Intune.
I was expecting that as soon we resumed the quality updates, the pause period would be disabled on the devices, but we noticed on the devices that updates are resuming after the default period of 35 days and not immediately.
Is this normal behaviour?
Nov 09 2020 10:08 AM
Jan 26 2022 07:36 AM
Jan 26 2022 10:25 PM - edited Jan 26 2022 10:28 PM
Could you take a look at these settings
Maybe changing them to zero if these settings are still configure to 1 or 2? and if that ain't working
I would check out this key... as it notes the start time... maybe removing that key ?
Jan 27 2022 12:19 AM
Jan 27 2022 01:03 AM
@Rudy_Ooms_MVP Hi. That fix does actually work thank you, although I deleted the three entries instead of changing them because they weren't present on a few machines which didn't have this issue. The problem 'fixing' this is the large number of devices and the spread of them remotely. I'm tempted to try and push this reg change out via intune but I'm cautious of unknown consequences.
I just cant believe that without any prompts or warnings within intune, Microsoft has decided this is the behaviour for updates being paused and restarted.
Jan 27 2022 01:48 AM
Jan 27 2022 01:53 AM - edited Jan 27 2022 01:56 AM
Yes so on that path I deleted these
After doing that, hitting the 'Check updates' button goes off and downloads/installs the updates as normal. This has worked manually on about 5-6 workstations so far. Other than in one case so far I didn't have to restart the machine either, but that may have been a separate issue. Its not practical to do this remotely on all the other machines.
We are in a hybrid environment.
Jan 27 2022 02:21 AM
Jan 27 2022 02:29 AM
Jan 27 2022 04:02 AM - edited Jan 27 2022 04:03 AM
We paused and resumed the same day. Paused because of a Microsoft bug that broke vpn for our staff with Jan update. We then worked out a work around so resumed it a few hours later. Not all of the devices got hit with the pause, just most of them. Those that have an issue have those three reg entries, other devices without the problem don't have them. They don't have different values, they don't exist at all. There's a bug there somewhere that doesn't take that date away 'On resume' in intune, or at least not promptly enough. It's been nearly 10 days since resume and it's still on those devices.
Jan 27 2022 07:08 AM - edited Jan 28 2022 06:46 AM
Hi just wondering but on how many devices do you need to do this? You could use pro active remedaitiaons to check out the key... and if those exist... just delete them like you did?
Still need it test it more but...
Jan 31 2022 01:47 AM