Windows 10: Windows 10 1703 to 1709 Defer Feature Updates Registry "Hack" Issues

Thanks! Still strumming them wholesome country songs *Wink

 

Hello TenForum users and administrators. I come to you today seeking some guidance on a particular registry "hack" we implemented at our company to defer Windows 10 Feature Updates from occurring automatically. Particularly preventing Windows 10 1703 from upgrading to Windows 10 1709 (Previous Windows versions have different registry values that need to be manipulated so this is specific to those two versions)

Backstory: When we decided it was time to finally upgrade the 1703 devices to 1709, I reversed the registry settings, initially created, to the 'default' values and applied the 'default' registry back to the affected 1703 device.We then used Windows Update to perform the update but the computers were unable to use Windows Update to successfully install the new version. At this point we decided to run the Windows Update Troubleshooter to see if it was able to solve Windows update issues. The troubleshooter did find Update Database corruption and applied fixes successfully. Once the fixes were applied, it downloaded and installed the 1709 update successfully (not quickly).

Problem: Now this is were the issue is noticeable. When you access Windows Settings > Update & Security > Windows Update, the users are prompted with the message "Some settings are managed by your organization". When you visit the Advanced Options section of Windows Update, the options are grayed out and un-manipulable by end users. The affected computer still seems able to connect to Windows Update, download and install Quality/Cumulative updates (No Feature updates have been released at this time so cannot confirm those).

Thoughts: I understand that Group Policy changes will change registry values to correlate the changes to the OS, but will the Registry changes we've made show up in Group Policy? If the Registry and Group Policy are one to one, am I looking in the wrong place in Group Policy for these changes?

1709 Registry: (*** Unknown Registry Values)

PolicyState:

• BranchReadinessLevel: Values= (10) Semi-Annual(Targeted)(Current Branch) (20)Semi-Annual (Current Branch for Business)
• DeferFeatureUpdates: Values= (1) Defer Feature Updates (0) Do Not Defer Feature Updates
• DeferQualityUpdates: Values= (1) Defer Quality Updates (0) Do Not Defer Quality Updates
• FeatureUpdatesDeferralInDays: Value=(# of days to defer Feature updates)
• IsDeferrallsActive: (1) Unknown Registry Setting (Not directly configured during initial registry deferral)***
• IsWUfBConfigured: (1) Unknown Registry Setting (Not directly configured during initial registry deferral)***
• PolicySources: (2) Unknown Registry Setting (Not directly configured during initial registry deferral)***
• QualityUpdatesDeferalInDays: Value=(# of days to defer Quality updates)

Settings:

• PauseFeatureStatus: Values = (0) Not Paused (1) Paused
• PauseQualityStatus: Values = (0) Not Paused (1) Paused

1703 Registry "Hack":

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]

"DeferFeatureUpdates"=dword:00000001
"BranchReadinessLevel"=dword:00000020
"DeferFeatureUpdatesPeriodInDays"=dword:0000016d
"PauseFeatureUpdatesStartTime"=""
"DeferQualityUpdates"=dword:00000001
"DeferQualityUpdatesPeriodInDays"=dword:0000001e
"PauseQualityUpdatesStartTime"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection]

"AllowTelemetry"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection\Users]

Pictures:











Related Topics:Windows Update - Defer Feature and Quality Updates in Windows 10 Windows 10 Tutorials

Conclusion: We aren't eager to release the Feature updates to users if we are going to be presented with this problem after the upgrade process. I am relatively experienced with updates throughout Windows editions but Windows 10 Feature updates has made it a challenge to have consistent and repeatable scripts to apply changes automatically. Thank you for your time if you've made it this far and any suggestions or opinions will be put directly to use. I will keep this thread updated with any progress or solutions we gain moving forward.

-Willie

:)

 

After KB4074588 something bricked USB3 support on HP AIO c220 based system

I just learned that there should normally be a "fourth Tuesday" quality update for version 1709, but none was released for it two days ago despite the buggy Patch Tuesday security update. For everyone running the Pro version, I strongly recommend downloading
the ISO for version 1703, installing that, and deferring feature updates for 365 days. For users of the home version, upgrade to pro and install version 1703. Version 1709 is a disaster and should be avoided. Remember to upgrade to at least version 1803 in
October when version 1703 reaches its end of support. Download the ISO for 1703 (original Creators Update) here: Windows 10 Creators Update 1703 Download • Windows ISO

 

Feature Update 1709 from 1607

Most of our enterprise machines are still on 1607. When 1709 is released on October 17 and our defer feature updates key expires, will the Windows Update skip 1703 and make 1709 the only available update to install or will users still have the option
to update to 1703?

 

Welcome to The Forum Willie, How is Trigger?*Wink