%3CLINGO-SUB%20id%3D%22lingo-sub-1497215%22%20slang%3D%22en-US%22%3ESimplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497215%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWith%20the%20rollout%20of%20Windows%2010%2C%20version%201903%2C%20we%20gave%20customers%20control%20over%20when%20to%20take%20feature%20updates.%20As%20noted%20in%20Mike%20Fortin%E2%80%99s%20April%202019%20blog%20on%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2019%2F04%2F04%2Fimproving-the-windows-10-update-experience-with-control-quality-and-transparency%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EImproving%20the%20Windows%2010%20update%20experience%20with%20control%2C%20quality%20and%20transparency%3C%2FA%3E%2C%20feature%20updates%20are%20no%20longer%20offered%20automatically%20unless%20a%20device%20is%20nearing%20its%20end%20of%20service%20and%20therefore%20must%20update%20to%20stay%20secure.%20The%20purpose%20of%20this%20post%20is%20to%20discuss%20how%20Windows%2010%2C%20version%202004%20simplifies%20Windows%20Update%20settings%20further%20and%20to%20clarify%20how%20you%20can%20control%20when%20to%20take%20feature%20updates.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EFirst%2C%20until%20you%20approach%20end%20of%20service%2C%20you%20no%20longer%20need%20to%20configure%20any%20settings%20in%20order%20to%20stay%20on%20your%20current%20version%20of%20Windows%2010.%20This%20change%20enables%20you%20to%20remain%20on%20any%20given%20release%20for%20a%20longer%20duration%2C%20taking%20a%20feature%20update%20approximately%20once%20a%20year%20or%20less%20depending%20on%20which%20edition%20of%20Windows%2010%20your%20device%20is%20running.%20Additionally%2C%20prior%20to%20approaching%20end%20of%20service%2C%20you%20have%20complete%20control%20over%20when%20to%20download%20and%20install%20the%20latest%20Windows%2010%20feature%20update%20from%20the%20Windows%20Update%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page%2C%20as%20shown%20below%3A%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22windows-update-feature-update.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F202015i7C47238EA3C525F6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22windows-update-feature-update.png%22%20alt%3D%22How%20a%20Windows%2010%20feature%20update%20is%20offered%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EHow%20a%20Windows%2010%20feature%20update%20is%20offered%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20ability%20to%20remain%20on%20your%20current%20version%20until%20you%20choose%20to%20download%20and%20install%20the%20latest%20feature%20update%20or%20until%20approaching%20end%20of%20service%3CSTRONG%3E%20is%20only%20possible%20when%20deferrals%20are%20not%20set%3C%2FSTRONG%3E%20for%20the%20device.%20To%20date%2C%20some%20of%20you%20have%20leveraged%2C%20and%20continue%20to%20leverage%2C%20deferrals%20to%20delay%20feature%20updates.%20While%20deferrals%20can%20be%20a%20great%20way%20to%20roll%20out%20updates%20in%20waves%20to%20a%20set%20of%20devices%20across%20an%20organization%2C%20setting%20deferrals%20as%20an%20end%20user%20might%20now%20have%20some%20unintended%20consequences.%20Deferrals%20work%20by%20allowing%20you%20to%20specify%20how%20many%20days%20after%20an%20update%20is%20released%20before%20it%20is%20offered%20to%20your%20device.%20For%20example%2C%20if%20you%20configure%20a%20feature%20update%20deferral%20of%20365%20days%2C%20you%20will%20be%20offered%20every%20feature%20update%20365%20days%20after%20it%20has%20been%20released.%20However%2C%20given%20that%20we%20release%20Windows10%20feature%20updates%20semi-annually%2C%20if%20you%20configure%20a%20feature%20update%20deferral%20of%20365%20days%2C%20your%20device%20will%20install%20a%20new%20feature%20update%20every%20six%20months%2C%20twice%20as%20often%20as%20an%20end%20user%20who%20has%20not%20configured%20any%20settings.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3ETo%20try%20and%20prevent%20these%20unintended%20consequences%20and%20enable%20you%20to%20stay%20with%20a%20given%20release%20of%20Windows%2010%20for%20the%20longest%20duration%2C%20beginning%20with%20Windows%2010%2C%20version%202004%2C%20we%20no%20longer%20display%20deferral%20options%20on%20the%20Windows%20Update%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page%20under%20%3CSTRONG%3EAdvanced%20options%3C%2FSTRONG%3E.%20This%20ensures%20that%20you%20have%20control%20over%2C%20and%20visibility%20into%2C%20exactly%20when%20to%20install%20the%20latest%20Windows%2010%20feature%20update%20until%20you%20near%20end%20of%20service.%20The%20ability%20to%20set%20deferrals%20has%20not%20been%20taken%20away%2C%20it%20is%20just%20no%20longer%20being%20displayed%20on%20the%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIf%20you%20want%20to%20leverage%20deferrals%20to%20install%20a%20feature%20update%20semi-annually%20a%20given%20number%20of%20days%20after%20its%20release%2C%20you%20can%20continue%20to%20do%20so%20by%20leveraging%20Local%20Group%20Policy.%20Deferral%20settings%20can%20be%20found%20in%20the%20Windows%20Update%20for%20Business%20folder%20in%20Local%20Group%20Policy%20Editor.%20To%20access%20this%20folder%2C%20navigate%20to%20%3CSTRONG%3EComputer%20Configuration%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3EAdministrative%20Templates%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3EWindows%20Components%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3EWindows%20Update%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3EWindows%20Update%20for%20Business%3C%2FSTRONG%3E.%20Within%20the%20%3CSTRONG%3EWindows%20Update%20for%20Business%3C%2FSTRONG%3E%20folder%2C%20you%20will%20see%20options%20for%20%E2%80%9CSelect%20when%20Preview%20builds%20and%20Feature%20Updates%20are%20received%E2%80%9D%20and%20%E2%80%9CSelect%20when%20Quality%20Updates%20are%20received%22%2C%20which%20enable%20you%20to%20defer%20feature%20updates%2C%20monthly%20quality%20updates%2C%20or%20both.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22wufb-local-gp-editor.png%22%20style%3D%22width%3A%20999px%3B%22%3E-ERR%3AREF-NOT-FOUND-%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EWindows%20Update%20for%20Business%20settings%20in%20the%20Local%20Group%20Policy%20Editor%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EFinally%2C%20it%20is%20important%20to%20note%20that%20this%20change%20does%20not%20impact%20IT%20administrators%20who%20utilize%20mobile%20device%20management%20(MDM)%20tools%20or%20Group%20Policy%20management%20tools%20to%20set%20deferrals%20in%20order%20to%20do%20validation%20and%20roll%20out%20feature%20updates%20in%20planned%20waves%20across%20their%20organization.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EI%20hope%20this%20post%20clears%20up%20any%20questions%20you%20may%20have%20about%20this%20change%20in%20Windows%2010%2C%20version%202004.%20If%20you%20are%20an%20IT%20admin%20and%20looking%20for%20detailed%20information%20on%20using%20Windows%20Update%20for%20Business%20to%20keep%20the%20Windows%2010%20devices%20in%20your%20organization%20always%20up%20to%20date%20with%20the%20latest%20security%20defenses%20and%20Windows%20features%2C%20see%20our%20-ERR%3AREF-NOT-FOUND-Windows%20Update%20for%20Business%20documentation.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1497215%22%20slang%3D%22en-US%22%3E%3CP%3ELearn%20how%20Windows%2010%2C%20version%202004%20simplifies%20Windows%20Update%20settings%20and%20how%20you%20can%20control%20when%20to%20take%20feature%20updates.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1497215%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServicing%20and%20updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1497468%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497468%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3EThe%20ability%20to%20remain%20on%20your%20current%20version%20until%20you%20choose%20to%20download%20and%20install%20the%20latest%20feature%20update%20or%20until%20approaching%20end%20of%20service%3CSTRONG%3E%20is%20only%20possible%20when%20deferrals%20are%20not%20set%3C%2FSTRONG%3E%20for%20the%20device.%3C%2FBLOCKQUOTE%3E%3CP%3EWhat%20happens%20if%20I%20update%20a%20device%20with%20deferral%20settings%20from%201909%20or%20earlier%20to%202004%3F%3CBR%20%2F%3EThere%20is%20no%20way%20to%20revert%20to%20default%20setting%20anymore.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1497506%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497506%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F158630%22%20target%3D%22_blank%22%3E%40Aria%20Carley%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3ETo%20try%20and%20prevent%20these%20unintended%20consequences%20and%20enable%20you%20to%20stay%20with%20a%20given%20release%20of%20Windows%2010%20for%20the%20longest%20duration%2C%20beginning%20with%20Windows%2010%2C%20version%202004%2C%20we%20no%20longer%20display%20deferral%20options%20on%20the%20Windows%20Update%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page%20under%20%3CSTRONG%3EAdvanced%20options%3C%2FSTRONG%3E.%20This%20ensures%20that%20you%20have%20control%20over%2C%20and%20visibility%20into%2C%20exactly%20when%20to%20install%20the%20latest%20Windows%2010%20feature%20update%20until%20you%20near%20end%20of%20service.%20The%20ability%20to%20set%20deferrals%20has%20not%20been%20taken%20away%2C%20it%20is%20just%20no%20longer%20being%20displayed%20on%20the%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThis%20looks%20like%20a%20poor%20design%20decision.%20For%20one%20thing%2C%20removing%20controls%20does%20not%20%22ensure%20that%20%5BI%5D%20have%20control%22.%20For%20another%2C%20these%20explanations%20still%20do%20not%20justify%20the%20removal%20of%20the%20deferral%20controls%20for%20the%20monthly%20updates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20was%20me%2C%20I'd%20leave%20the%20controls%20to%20be%2C%20and%20added%20a%20%22Maximum%22%20item%20to%20the%20drop-down%20list%20that%20controlled%20the%20feature%20update%20deferral.%20This%20%22Maximum%22%20item%20would%20enact%20the%20behavior%20that%20this%20article%20explains.%20But%20then%20again%2C%20if%20it%20was%20me%2C%20I'd%20have%20resolved%20the%20problem%20in%20the%20source%20by%20ensuring%20that%20updates%20have%20such%20quality%20that%20nobody%20needs%20deferring%20them%20in%20the%20first%20place.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1497844%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497844%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20is%20this%20refleced%20in%20the%20MDM%20policies%20for%20Windows%20Update%20for%20Business%20in%20Intune%3F%3C%2FP%3E%3CP%3EIn%20the%20%22Windows%2010%20Update%20Rings%22%20configuration%20profile%20you%20have%20to%20put%20in%20a%20deferral%20period%20(Feature%20update%20deferral%20period%20(days)).%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20have%20to%20be%20a%200%20to%20deactivate%20the%20deferrals%20for%20feature%20updates%3F%3C%2FP%3E%3CP%3EHow%20does%20it%20play%20together%20with%20the%20%22Windows%2010%20feature%20updates%20(Preview)%22%20profile%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1498036%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1498036%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20per%20above%2C%20I%E2%80%99m%20also%20interested%20to%20see%20how%20this%20fits%2Fworks%20within%20the%20existing%20Update(s)%20related%20options%20via%20Intune.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1498130%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1498130%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20what%20Microsoft%20should%20do%20with%20feature%20updates%3A%3C%2FP%3E%3CUL%3E%3CLI%3ERelease%20one%20feature%20update%20per%20year%3C%2FLI%3E%3CLI%3EEach%20feature%20update%20should%20be%20in%20service%20for%2030%20months%3C%2FLI%3E%3CLI%3EEach%20feature%20update%20should%20be%20installed%20using%20the%20same%20servicing%20technology%20they%20used%20for%20the%201903%20to%201909%20release%3C%2FLI%3E%3CLI%3EFor%20the%20enterprise%2C%20never%20automatically%20install%20a%20feature%20update%20without%20giving%20complete%20control%20over%20when%20and%20through%20what%20method%20the%20organization%20wants%20to%20update%20their%20estate.%20If%20they%20fall%20out%20of%20support%2C%20that's%20on%20them.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1500375%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1500375%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F158630%22%20target%3D%22_blank%22%3E%40Aria%20Carley%3C%2FA%3E%26nbsp%3B.%20Please%20check%20these%20sentences%20again%20in%20your%20post...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20example%2C%20if%20you%20configure%20a%20feature%20update%20deferral%20of%20365%20days%2C%20you%20will%20be%20offered%20every%20feature%20update%20365%20days%20after%20it%20has%20been%20released.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Eif%20you%20configure%20a%20feature%20update%20deferral%20of%20365%20days%2C%20your%20device%20will%20install%20a%20new%20feature%20update%20every%20six%20months%2C%20twice%20as%20often%20as%20an%20end%20user.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EBoth%20are%20giving%20same%20meaning%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1500463%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1500463%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F256757%22%20target%3D%22_blank%22%3E%40win32_lean_and_mean%3C%2FA%3EI%20asked%20the%20same%20question%20from%20Microsoft%20Support.%20They%20say%20the%20Group%20Policy%20Editor%20and%20the%20Settings%20app%20in%201909%20and%20earlier%20stored%20their%20deferral%20settings%20in%20different%20places%20in%20Registry.%20The%20one%20that%20the%20Group%20Policy%20Editor%20stored%20always%20took%20precedence.%20Now%2C%20the%20location%20that%20the%20Settings%20app%20used%20is%20ignored.%20Also%2C%20during%20the%20update%20to%2020H1%2C%20those%20settings%20get%20deleted.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1500684%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1500684%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20my%20own%20way%20and%20it%20serves%20me%20well.%20I%20decide%20what%20happens%20and%20when.%20Works%20like%20a%20charm.%20I%20don't%20have%20to%20worry%20about%20a%20stable%20system%20becoming%20a%20hot%20mess.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.sordum.org%2F9470%2Fwindows-update-blocker-v1-5%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.sordum.org%2F9470%2Fwindows-update-blocker-v1-5%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwpd.app%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwpd.app%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1502288%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1502288%22%20slang%3D%22en-US%22%3E%3CP%3E%22we%20no%20longer%20display%20deferral%20options%20on%20the%20Windows%20Update%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page%20under%20%3CSTRONG%3EAdvanced%20options%3C%2FSTRONG%3E.%20This%20ensures%20that%20you%20have%20control%20over%2C%20and%20visibility%20into%2C%20exactly%20when%20to%20install%20the%20latest%20Windows%2010%20feature%20update%20until%20you%20near%20end%20of%20service.%20The%20ability%20to%20set%20deferrals%20has%20not%20been%20taken%20away%2C%20it%20is%20just%20no%20longer%20being%20displayed%20on%20the%20%3CSTRONG%3ESettings%3C%2FSTRONG%3E%20page.%22%3C%2FP%3E%3CP%3E%22Local%20Group%20Policy%20Editor%22%3C%2FP%3E%3CP%3ESo%20let%20me%20get%20this%20straight%2C%20by%20removing%20the%20option%20and%20forcing%20it%20into%20Group%20Policy%20Editor%2C%20something%20only%20Windows%2010%20Pro%20and%20higher%20have%20(without%20modifying%20the%20OS)%2C%20you%20are%20giving%20the%20users%20control%20over%20when%26nbsp%3B%20to%20install%20the%20latest%20Windows%2010%20feature%20update%3F%3C%2FP%3E%3CP%3EThis%20contradicts%20itself%20like%20mad.%20This%20is%20also%20a%20move%20that%20Apple%20would%20do.%3C%2FP%3E%3CP%3EMicrosoft%2C%20you%20are%20now%20telling%20your%20users%20that%20they%20are%20too%20dumb%20to%20control%20when%20updates%20can%20be%20installed%20on%20there%20systems.%20Given%20the%20recent%20issues%20with%20feature%20updates%2C%20this%20is%20just%20going%20to%20cause%20major%20issues.%3C%2FP%3E%3CP%3ECongratulations%2C%20you%20made%20me%20compare%20you%20to%20Apple%20and%20it's%20actually%20a%20BAD%20thing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1502331%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1502331%22%20slang%3D%22en-US%22%3E%20%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3ECongratulations%2C%20you%20made%20me%20compare%20you%20to%20Apple%20and%20it's%20actually%20a%20BAD%20thing.%3C%2FP%3E%20%3CP%3EYeah...%20beyond%20bad%20even.%20Totally%20unacceptable.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1503384%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1503384%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1506977%22%20slang%3D%22en-US%22%3ERe%3A%20Simplified%20Windows%20Update%20settings%20for%20end%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1506977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F322694%22%20target%3D%22_blank%22%3E%40RAJUMATHEMATICSMSC%3C%2FA%3EThe%20two%20sentences%20are%20not%20in%20conflict.%26nbsp%3B%20Deferral%20of%20365%20days%20is%20after%20the%20release%20of%20a%20given%20version%3A%3C%2FP%3E%3CP%3E365%20days%20after%20the%20release%20of%201809%2C%20the%20PC%20installs%201809%3C%2FP%3E%3CP%3E365%20days%20after%20the%20release%20of%201903%2C%20the%20PC%20installs%201903%3C%2FP%3E%3CP%3E365%20days%20after%20the%20release%20of%201909%2C%20the%20PC%20installs%201909%3C%2FP%3E%3CP%3EThe%20new%20default%20(no%20deferral)%20as%20I%20understand%20it%20ends%20up%20upgrading%20once%20per%20year%3A%3C%2FP%3E%3CP%3E16-18%20months%20after%20the%20release%20of%201809%2C%20the%20PC%20installs%20the%20then-current%20version%20(1909)%20in%20spring%202020%3C%2FP%3E%3CP%3E16-18%20months%20after%20the%20release%20of%201909%2C%20the%20PC%20installs%20the%20then-current%20version%20(2009)%20in%20spring%202021%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELeft%20unclear%20is%20how%20to%20turn%20it%20off%2C%20to%20revert%20to%20the%20default.%26nbsp%3B%20I%20have%20read%20setting%20DeferFeatureUpdatesPeriodInDays%20to%200%20reverts%20to%20the%20default%20behavior%20but%20my%20testing%20with%20PSWindowsUpdate%20seems%20inconsistent%3A%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%20150%3A%20feature%20update%202004%20not%20detected%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%200%3A%20feature%20update%20still%20not%20detected%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%201%3A%20feature%20update%20IS%20detected%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%200%3A%20feature%20update%20IS%20STILL%20detected%3C%2FP%3E%3CP%3EDelete%20DeferFeatureUpdatesPeriodInDays%3A%20feature%20update%20IS%20STILL%20detected%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%20300%3A%20feature%20update%20is%20no%20longer%20detected%3C%2FP%3E%3CP%3EDeferFeatureUpdatesPeriodInDays%20%3D%200%3A%20feature%20update%20still%20not%20detected%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

