Nov 14 2019 06:53 AM Show @Ronald Meer I'm seeing the same behavior when pausing Feature updates, I assumed it would resume immediately but it hasn't. Nov 06 2020 03:10 PM - edited Nov 06 2020 03:11 PM @Ronald MeerI´m having the same issue. I´m thinking about creating a new policy. Nov 08 2020 03:51 AM @Dan18539 After you resume updates the updates will continue after the default period of 35 days. Nov 09 2020 10:08 AM This makes the Resume button functionally useless. If not resumed, it automatically resumes after 35 days. If resumed, it waits till day 35 to resume. Is this working as expected right now? Nov 09 2020 11:54 PM @thedrum808a If you do not hit the resume button. Updates will be paused indefinitely. Oct 19 2021 10:24 AM How do 35 days count? Since the day you paused it, or 35 days from the time you resume it? Jan 26 2022 07:36 AM This is an old post but I'm having the exact same problem. We paused updates to stop a buggy Update from Microsoft coming down and breaking our VPN, and now resuming it we find all the devices stuck and refusing to update because it's 'paused by the organisation' even though we've resumed updates in the ring. So we are now stuck with devices out of date and unable to update. Where was the thinking within Microsoft that thought that was a good idea? When resumed, they should resume not continue to be paused for over a month. Is there a work around or a way to make updates resume? Jan 26 2022 10:25 PM - edited Jan 26 2022 10:28 PM Hi Could you take a look at these settings I would check out this key... as it notes the start time... maybe removing that key ? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update Jan 27 2022 12:19 AM I'm having similar issues after resuming the updates in Intune, but only my Hybrid Azure AD joined devices. Our Azure AD joined devices are not exhibiting this behaviour. I am wondering if this is a hang up of old AD GPOs still on the device. 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 Hi, Just curious but which of the registry keys did you deleted? Sounds like a proactive remediation to me... Jan 27 2022 01:53 AM - edited Jan 27 2022 01:56 AM Yes so on that path I deleted these PauseQualityUpdatesStartTime 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 Hi.. I guess I got some content for a new blog :p ... When looking at those registry keys... were there values in it after you resumed the updates or were they empty? Jan 27 2022 02:27 AM Just checking now on one device and they don't seem to have come back. Jan 27 2022 02:29 AM When you first pauze those updates it will add a date in the PauseQualityUpdatesStartTime value . I am wondering if those are also empty or still configured. 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 Jan 27 2022 08:36 AM It's around 130 and they are 99% off premises. Jan 31 2022 01:47 AM Hi Just read your blog based on this issue and answer. Could you tell me where in intune you are putting the detect and remediation scripts? What type of intune configuration is it? How do I force Windows Update through Intune?In the admin center, go to Devices > Windows > Quality updates for Windows 10 and later and select the policy that you want to manage.
How do I get rid of Intune device managed?Remove in device Settings app
Open the Settings app. Go to Accounts > Access work or school. Select the connected account that you want to remove > Disconnect. To confirm device removal, select Yes.
How often does Intune check for Windows updates?Client-based data from Intune devices that are configured to send data to Intune – This data is processed in batches and refreshes every eight hours, but is only available after you configure data collection. The data contains information like when a client doesn't have enough disk space to install an update.
What is deferral period of quality updates with Windows Update rings Intune?The deferral period begins when Microsoft releases the update. Supported deferral period: Windows version 1709 and later - 0 to 365 days.
|
