New
#31
As a matter of fact after reading this I went to my Pro machine on 1903 and indeed the options are gone. I had set the data to 7 and 7 (features and quality updates).
So this is a bug.
As a matter of fact after reading this I went to my Pro machine on 1903 and indeed the options are gone. I had set the data to 7 and 7 (features and quality updates).
So this is a bug.
Thanks for confirming it. I was beginning to think it was only me.
Same here
I did a clean install, altered the feature update to to 365, now that option is not showing and only the quality updates are available ! (i suspect that would go to if i tried to apply any number at all to it)
The problems seems not to be the update to 1903, but something inherently wrong with 1903.
So far as the ISO is concerned, why not make a USB installer that way you wont have to download it again, and you can use it for both upgrades and clean install ?
Though you can still set them via Group Policy but then you get the option box back, but is greyed out.
Windows 10 1903: the case of the missing update deferral options - gHacks Tech NewsDeferral options are still available in the Group Policy. Tap on the Windows-key, type gpedit.msc, and hit the Enter-key to launch the Group Policy Editor (professional versions only).
Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business.
There you find "Select when Preview Builds and Feature Updates are received" and "Select when Quality Updates are received".
Using Regedit set 'DeferFeaturesUpdatePeriodInDays' or 'DeferQualtyUpdatePeriodInDays' back to zero in the following key
HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings
This will make them visible again (after another 'check for updates').
The contents of these Windows Update settings pages are only refreshed when you check for updates, either the automatic check or manually. Set a number of days then check for updates will make the option(s) disappear straight away.
Courtesy of Bree
Last edited by Intrepid1; 25 Sep 2019 at 22:19.
Yes and thank you. Added Courtesy to post. Just spreading the word to prevent people from doing a reinstall when I came across the issue...
OK, I tried to post it on all relevant threads, but must have missed this one.
Annoyingly, the word doesn't seem to have got through to Microsoft yet, they STILL haven't acknowledged this bug even exists. There are (to my knowledge) at least three reports in the Feedback Hub by now (see this post and the two following). The more people who upvote one, the sooner MS will acknowledge it exists and get round to fixing it.