With the rollout of Windows 10, version 1903, we gave customers control over when to take feature updates. As noted in Mike Fortin’s April 2019 blog on Improving the Windows 10 update experience with control, quality and transparency, feature updates are no longer offered automatically unless a device is nearing its end of service and therefore must update to stay secure. The purpose of this post is to discuss how Windows 10, version 2004 simplifies Windows Update settings further and to clarify how you can control when to take feature updates.

First, until you approach end of service, you no longer need to configure any settings in order to stay on your current version of Windows 10. This change enables you to remain on any given release for a longer duration, taking a feature update approximately once a year or less depending on which edition of Windows 10 your device is running. Additionally, prior to approaching end of service, you have complete control over when to download and install the latest Windows 10 feature update from the Windows Update Settings page, as shown below:

How a Windows 10 feature update is offeredHow a Windows 10 feature update is offered

The ability to remain on your current version until you choose to download and install the latest feature update or until approaching end of service is only possible when deferrals are not set for the device. To date, some of you have leveraged, and continue to leverage, deferrals to delay feature updates. While deferrals can be a great way to roll out updates in waves to a set of devices across an organization, setting deferrals as an end user might now have some unintended consequences. Deferrals work by allowing you to specify how many days after an update is released before it is offered to your device. For example, if you configure a feature update deferral of 365 days, you will be offered every feature update 365 days after it has been released. However, given that we release Windows10 feature updates semi-annually, if you configure a feature update deferral of 365 days, your device will install a new feature update every six months, twice as often as an end user who has not configured any settings.

To try and prevent these unintended consequences and enable you to stay with a given release of Windows 10 for the longest duration, beginning with Windows 10, version 2004, we no longer display deferral options on the Windows Update Settings page under Advanced options. This ensures that you have control over, and visibility into, exactly when to install the latest Windows 10 feature update until you near end of service. The ability to set deferrals has not been taken away, it is just no longer being displayed on the Settings page.

If you want to leverage deferrals to install a feature update semi-annually a given number of days after its release, you can continue to do so by leveraging Local Group Policy. Deferral settings can be found in the Windows Update for Business folder in Local Group Policy Editor. To access this folder, navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business. Within the Windows Update for Business folder, you will see options for “Select when Preview builds and Feature Updates are received” and “Select when Quality Updates are received", which enable you to defer feature updates, monthly quality updates, or both.

Windows Update for Business settings in the Local Group Policy EditorWindows Update for Business settings in the Local Group Policy Editor

Finally, it is important to note that this change does not impact IT administrators who utilize mobile device management (MDM) tools or Group Policy management tools to set deferrals in order to do validation and roll out feature updates in planned waves across their organization.

I hope this post clears up any questions you may have about this change in Windows 10, version 2004. If you are an IT admin and looking for detailed information on using Windows Update for Business to keep the Windows 10 devices in your organization always up to date with the latest security defenses and Windows features, see our Windows Update for Business documentation.

 

12 Comments
Senior Member
The ability to remain on your current version until you choose to download and install the latest feature update or until approaching end of service is only possible when deferrals are not set for the device.

What happens if I update a device with deferral settings from 1909 or earlier to 2004?
There is no way to revert to default setting anymore.

Frequent Visitor

@Aria Carley wrote:

To try and prevent these unintended consequences and enable you to stay with a given release of Windows 10 for the longest duration, beginning with Windows 10, version 2004, we no longer display deferral options on the Windows Update Settings page under Advanced options. This ensures that you have control over, and visibility into, exactly when to install the latest Windows 10 feature update until you near end of service. The ability to set deferrals has not been taken away, it is just no longer being displayed on the Settings page.


This looks like a poor design decision. For one thing, removing controls does not "ensure that [I] have control". For another, these explanations still do not justify the removal of the deferral controls for the monthly updates.

 

If it was me, I'd leave the controls to be, and added a "Maximum" item to the drop-down list that controlled the feature update deferral. This "Maximum" item would enact the behavior that this article explains. But then again, if it was me, I'd have resolved the problem in the source by ensuring that updates have such quality that nobody needs deferring them in the first place.

Occasional Contributor

How is this refleced in the MDM policies for Windows Update for Business in Intune?

In the "Windows 10 Update Rings" configuration profile you have to put in a deferral period (Feature update deferral period (days)). 

Does it have to be a 0 to deactivate the deferrals for feature updates?

How does it play together with the "Windows 10 feature updates (Preview)" profile?

 

 

Frequent Visitor

As per above, I’m also interested to see how this fits/works within the existing Update(s) related options via Intune.

Regular Visitor

Here's what Microsoft should do with feature updates:

  • Release one feature update per year
  • Each feature update should be in service for 30 months
  • Each feature update should be installed using the same servicing technology they used for the 1903 to 1909 release
  • For the enterprise, never automatically install a feature update without giving complete control over when and through what method the organization wants to update their estate. If they fall out of support, that's on them.
Contributor

@Aria Carley . Please check these sentences again in your post...

 

For example, if you configure a feature update deferral of 365 days, you will be offered every feature update 365 days after it has been released.

 

if you configure a feature update deferral of 365 days, your device will install a new feature update every six months, twice as often as an end user.

Both are giving same meaning

Frequent Visitor

@win32_lean_and_meanI asked the same question from Microsoft Support. They say the Group Policy Editor and the Settings app in 1909 and earlier stored their deferral settings in different places in Registry. The one that the Group Policy Editor stored always took precedence. Now, the location that the Settings app used is ignored. Also, during the update to 20H1, those settings get deleted.

Regular Visitor

I have my own way and it serves me well. I decide what happens and when. Works like a charm. I don't have to worry about a stable system becoming a hot mess.

 

https://www.sordum.org/9470/windows-update-blocker-v1-5/

https://wpd.app/

Occasional Visitor

"we no longer display deferral options on the Windows Update Settings page under Advanced options. This ensures that you have control over, and visibility into, exactly when to install the latest Windows 10 feature update until you near end of service. The ability to set deferrals has not been taken away, it is just no longer being displayed on the Settings page."

"Local Group Policy Editor"

So let me get this straight, by removing the option and forcing it into Group Policy Editor, something only Windows 10 Pro and higher have (without modifying the OS), you are giving the users control over when  to install the latest Windows 10 feature update?

This contradicts itself like mad. This is also a move that Apple would do.

Microsoft, you are now telling your users that they are too dumb to control when updates can be installed on there systems. Given the recent issues with feature updates, this is just going to cause major issues.

Congratulations, you made me compare you to Apple and it's actually a BAD thing.

Regular Visitor
@Nethaniel wrote:

Congratulations, you made me compare you to Apple and it's actually a BAD thing.


Yeah... beyond bad even. Totally unacceptable. 

Deleted
Not applicable

 

 

Occasional Visitor

@RAJUMATHEMATICSMSCThe two sentences are not in conflict.  Deferral of 365 days is after the release of a given version:

365 days after the release of 1809, the PC installs 1809

365 days after the release of 1903, the PC installs 1903

365 days after the release of 1909, the PC installs 1909

The new default (no deferral) as I understand it ends up upgrading once per year:

16-18 months after the release of 1809, the PC installs the then-current version (1909) in spring 2020

16-18 months after the release of 1909, the PC installs the then-current version (2009) in spring 2021

 

Left unclear is how to turn it off, to revert to the default.  I have read setting DeferFeatureUpdatesPeriodInDays to 0 reverts to the default behavior but my testing with PSWindowsUpdate seems inconsistent:

DeferFeatureUpdatesPeriodInDays = 150: feature update 2004 not detected

DeferFeatureUpdatesPeriodInDays = 0: feature update still not detected

DeferFeatureUpdatesPeriodInDays = 1: feature update IS detected

DeferFeatureUpdatesPeriodInDays = 0: feature update IS STILL detected

Delete DeferFeatureUpdatesPeriodInDays: feature update IS STILL detected

DeferFeatureUpdatesPeriodInDays = 300: feature update is no longer detected

DeferFeatureUpdatesPeriodInDays = 0: feature update still not detected