Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1004344%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004344%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20I%20install%20this%20on%20my%20Surface%20Book%202%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004826%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004826%22%20slang%3D%22en-US%22%3E%3CP%3EI%20run%20Windows%2010%20in%20a%20corporate%20environment%20and%20we%20are%20in%20the%20process%20of%20updating%20users%20PCs%20from%20Win10%201803%20to%201903%20as%20we%20have%20already%20tested%20its%20stability%2C%20performance%20and%20capability%20with%20our%20bespoke%20applications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20of%20today%2013th%20November%202019%2C%20Microsoft%20have%20removed%20the%20ability%20to%20update%20to%201903%2C%20and%20have%20instead%20replaced%20it%20with%201909.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20was%20no%20warning%20yesterday%2C%20i%20am%20half%20way%20through%20a%201000%2B%20user%20laptop%20upgrade.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYour%20disregard%20for%20the%20IT%20Pro%20who%20has%20to%20deal%20with%20your%20lack%20of%20oversight%20for%20the%20Advanced%20user%20is%20perplexing%2C%20we%20do%20not%20want%20to%20have%20to%20succumb%20to%20your%20constant%20updates%2C%20all%20they%20do%20is%20make%20things%20worse%2C%20WTF%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%2015%2B%20years%20of%20IT%20Support%20experience%20i%20have%20to%20say%20making%20Windows%20more%20user%20friendly%20is%20the%20worst%20thing%20to%20have%20happened%2C%20the%20inability%20to%20choose%20an%20update%20package%20to%20be%20installed%20is%20beyond%20me%2C%20i%20cannot%20comprehend%20the%20stupidity%20of%20such%20Company%20like%20Microsoft%20who%20say%20they%20provide%20a%20service%2C%20and%20yet%20the%20level%20of%20consistency%20is%20close%20to%20that%20of%20a%20British%20political%20party.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20not%20want%20future%20Windows%20update%20versions%20to%20be%20superseded%20ever%20again%2C%20IT%20Pros%20like%20myself%20use%20to%20be%20able%20to%20download%20these%20as%20service%20packs%20and%20install%20them%20offline%20or%20deploy%20remotely%20with%20ease%2C%20now%20we%20have%20to%20use%20your%20f**king%20s**t%20windows%20update%20services%20that%20can%20only%20be%20%22delayed%22%20and%20never%20turned%20off.%20well%20f**k%20you%20Microsoft%2C%20i%20decide%20when%20my%20users%20get%20upgraded%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOh%20yeah%2C%20and%201909%20is%20not%20compatible%20with%20our%20current%20builds%2C%20thanks%20for%20your%20unwanted%20improvements%20d**k%20face.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004884%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004884%22%20slang%3D%22en-US%22%3E%3CP%3E1909%20broke%20my%20surface%20pro%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004888%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004888%22%20slang%3D%22en-US%22%3E%3CP%3ECouldn't%20have%20said%20it%20better%20myself%2C%20arrived%20to%20work%20today%20to%20an%20absolute%20sh**%20show%20!%20Bah%20humbug%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006058%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006058%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F456185%22%20target%3D%22_blank%22%3E%40AceTech30%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes%2C%20you%20can%20install%20it%20on%20any%20Windows%2010%20machine.%26nbsp%3B%20I%20myself%20am%20a%20Surface%20Book%202%20user%20and%20have%20been%20running%20it%20for%20months.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006063%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006063%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F456460%22%20target%3D%22_blank%22%3E%40Sjrjaj%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%2C%20tell%20me%20more%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20does%20%22broke%22%20mean.%26nbsp%3B%20Were%20you%20upgrading%20from%201903%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Econtact%20me%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310121%22%20target%3D%22_blank%22%3E%40Johnwilc%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E.com%20and%20I'll%20make%20sure%20you%20get%20assistance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006675%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006675%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CBR%20%2F%3ESo%20the%20latest%20monthly%20quality%20update%20for%20Windows%2010%2C%20version%201903%20(released%20October%208%2C%202019)%3B%20which%20includes%20the%20new%20features%20in%20Windows%2010%2C%20version%201909%20which%20are%20currently%20in%20a%20dormant%2Fdisabled%20state%20will%20remain%20so%2C%20for%20example%20for%20the%20full%20Windows%2010%20Pro%201903%20support%20lifecycle%20(Dec.%208%2C%202020)%20unless%20the%20KB%20referred%20to%20is%20installed%3F%20We%20can%20continue%20to%20defer%20feature%20updates%20while%20still%20receiving%20quality%20updates%3F%20Feature%20updates%20are%20being%20moved%20from%20March%2C%20September%20releases%20to%20December%2C%20June%20as%20I%20understand%20but%20the%20frequency%20will%20remain%20the%20same%20as%20indicated%3F%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006706%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006706%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F417523%22%20target%3D%22_blank%22%3E%40RaaMata%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1903%20will%20have%2018%20month%20servicing%20lifecycle%2C%26nbsp%3B%20during%20which%20it%20will%20receive%20quality%20updates.%3C%2FP%3E%0A%3CP%3E1909%20will%20have%2030%20months%2C%20for%20Enterprise%20and%20Education%20SKUs.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eyou%20did%20not%20say%20how%20your%20device%20is%20being%20managed%2C%20but%20its%20covered%20above.%26nbsp%3B%20You%20mentioned%20%22deferred%22%20so%20you%20may%20be%20WuFB%20managed.%20If%20so%2C%20we%20adhere%20to%20your%20WuFB%20deferral%20settings.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006957%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006957%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20i%20find%20the%20%22%3CSTRONG%3EFeature%20Update%20to%20Windows%2010%20version%201909%20via%20Enablement%20Package%20(KB4517245)%22%26nbsp%3B%20in%20SCCM%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20cant%20find%20the%20%3CSTRONG%3EKB4517245%26nbsp%3B%3C%2FSTRONG%3Ein%20SCCM%20console.%20Im%20using%20SCCM%20CB%20version%201902.%20We%20have%20clients%20on%201903%20and%20I%20don't%20want%20to%20deploy%20the%20complete%201909%20.wim%20file%20%2C%20all%20I%20want%20is%20the%20%22small%22%20enablement%20package%20to%20update%20my%201903%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDenco%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1007045%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1007045%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F456118%22%20target%3D%22_blank%22%3E%40denco-86%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20what%20you%20want%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20565px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F157004i3AED5219313AC13D%2Fimage-dimensions%2F565x318%3Fv%3D1.0%22%20width%3D%22565%22%20height%3D%22318%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1007052%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1007052%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20show%20me%20in%20the%20SCCM%20Console%20under%20the%20%22Software%20Library%20%26gt%3B%20All%20Software%20Updates%20%22%20node%20please%3F%3C%2FP%3E%3CP%3EIf%20that%20is%20not%20possible%20can%20you%20show%20me%20how%20to%20download%20the%20KB4517245%20patch%20offline%20please%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDenco%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1008895%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1008895%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BFor%20Windows%2010%20version%20lower%20than%201903%20how%20do%20you%20use%20SCCM%20to%20get%20to%20version%201909%20%3F%26nbsp%3B%20%26nbsp%3BThanks%20for%20posting%20that%20information%20on%201903%20--%26gt%3B%201909%20using%20WSUS%2FSCCM%20as%20we%20would%20have%20never%20figured%20that%20out%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1008978%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1008978%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BAlso%20in%20our%20WSUS%20-%26nbsp%3BKB4517245%26nbsp%3B%20does%20show%20up%20-%20but%20for%20some%20reason%20we%20cannot%20get%20SCCM%20to%20pick%20up%20this.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BIs%20there%20any%20articles%20on%20how%20exactly%20to%20do%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1009162%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1009162%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22xmsonormal%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F456118%22%20target%3D%22_blank%22%3E%40denco-86%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54954%22%20target%3D%22_blank%22%3E%40Eric%20Sabo%3C%2FA%3E%26nbsp%3BPlease%20make%20sure%20you%20have%20the%20%E2%80%9CWindows%2010%2C%20version%201903%20and%20later%E2%80%9D%20product%20and%20%E2%80%9CUpgrades%E2%80%9D%20classification%20selected%20in%20your%20Software%20Update%20Point%20site%20component.%20Both%20the%20enablement%20package%2C%20for%20devices%20on%201903%2C%20and%20normal%20feature%20update%2C%20for%20devices%20on%20earlier%20Windows%2010%20releases%2C%20should%20show%20in%20the%20%E2%80%9CWindows%2010%20Servicing%E2%80%9D%20%5C%20%E2%80%9CAll%20Windows%2010%20Updates%E2%80%9D%20node%2C%20not%20the%20%E2%80%9CAll%20Software%20Updates%E2%80%9D%20node%20as%20these%20are%20feature%20upgrades.%20Also%20note%20that%26nbsp%3Byou%20can%E2%80%99t%20search%20%E2%80%9CKB4517245%E2%80%9D%20as%20it%E2%80%99s%20not%20in%20the%20title%2C%20search%20just%20%E2%80%9C4517245%E2%80%9D%20or%26nbsp%3B%22enablement%22%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F157215iF63E73FDB9E9AF63%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1009285%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1009285%22%20slang%3D%22en-US%22%3E%3CP%3ERae%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20that%20helped%20a%20lot%20-%20we%20were%20looking%20under%20All%20Software%20Updates.%26nbsp%3B%20%26nbsp%3B%20Thanks%20again%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1010408%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1010408%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20updated%20one%201903%20machine%20with%20an%20enablement%20package%20update%20via%20WSUS%20and%20in%20winver%20it%20shows%20new%20build%2018363%2C%20but%20in%20WSUS%20it%20is%20still%2018362%20after%20latest%20report.%20Main%20WSUS%20server%20is%20on%20Windows%20Server%202012%20R2%20and%20downstream%20server%20with%20this%20machine%20is%20also%20on%20Windows%20Server%202012%20R2.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1011444%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1011444%22%20slang%3D%22en-US%22%3E%3CP%3EGetting%20things%20ready%20-%2094%25%3C%2FP%3E%3CP%3Edownload%20gets%20stuck%20at%20the%20above%26nbsp%3B%20for%20hours%2C%20tried%20restarting%20didn't%20work%2C%20any%20suggestions%20besides%20deleting%20the%20update%3F%3C%2FP%3E%3CP%3Ebellskee%40aol.com%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1011478%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1011478%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F459067%22%20target%3D%22_blank%22%3E%40bellskee%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20share%20some%20more%20context..%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20are%20you%20upgrading%20from%3F%3C%2FP%3E%0A%3CP%3EHow%20are%20you%20updating%3F%20WU%2C%20WuFB%2C%20WSUS%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013673%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013673%22%20slang%3D%22en-US%22%3E%3CP%3ESingle%20restart%20huh%3F%20I%20just%20ran%201909%20update%20(pressed%20Download%20and%20install%20now%20link%20on%20Updates%20page%20in%20Settings)%20on%20a%20fully%20updated%201903%20laptop.%20It%20downloaded%20and%20presented%20Restart%20now%20button.%20I%20pressed%20it.%20It%20rebooted%2C%20showed%20usual%20updates%20installing%20view%20with%20percents%20and%20then%20rebooted%20again%20and%20then%20booted%20into%20Windows%20desktop%20(autologon%20enabled).%20So%2C%20not%20exactly%20one%20restart%20%3A)%3C%2Fimg%3E%20At%20least%20in%20my%20case.%20Some%20cheap%20ASUS%20laptop.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1014154%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1014154%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236912%22%20target%3D%22_blank%22%3E%40David%20Glanz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%20David%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EShould%20not%20be%20a%20problem.%26nbsp%3B%20The%20servicing%20pipelines%20are%20separate%2C%20and%20the%20update%20process%20in%20this%20case%2C%20same%20as%20monthly%2C%20you%20have%20been%20using%20for%20sometime%20now%20with%20now%20issues.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1014425%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1014425%22%20slang%3D%22en-US%22%3E%3CP%3ETried%20to%20move%20test%20machine%20with%201909%20version%20to%20WSUS%20server%20on%20Windows%20Server%202016%20and%20it%20still%20reports%2018362.449%20(2%20instead%20of%203).%20I%20guess%20will%20have%20to%20wait%20for%20OS%20hosting%20WSUS%20patch%20to%20fix%20reporting%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013943%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013943%22%20slang%3D%22en-US%22%3EMy%20existing%20PC%20is%20dual-boot%20Win%207%20Pro%2064-bit%20and%20Win%2010%20Pro%2064-bit%20(now%20at%20version%201903).%20A%20Dell%20Optiplex%207010%20with%20Intel%20Core%20i5%203470%2C%20plenty%20of%20hard%20drive%20storage%20and%2016GB%20RAM.%20So%20far%2C%20updates%20to%20each%20OS%20have%20NOT%20affected%20the%20other%2C%20as%20far%20as%20I%20can%20tell.%20Is%20there%20anything%20different%20about%20doing%20the%20new%20update%20of%20the%20Win%2010%20side%20to%20version%201909%20that%20might%20affect%20the%20Win%207%20side%20and%20the%20current%2C%20working%20dual-booting%3F%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013955%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013955%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John%2C%3C%2FP%3E%3CP%3EIn%20corporate%20environment%20(W10%20Enterprise%2C%20Windows%20Update%20for%20Business%2C%20deployment%20rings...)%20is%20it%20possible%20to%20make%20this%20feature%20update%20mandatory%2C%20just%20like%20the%20previous%20ones%20%3F%20Most%20of%20our%20users%20do%20not%20want%20to%20deal%20with%20updates%20and%20were%20ok%20with%20existing%20installation%20options%20(especially%20when%20restart%20is%20as%20fast%20as%20this%20one).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016470%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016470%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40John%20Wilcox%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20if%20this%20is%20right%20forum%2C%20however%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDownloading%20newly%20released%20Danish%20Window%2010%20Enterprise%201909%2C%20from%20VLSC%2C%20I%20believe%20either%20the%20Install.wim%20is%20wrongly%20numbered%2C%20or%20the%20files%20are%20backlevel!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20what%20shows%20(%3CSPAN%3EVersion%20%3A%2010.0.18362%3C%2FSPAN%3E%20%3D%26gt%3B%201903)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ED%3A%5CSources%26gt%3Bdism%20%2Fget-imageinfo%20%2Fimagefile%3Ag%3A%5Csources%5Cinstall.wim%20%2Findex%3A3%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EDeployment%20Image%20Servicing%20and%20Management%20tool%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EVersion%3A%2010.0.17763.1%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EDetails%20for%20image%20%3A%20g%3A%5Csources%5Cinstall.wim%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EIndex%20%3A%203%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EName%20%3A%20Windows%2010%20Enterprise%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EDescription%20%3A%20Windows%2010%20Enterprise%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ESize%20%3A%2014.647.013.793%20bytes%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EWIM%20Bootable%20%3A%20No%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EArchitecture%20%3A%20x64%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EHal%20%3A%20%3CUNDEFINED%3E%3C%2FUNDEFINED%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EVersion%20%3A%2010.0.18362%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EServicePack%20Build%20%3A%20418%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EServicePack%20Level%20%3A%200%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EEdition%20%3A%20Enterprise%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EInstallation%20%3A%20Client%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EProductType%20%3A%20WinNT%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EProductSuite%20%3A%20Terminal%20Server%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ESystem%20Root%20%3A%20WINDOWS%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EDirectories%20%3A%2022289%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EFiles%20%3A%2095438%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ECreated%20%3A%2007-10-2019%20-%2004%3A21%3A32%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EModified%20%3A%2007-10-2019%20-%2004%3A38%3A44%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ELanguages%20%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3Eda-DK%20(Default)%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EThe%20operation%20completed%20successfully.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016557%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016557%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20expected%20as%201909%20is%20just%20a%20CU%20of%201903.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3EBecause%20of%20the%20common%20baseline%2C%20even%20after%20installing%20Windows%2010%2C%20version%201909%2C%20individual%20system%20file%20versions%20will%20still%20appear%20as%2018362.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016722%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016722%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3BThe%20build%20shows%20in%20the%20client%20operating%20system%20as%2018363%20so%20surely%20this%20should%20be%20reported%20to%20WSUS%2FSCCM%20as%20the%20correct%20build%3F%20Even%20a%20CU%20affects%20the%20build%20number%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016755%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016755%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F461742%22%20target%3D%22_blank%22%3E%40polaris%3C%2FA%3E%26nbsp%3BCU%20updates%20the%20number%20after%20the%20dot%20and%20this%20is%20a%20CU%20number%2C%20not%20a%20build%20number%2C%20which%20is%20first%205%20digits.%20In%20my%20case%20CU%20digits%20are%20reported%20correctly%2C%20but%20not%20the%20build%20digits.%20I'm%20guessing%20WSUS%20is%20maybe%20identifying%20OS%20by%20some%20system%20file%2C%20which%20hasn't%20changed%20in%201909.%20But%20it%20does%20show%20CU%20number%20correctly%2C%20so%20maybe%20not%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016765%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016765%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3BWhat%20CU%20number%20are%20you%20seeing%3F%20I%20am%20getting%20.449%20for%20clients%20that%20are%20on%20either%201909%20or%201903%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016884%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016884%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20it%20is%20.449%20for%201909%20and%201903.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20actually%20winver%20for%201903%20and%201909%20shows%20.476.%20I%20think%20first%20it%20was%20.449%20after%20the%201909%20update%2C%20but%20now%20some%20other%20update%20installed%20and%20it%20went%20higher%2C%20but%20WSUS%20for%20some%20reason%20is%20not%20reflecting%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017288%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017288%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%20have%20freshly%20installed%201903%20machines%20in%20fr-ca%20with%20OSD%20with%20the%20October%20cumulative%20update%20installed.%20The%20enablement%20Package%20has%20been%20deployed%20(available)%20to%20those%20machines%2C%20but%20they%20don't%20show%20up%20in%20software%20center)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20we%20missing%20something%3F%20We're%20on%20CB%201902%20with%20the%20hotfix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThks%20in%20advance%20and%20don't%20hesitate%20if%20you%20have%20any%20questions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017502%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017502%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99115%22%20target%3D%22_blank%22%3E%40Stephane%20Lalancette%3C%2FA%3E%26nbsp%3Bdo%20your%20clients%20have%20the%20prerequisite%201903%20cumulative%20and%20servicing%20stack%20updates%20installed%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20prerequisites%20listed%20here%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4517245%2Ffeature-update-via-windows-10-version-1909-enablement-package%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%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%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4517245%2Ffeature-update-via-windows-10-version-1909-enablement-package%3C%2FA%3E%3C%2FP%3E%0A%3CP%3Eor%20here%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fconfigmgr%2Fsum%2Fget-started%2Fconfigure-classifications-and-products%3Fwindows-10-version-1903-and-later%23feature-updates-for-windows-10-version-1909%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%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%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fconfigmgr%2Fsum%2Fget-started%2Fconfigure-classifications-and-products%3Fwindows-10-version-1903-and-later%23feature-updates-for-windows-10-version-1909%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20the%20prerequisites%20installed%2C%20what%20does%20the%20state%20of%20the%20enablement%20package%20update%20report%20as%20for%20the%20clients%20in%20deployment%20monitoring%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017530%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F461742%22%20target%3D%22_blank%22%3E%40polaris%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3BWhere%20in%20WSUS%2FConfigMgr%20are%20you%20seeing%20the%20OS%20build%20number%20incorrectly%20represented%20as%2018362%20instead%20of%2018363%3F%20In%20ConfigMgr%2C%20I%20see%20the%20Operating%20System%20Build%20correctly%20represented%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F157913i5D4DB5DA73FF8309%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017663%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458019%22%20target%3D%22_blank%22%3E%40Rae_Goodhart%3C%2FA%3E%26nbsp%3BI%20am%20just%20using%20WSUS%20but%20it%20looks%20similar%20to%20the%20screenshot%20you%20have%20posted%20(without%20the%20correct%20build%2FCU%20of%20course)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1018745%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1018745%22%20slang%3D%22en-US%22%3E%3CP%3EYep%2C%20in%20WSUS%20there%20is%20no%20Operating%20System%20Build%20column.%20It%20is%20called%20%22Version%22%20column%20and%20it%20shows%2018362.449%20for%20some%20reason%20for%201909%2C%20although%20it%20should%20be%2018363.476.%20And%20it%20looks%20like%20it%20also%20shows%20it%20wrong%20for%201903%20for%20me.%20It%20should%20be%2018362.476%2C%20but%20it%20shows%2018362.449.%20It's%20like%20it%20got%20stuck%20after%20it%20received%20these%20new%201909%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019215%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019215%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F461742%22%20target%3D%22_blank%22%3E%40polaris%3C%2FA%3E%26nbsp%3BThe%20Version%20in%20WSUS%20is%20based%20on%20the%20version%20of%20the%20Windows%20update%20client%2C%20which%20does%20not%20change%20to%2018363%2C%20it's%20more%20of%20a%20binary%20version.%26nbsp%3B%20For%20the%20CU%20issue%2C%20not%20all%20cumulative%20updates%20patch%20the%20component%20of%20Windows%20that%20is%20the%20Windows%20update%20client%2C%20and%20in%20this%20case%20.476%20appears%20to%20not%20have%20updated%20the%20Windows%20update%20client%20itself%2C%20so%20the%20Version%20remains.%20I%20don't%20believe%20this%20is%20related%20to%201909%2F1903%20enablement%20package%2C%20it%20just%20happens%20that%20this%20cummulative%20update%20didn't%20need%20to%20make%20any%20changes%20in%20the%20Windows%20update%20client%20component%20of%20Windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019568%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019568%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20WSUS%20admins%20have%20no%20reliable%20source%20of%20information%20about%20a%20real%20version%20of%20Windows%2010%3F%20It%20seems%20that%20smaller%20feature%20updates%20have%20their%20own%20problem%20now.%20Or%20we%20should%20just%20approve%20them%20and%20hope%20they%20install%20without%20checking%20(no%20Needed%20shown%20at%20least)%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019723%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019723%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20would%20expect%20the%201909%20release%20to%20contain%20any%20CU's%20inbetween%201903%20and%201909%2C%20and%20the%20version%2Fbuild%20number%20reflecting%20this%20-%20alas%20version%20should%20be%26nbsp%3B%3CSPAN%3E10.0.18363%2C%20not%26nbsp%3B10.0.18362.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20please%20note%20that%20I'm%20refering%20to%20the%20Install.wim%2C%20not%20individual%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20appears%20MS%20managed%20to%20make%20a%20total%20mess%20out%20of%20this%2C%20that%20everyone%20now%20has%20to%20spend%20numerous%20hours%20to%20Work%20around%20-%20total%20Waste%20of%20everyones%20time.%20MS%20please%20call%20in%20some%20proffesionals%E2%80%A6.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1002660%22%20slang%3D%22en-US%22%3EWindows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1002660%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20post%20was%20co-authored%20by%20John%20Wilcox%20(Windows%20as%20a%20Service%20Evangelist%2C%20Windows%20Servicing%20%26amp%3B%20Delivery)%2C%20Alec%20Oot%20(Principal%20Program%20Manager%20Lead%2C%20Windows%20Servicing%20%26amp%3B%20Delivery)%2C%20and%20Will%20Patton%20(Senior%20Program%20Manager%2C%20Windows%20Servicing%20%26amp%3B%20Delivery)%3C%2FP%3E%3CP%3EIn%20recent%20blogs%20by%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2019%2F07%2F01%2Fevolving-windows-10-servicing-and-quality-the-next-steps%2F%22%20rel%3D%22nofollow%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EJohn%20Cable%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FMoving-to-the-next-Windows-10-feature-update-for-commercial%2Fba-p%2F732968%22%20target%3D%22_blank%22%3Emyself%3C%2FA%3E%2C%20we%20shared%20how%20Windows%2010%2C%20version%201909%20(referred%20to%20internally%20as%2019H2)%20will%20continue%20our%20efforts%20to%20improve%20the%20overall%20update%20experience%20for%20consumers%20and%20businesses.%20In%20this%20post%2C%20we%20are%20sharing%20more%20detail%20about%20the%20mechanics%20that%20will%20be%20used%20to%20provide%20those%20improvements.%3C%2FP%3E%3CP%3EBefore%20we%20describe%20what%E2%80%99s%20new%2C%20however%2C%20we%20want%20to%20clarify%20that%20if%20a%20device%20is%20running%20any%20version%20of%20Windows%2010%20earlier%20than%20version%201903%2C%20the%20process%20of%20updating%20to%20version%201909%20will%20be%20the%20same%20as%20previous%20feature%20updates.%20This%20applies%20to%20devices%20managed%20with%20Windows%20Update%20or%20Windows%20Update%20for%20Business%2C%20or%20devices%20self-managed%20with%20Windows%20Server%20Update%20Services%20(WSUS)%2C%20Configuration%20Manager%2C%20or%20other%20management%20tool.%20Again%2C%20for%20devices%20running%20Windows%2010%2C%20version%201809%20and%20previous%2C%20there%20is%20nothing%20new%20with%20the%20update%20process%20to%20version%201909.%3C%2FP%3EWhat%E2%80%99s%20new%20about%20delivering%20Windows%2010%2C%20version%201909%3CP%3EDevices%20running%20Windows%2010%2C%20version%201903%20can%20take%20advantage%20of%20a%20new%20way%20of%20servicing%20that%20leverages%20the%20same%20servicing%20technology%20used%20to%20deliver%20monthly%20quality%20updates%20to%20get%20the%20new%20features%20and%20capabilities%20available%20in%20version%201909.%20This%20enables%20you%20to%20install%20the%20update%20to%20Windows%2010%2C%20version%201909%20with%20an%20improved%20update%20experience%20and%20reduced%20downtime.%3C%2FP%3E%3CP%3EWindows%2010%2C%20versions%201903%20and%201909%20share%20a%20common%20core%20operating%20system%20with%20an%20identical%20set%20of%20system%20files.%20As%20a%20result%2C%20the%20new%20features%20in%20Windows%2010%2C%20version%201909%20were%20included%20in%20the%20latest%20monthly%20quality%20update%20for%20Windows%2010%2C%20version%201903%20(released%20October%208%2C%202019)%2C%20but%20are%20currently%20in%20a%20dormant%2Fdisabled%20state.%20These%20new%20features%20will%20remain%20dormant%20until%20they%20are%20turned%20on%20via%20an%20%E2%80%9Cenablement%20package%2C%E2%80%9D%20a%20small%2C%20quick-to-install%20%E2%80%9Cmaster%20switch%E2%80%9D%20that%20simply%20activates%20the%20Windows%2010%2C%20version%201909%20features.%3C%2FP%3E%3CP%3EThe%20enablement%20package%20is%20a%20great%20option%20for%20installing%20a%20scoped%20feature%20update%20like%20Windows%2010%2C%20version%201909%20as%20it%20allows%20you%20to%20update%20from%20version%201903%20to%20version%201909%20with%20a%20single%20restart%2C%20reducing%20update%20downtime%20and%2C%20thus%2C%20enabling%20you%20to%20take%20advantage%20of%20new%20features%20right%20away.%20Additionally%2C%20since%20Windows%2010%2C%20versions%201903%20and%201909%20share%20a%20common%20baseline%2C%20applications%20and%20drivers%20that%20worked%20with%20version%201903%20are%20designed%20to%20work%20as-is%20with%20version%201909%2C%20just%20like%20any%20Windows%2010%20quality%20update.%3C%2FP%3EHow%20to%20get%20Windows%2010%2C%20version%201909%3CP%3EAs%20stated%20above%2C%20if%20your%20device%20is%20running%20any%20version%20of%20Windows%2010%20earlier%20than%20version%201903%2C%20there%20are%20no%20changes%20to%20how%20you%20install%20Windows%2010%2C%20version%201909.%20If%20your%20devices%20are%20running%20Windows%2010%2C%20version%201903%2C%20here%20is%20guidance%20on%20how%20to%20update%20to%20Windows%2010%2C%20version%201909.%3C%2FP%3EFor%20devices%20managed%20by%20Windows%20Update%3CP%3EIf%20you%20receive%20updates%20directly%20from%20Windows%20Update%2C%20the%20Windows%2010%2C%20version%201909%20update%20will%20be%20presented%20just%20like%20any%20feature%20update.%20The%20installation%20process%20will%20be%20faster%2C%20but%2C%20as%20with%20any%20feature%20update%2C%20you%20will%20have%20the%20ability%20to%20choose%20when%20to%20install%20version%201909%20using%20the%20controls%20that%20we%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%20rel%3D%22nofollow%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Eannounced%20earlier%20this%20year%3C%2FA%3E.%3C%2FP%3E%3CP%3EIf%20you%20are%20using%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-manage-updates-wufb%22%20rel%3D%22noopener%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20Update%20for%20Business%3C%2FA%3E%2C%20you%20will%20receive%20the%20Windows%2010%2C%20version%201909%20update%20in%20the%20same%20way%20as%20prior%20feature%20updates%20and%20as%20defined%20by%20your%20feature%20update%20deferral%20policy.%20Windows%20will%20automatically%20choose%20the%20right%20path%20and%20will%20update%20devices%20already%20running%20Windows%2010%2C%20version%201903%20to%20Windows%2010%2C%20version%201909%20using%20the%20enablement%20package.%3C%2FP%3EFor%20self-managed%20devices%3CP%3EAll%20of%20the%20existing%20options%20you%20use%20to%20deploy%20feature%20updates%20are%20supported%20with%20Windows%2010%2C%20version%201909%2C%20and%20update%20media%20is%20(or%20will%20soon%20be)%20available%20in%20all%20of%20the%20normal%20channels%20(for%20more%20detailed%20information%20on%20timing%2C%20please%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fwhats-new-in-1909%22%20rel%3D%22noopener%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20IT%20Pro%20blog%3C%2FA%3E).%20Note%20that%20installing%20Windows%2010%2C%20version%201909%20via%20media%20does%20not%20provide%20the%20time%20savings%20and%20reduced%20restarts%20available%20when%20upgrading%20from%20version%201903%20to%20version%201909%20using%20the%20enablement%20package.%3C%2FP%3E%3CP%3EWe%20are%20making%20the%20Windows%2010%2C%20version%201909%20enablement%20package%20available%20on%20WSUS%20as%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4517245%22%20rel%3D%22noopener%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EKB4517245%3C%2FA%3E%2C%20which%20can%20be%20deployed%20on%20existing%20deployments%20of%20Windows%2010%2C%20version%201903.%3C%2FP%3EAdditional%20details%20Versioning%3CP%3EYou%20can%20verify%20that%20the%20Windows%2010%2C%20version%201909%20update%20was%20successful%20by%20running%20Winver%2C%20versioning%20APIs%2C%20WMI%2C%20and%20other%20common%20interfaces%2C%20and%20verifying%20that%20the%20operating%20system%20build%20number%20is%2018363.%20Because%20of%20the%20common%20baseline%2C%20even%20after%20installing%20Windows%2010%2C%20version%201909%2C%20individual%20system%20file%20versions%20will%20still%20appear%20as%2018362.%3C%2FP%3EDisk%20space%3CP%3EIf%20you%20choose%20to%20keep%20your%20devices%20on%20Windows%2010%2C%20version%201903%2C%20the%20disk-space%20overhead%20of%20the%20dormant%2Fdisabled%20features%20that%20are%20part%20of%20the%20common%20monthly%20update%20is%20less%20than%2025%20MB.%20Again%2C%20those%20features%20will%20remain%20dormant%2Fdisabled%20until%20the%20Windows%2010%2C%20version%201909%20enablement%20package%20is%20used.%3C%2FP%3EUninstall%3CP%3EIf%20you%20do%20need%20to%20uninstall%20Windows%2010%2C%20version%201909%2C%20open%20your%20Windows%20Update%20settings%20(Settings%20%26gt%3B%20Update%20%26amp%3B%20Security%20%26gt%3B%20Windows%20Update%20%26gt%3B%20View%20update%20history)%2C%20select%20Uninstall%20updates%2C%20and%20uninstall%20the%20Feature%20Update%20to%20Windows%2010%20version%201909%20via%20Enablement%20Package%20(KB4517245).%20This%20will%20revert%20the%20device%20to%20Windows%2010%2C%20version%201903.%20This%20is%20a%20separate%20path%20from%20the%20Recovery%20tab%2C%20which%20uninstalls%20the%20most%20recent%20non-servicing-based%20feature%20update.%3C%2FP%3EWindows%20Server%3CP%3EWindows%20Server%20instances%20will%20continue%20to%20receive%20Windows%20Server%2C%20version%201903%20monthly%20quality%20updates.%20The%20feature%20enablement%20package%20will%20not%20be%20automatically%20offered%20to%20Windows%20Server%20by%20Windows%20Update%2C%20nor%20will%20it%20be%20available%20in%20the%20Microsoft%20Update%20Catalog%20or%20via%20WSUS.%20Instead%2C%20refreshed%20update%20media%20will%20soon%20be%20made%20available%20for%20updating%20to%20Windows%20Server%2C%20version%201909.%3C%2FP%3E30%20months%20of%20support%3CP%3EWe%20want%20to%20conclude%20this%20post%20with%20a%20quick%20reminder.%20Devices%20running%20Windows%2010%2C%20version%201903%20receive%2018%20months%20of%20support.%20Devices%20running%20the%20Enterprise%2C%20IoT%20Enterprise%2C%20or%20Education%20editions%20of%20Windows%2010%2C%20version%201909%20receive%2030%20months%20of%20support.%20For%20more%20information%20about%20the%20Windows%20servicing%20lifecycle%2C%20please%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F13853%2Fwindows-lifecycle-fact-sheet%22%20rel%3D%22noopener%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20lifecycle%20fact%20sheet%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1002660%22%20slang%3D%22en-US%22%3E%3CP%3EFind%20out%20how%20to%20update%20devices%20running%20Windows%2010%2C%20version%201903%20to%20version%201909%20using%20a%20streamlined%20delivery%20approach.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1002660%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EServicing%20and%20updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1025223%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1025223%22%20slang%3D%22en-US%22%3E%22You%20can%20verify%20that%20the%20Windows%2010%2C%20version%201909%20update%20was%20successful%20by%20running%20Winver%2C%20versioning%20APIs%2C%20WMI%2C%20and%20other%20common%20interfaces%2C%20and%20verifying%20that%20the%20operating%20system%20build%20number%20is%2018363.%20Because%20of%20the%20common%20baseline%2C%20even%20after%20installing%20Windows%2010%2C%20version%201909%2C%20individual%20system%20file%20versions%20will%20still%20appear%20as%2018362.%22%20Any%20chance%20of%20that%20not%20being%20the%20case%20eventually%3F%20For%20one%20example%2C%201909%20machines%20report%20to%20WSUS%20as%2018362%2C%20and%20that%20pretty%20much%20blows%20all%20the%20reporting%20I%20pulled%20from%20WSUS%20out%20of%20the%20water...%20Seems%20very%20half-baked.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1033700%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F456185%22%20target%3D%22_blank%22%3E%40AceTech30%3C%2FA%3E%26nbsp%3Byou%20can%20install%20in%20on%20your%20surface%2C%20the%20only%20update%20block%20that%20I've%20seen%20is%20this%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmspoweruser.com%2Fmicrosoft-blocks-windows-10-v1909-update-for-pcs-with-old-avg-and-avast-antivirus%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmspoweruser.com%2Fmicrosoft-blocks-windows-10-v1909-update-for-pcs-with-old-avg-and-avast-antivirus%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1033706%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033706%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285725%22%20target%3D%22_blank%22%3E%40ajc196%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wish%20it%20was%20tested%20internally%20on%20real%20hardware%20with%20Microsoft's%20test%20group%20(if%20any%20still%20left%3F)%20before%20public%20release%20so%20things%20like%20that%20could%20have%20been%20identified.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1034126%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034126%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%2C%20where%20will%20I%20find%20the%20enhancement%20package%20to%20it%20on.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1034134%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034134%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F469638%22%20target%3D%22_blank%22%3E%40Kwaw210%3C%2FA%3E%26nbsp%3Bby%20%22%3CSPAN%3Eenhancement%20package%22%2C%20are%20you%20referring%20to%20the%20standalone%20cumulative%20update%20for%201909%3F%20if%20yes%20then%20here%20you%20can%20find%20it%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fuupdump.ml%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fuupdump.ml%2F%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ep.s%20all%20links%20are%20officially%20downloaded%20from%20Microsoft%20servers%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1034236%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034236%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F469638%22%20target%3D%22_blank%22%3E%40Kwaw210%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20is%20your%20device%20being%20managed%2C%20getting%20updated%20today%3F%26nbsp%3B%20Via%20Windows%20Update%2C%20or%20managed%20locally%20from%20WSUS%3F%26nbsp%3B%20Both%20are%20covered%20above%20in%20the%20blog%2C%20both%20Windows%20Update%20managed%20and%20Self%20Managed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%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-1037425%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1037425%22%20slang%3D%22en-US%22%3E%3CP%3EUpdated%20to%201909%20on%20my%20HP%20Elitebook%20and%20now%20Skype%20for%20Business%20and%20Teams%20apps%20both%20fail%20to%20login.%26nbsp%3B%20%26nbsp%3BThis%20is%20a%20corporate%20environment%20so%20a%20bit%20challenging%20when%20these%20stop%20working.%26nbsp%3B%20I%20can%20still%20access%20Teams%20via%20browser%20so%20very%20odd%20that%20just%20the%20app%20got%20broken.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1059307%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1059307%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20using%20WSUS%2C%20make%20sure%20you%20also%20have%20the%20%3CSTRONG%3EUpgrades%3C%2FSTRONG%3E%20checkbox%20checked%20in%20the%20%3CEM%3EOptions%20%26gt%3B%20Product%3C%2FEM%3Es%3CEM%3E%20and%20Classifications%3C%2FEM%3E%20section%20under%20the%20%3CEM%3EClassifications%3C%2FEM%3E%20tab.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F354758%22%20target%3D%22_blank%22%3E%40Half_Penny%3C%2FA%3E%26nbsp%3B%2C%20that%20sounds%20like%20what%20we%20started%20experiencing%20recently.%26nbsp%3B%20You%20can%20fix%20it%20by%20attempting%20to%20log-in%20with%20a%20non-existent%20user%20like%20Arbdargardawal%40yourcompany.com%20and%20then%20when%20it%20fails%20to%20login%2C%20the%20user%20cache%20will%20be%20cleared%20and%20it%20will%20let%20you%20log%20in%20again%20with%20your%20proper%20credentials.%26nbsp%3B%20Re-installing%20Teams%20also%20seems%20to%20work%2C%20but%20this%20is%20faster.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1062755%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1062755%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20we%20began%20the%20rollout%20of%201909%2C%20we%20tested%20it%20on%20our%20Technology%20Department%20computers%20before%20installing%20to%20any%20other%20machines%20in%20the%20School%20District.%20We%20had%20various%20%22strange%22%20issues.%20A%20couple%20of%20machines%20were%20simply%20like%20we%20has%20performed%20a%20complete%20reinstall%20of%20the%20OS.%20We%20had%20to%20install%20all%20apps.%20We%20had%20to%20install%20printers.%20We%20had%20to%20setup%20the%20machines%20like%20they%20were%20fresh%20out%20of%20the%20box.%20One%20machine%20had%20to%20have%20Office%20reinstalled.%20Needless%20to%20say%2C%20none%20of%20the%20test%20machines%20were%20right.%20All%20had%20something%20wrong%20with%20them.%20But%20as%20long%20as%203%20days%20later%2C%20some%20of%20the%20machines%20corrected%20themselves%20and%20were%20OK%20again%3F%3F%3F%20I%20hope%20the%20next%26nbsp%3Bversion%20of%20Windows%2010%20doesn't%20come%20with%20so%20many%20%22strange%22%20quirks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20held%20off%20pushing%20out%201909%20for%20a%20while.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1063285%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1063285%22%20slang%3D%22en-US%22%3EJust%20a%20quetion%20because%20it%20has%20been%20puzzling%20me%20for%20weeks%20now.%20I%20have%20a%20multi-bnoot%20machine%20on%20which%20I%20run%202%20versions%20of%20Windows%2010%20(Both%20Dutch)%20-1%3A%20Windows%2010%20Pro%20N%20(the%20one%20I%20most%20frequently%20use)%20-2%3A%20Windows%2010%20Pro%20(regular%2C%20non%20N)%20Strangely%20enough%20the%20%22November%202019%20Update%22%20ran%20flawlessly%20on%20the%20the%20'Non%20N'%20version%20contrary%20to%20the%20N%20version%2C%20which%20does%20download%20the%20files%2C%20installs%20up%20till%20almost%20100%25%20but%20never%20really%20finishes.%20Could%20the%20difference%20between%20%22N%22%20and%20non%20N%20explain%20this%3F%20Can%20I%20do%20something%20to%20get%20it%20running%20Or%20is%20it%20a%20matter%20of%20your%20programmers%2C%20who%20perhaps%20did%20not%20realise%20the%20differences%20between%20the%202%20versions%3F%20I%20had%20an%20equal%20problem%20installing%20the%20previous%20update.%20I%20am%20keen%20on%20reactions%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1064245%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%2C%20version%201909%20delivery%20options%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1064245%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EL%C3%A0m%20th%E1%BA%BF%20n%C3%A0o%20%C4%91%E1%BB%83%20thi%E1%BA%BFt%20b%E1%BB%8B%20c%E1%BB%A7a%20b%E1%BA%A1n%20%C4%91%C6%B0%E1%BB%A3c%20qu%E1%BA%A3n%20l%C3%BD%2C%20%C4%91%C6%B0%E1%BB%A3c%20c%E1%BA%ADp%20nh%E1%BA%ADt%20ng%C3%A0y%20h%C3%B4m%20nay%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

This post was co-authored by John Wilcox (Windows as a Service Evangelist, Windows Servicing & Delivery), Alec Oot (Principal Program Manager Lead, Windows Servicing & Delivery), and Will Patton (Senior Program Manager, Windows Servicing & Delivery)

In recent blogs by John Cable and myself, we shared how Windows 10, version 1909 (referred to internally as 19H2) will continue our efforts to improve the overall update experience for consumers and businesses. In this post, we are sharing more detail about the mechanics that will be used to provide those improvements.

Before we describe what’s new, however, we want to clarify that if a device is running any version of Windows 10 earlier than version 1903, the process of updating to version 1909 will be the same as previous feature updates. This applies to devices managed with Windows Update or Windows Update for Business, or devices self-managed with Windows Server Update Services (WSUS), Configuration Manager, or other management tool. Again, for devices running Windows 10, version 1809 and previous, there is nothing new with the update process to version 1909.

What’s new about delivering Windows 10, version 1909

Devices running Windows 10, version 1903 can take advantage of a new way of servicing that leverages the same servicing technology used to deliver monthly quality updates to get the new features and capabilities available in version 1909. This enables you to install the update to Windows 10, version 1909 with an improved update experience and reduced downtime.

Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the latest monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant/disabled state. These new features will remain dormant until they are turned on via an “enablement package,” a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.

The enablement package is a great option for installing a scoped feature update like Windows 10, version 1909 as it allows you to update from version 1903 to version 1909 with a single restart, reducing update downtime and, thus, enabling you to take advantage of new features right away. Additionally, since Windows 10, versions 1903 and 1909 share a common baseline, applications and drivers that worked with version 1903 are designed to work as-is with version 1909, just like any Windows 10 quality update.

How to get Windows 10, version 1909

As stated above, if your device is running any version of Windows 10 earlier than version 1903, there are no changes to how you install Windows 10, version 1909. If your devices are running Windows 10, version 1903, here is guidance on how to update to Windows 10, version 1909.

For devices managed by Windows Update

If you receive updates directly from Windows Update, the Windows 10, version 1909 update will be presented just like any feature update. The installation process will be faster, but, as with any feature update, you will have the ability to choose when to install version 1909 using the controls that we announced earlier this year.

If you are using Windows Update for Business, you will receive the Windows 10, version 1909 update in the same way as prior feature updates and as defined by your feature update deferral policy. Windows will automatically choose the right path and will update devices already running Windows 10, version 1903 to Windows 10, version 1909 using the enablement package.

For self-managed devices

All of the existing options you use to deploy feature updates are supported with Windows 10, version 1909, and update media is (or will soon be) available in all of the normal channels (for more detailed information on timing, please see the Windows IT Pro blog). Note that installing Windows 10, version 1909 via media does not provide the time savings and reduced restarts available when upgrading from version 1903 to version 1909 using the enablement package.

We are making the Windows 10, version 1909 enablement package available on WSUS as KB4517245, which can be deployed on existing deployments of Windows 10, version 1903.

Additional details

Versioning

You can verify that the Windows 10, version 1909 update was successful by running Winver, versioning APIs, WMI, and other common interfaces, and verifying that the operating system build number is 18363. Because of the common baseline, even after installing Windows 10, version 1909, individual system file versions will still appear as 18362.

Disk space

If you choose to keep your devices on Windows 10, version 1903, the disk-space overhead of the dormant/disabled features that are part of the common monthly update is less than 25 MB. Again, those features will remain dormant/disabled until the Windows 10, version 1909 enablement package is used.

Uninstall

If you do need to uninstall Windows 10, version 1909, open your Windows Update settings (Settings > Update & Security > Windows Update > View update history), select Uninstall updates, and uninstall the Feature Update to Windows 10 version 1909 via Enablement Package (KB4517245). This will revert the device to Windows 10, version 1903. This is a separate path from the Recovery tab, which uninstalls the most recent non-servicing-based feature update.

Windows Server

Windows Server instances will continue to receive Windows Server, version 1903 monthly quality updates. The feature enablement package will not be automatically offered to Windows Server by Windows Update, nor will it be available in the Microsoft Update Catalog or via WSUS. Instead, refreshed update media will soon be made available for updating to Windows Server, version 1909.

30 months of support

We want to conclude this post with a quick reminder. Devices running Windows 10, version 1903 receive 18 months of support. Devices running the Enterprise, IoT Enterprise, or Education editions of Windows 10, version 1909 receive 30 months of support. For more information about the Windows servicing lifecycle, please see the Windows lifecycle fact sheet.

48 Comments
Occasional Visitor

Can I install this on my Surface Book 2?  

Frequent Visitor

1909 broke my surface pro

Occasional Visitor

Couldn't have said it better myself, arrived to work today to an absolute sh** show ! Bah humbug

Microsoft

@AceTech30 

 

Yes, you can install it on any Windows 10 machine.  I myself am a Surface Book 2 user and have been running it for months. 

Microsoft

@Sjrjaj 

 

Please, tell me more, 

What does "broke" mean.  Were you upgrading from 1903? 

 

contact me @johnwilc@microsoft.com and I'll make sure you get assistance. 

Microsoft


So the latest monthly quality update for Windows 10, version 1903 (released October 8, 2019); which includes the new features in Windows 10, version 1909 which are currently in a dormant/disabled state will remain so, for example for the full Windows 10 Pro 1903 support lifecycle (Dec. 8, 2020) unless the KB referred to is installed? We can continue to defer feature updates while still receiving quality updates? Feature updates are being moved from March, September releases to December, June as I understand but the frequency will remain the same as indicated? 

Microsoft

@RaaMata 

 

1903 will have 18 month servicing lifecycle,  during which it will receive quality updates.

1909 will have 30 months, for Enterprise and Education SKUs. 

 

you did not say how your device is being managed, but its covered above.  You mentioned "deferred" so you may be WuFB managed. If so, we adhere to your WuFB deferral settings. 

 

 

Frequent Visitor

Hi John

 

How can i find the "Feature Update to Windows 10 version 1909 via Enablement Package (KB4517245)"  in SCCM?

 

I cant find the KB4517245 in SCCM console. Im using SCCM CB version 1902. We have clients on 1903 and I don't want to deploy the complete 1909 .wim file , all I want is the "small" enablement package to update my 1903 users.

 

Denco

Microsoft

@denco-86 

 

This is what you want

 

clipboard_image_0.png

Frequent Visitor

Hi John

 

Can you show me in the SCCM Console under the "Software Library > All Software Updates " node please?

If that is not possible can you show me how to download the KB4517245 patch offline please?

 

Denco

Occasional Contributor

@John Wilcox     For Windows 10 version lower than 1903 how do you use SCCM to get to version 1909 ?   Thanks for posting that information on 1903 --> 1909 using WSUS/SCCM as we would have never figured that out

Occasional Contributor

@John Wilcox   Also in our WSUS - KB4517245  does show up - but for some reason we cannot get SCCM to pick up this.     Is there any articles on how exactly to do this?

Microsoft

@denco-86 @Eric Sabo Please make sure you have the “Windows 10, version 1903 and later” product and “Upgrades” classification selected in your Software Update Point site component. Both the enablement package, for devices on 1903, and normal feature update, for devices on earlier Windows 10 releases, should show in the “Windows 10 Servicing” \ “All Windows 10 Updates” node, not the “All Software Updates” node as these are feature upgrades. Also note that you can’t search “KB4517245” as it’s not in the title, search just “4517245” or "enablement"

clipboard_image_1.png

Occasional Contributor

Rae,

 

Thanks that helped a lot - we were looking under All Software Updates.    Thanks again

Super Contributor

We have updated one 1903 machine with an enablement package update via WSUS and in winver it shows new build 18363, but in WSUS it is still 18362 after latest report. Main WSUS server is on Windows Server 2012 R2 and downstream server with this machine is also on Windows Server 2012 R2.

Occasional Visitor

Getting things ready - 94%

download gets stuck at the above  for hours, tried restarting didn't work, any suggestions besides deleting the update?

bellskee@aol.com

Microsoft

@bellskee 

 

Please share some more context..

 

What are you upgrading from?

How are you updating? WU, WuFB, WSUS?

 

 

Super Contributor

Single restart huh? I just ran 1909 update (pressed Download and install now link on Updates page in Settings) on a fully updated 1903 laptop. It downloaded and presented Restart now button. I pressed it. It rebooted, showed usual updates installing view with percents and then rebooted again and then booted into Windows desktop (autologon enabled). So, not exactly one restart :) At least in my case. Some cheap ASUS laptop.

New Contributor
My existing PC is dual-boot Win 7 Pro 64-bit and Win 10 Pro 64-bit (now at version 1903). A Dell Optiplex 7010 with Intel Core i5 3470, plenty of hard drive storage and 16GB RAM. So far, updates to each OS have NOT affected the other, as far as I can tell. Is there anything different about doing the new update of the Win 10 side to version 1909 that might affect the Win 7 side and the current, working dual-booting? Thanks.
Frequent Visitor

Hi John,

In corporate environment (W10 Enterprise, Windows Update for Business, deployment rings...) is it possible to make this feature update mandatory, just like the previous ones ? Most of our users do not want to deal with updates and were ok with existing installation options (especially when restart is as fast as this one).

Microsoft

@David Glanz 

 

Hi David,

 

Should not be a problem.  The servicing pipelines are separate, and the update process in this case, same as monthly, you have been using for sometime now with now issues.

 

 

 

Super Contributor

Tried to move test machine with 1909 version to WSUS server on Windows Server 2016 and it still reports 18362.449 (2 instead of 3). I guess will have to wait for OS hosting WSUS patch to fix reporting?

Occasional Visitor

@John Wilcox

 

Not sure if this is right forum, however:

 

Downloading newly released Danish Window 10 Enterprise 1909, from VLSC, I believe either the Install.wim is wrongly numbered, or the files are backlevel!

 

This is what shows (Version : 10.0.18362 => 1903):

 

D:\Sources>dism /get-imageinfo /imagefile:g:\sources\install.wim /index:3

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Details for image : g:\sources\install.wim

Index : 3
Name : Windows 10 Enterprise
Description : Windows 10 Enterprise
Size : 14.647.013.793 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.18362
ServicePack Build : 418
ServicePack Level : 0
Edition : Enterprise
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 22289
Files : 95438
Created : 07-10-2019 - 04:21:32
Modified : 07-10-2019 - 04:38:44
Languages :
da-DK (Default)
The operation completed successfully.

Super Contributor

This is expected as 1909 is just a CU of 1903.

 

"Because of the common baseline, even after installing Windows 10, version 1909, individual system file versions will still appear as 18362."

Occasional Visitor

@Oleg K The build shows in the client operating system as 18363 so surely this should be reported to WSUS/SCCM as the correct build? Even a CU affects the build number

Super Contributor

@polaris CU updates the number after the dot and this is a CU number, not a build number, which is first 5 digits. In my case CU digits are reported correctly, but not the build digits. I'm guessing WSUS is maybe identifying OS by some system file, which hasn't changed in 1909. But it does show CU number correctly, so maybe not it.

Occasional Visitor

@Oleg K What CU number are you seeing? I am getting .449 for clients that are on either 1909 or 1903

Super Contributor

Yes, it is .449 for 1909 and 1903.

 

But actually winver for 1903 and 1909 shows .476. I think first it was .449 after the 1909 update, but now some other update installed and it went higher, but WSUS for some reason is not reflecting this.

Occasional Contributor

Hi, we have freshly installed 1903 machines in fr-ca with OSD with the October cumulative update installed. The enablement Package has been deployed (available) to those machines, but they don't show up in software center)

 

Are we missing something? We're on CB 1902 with the hotfix.

 

Thks in advance and don't hesitate if you have any questions.

Microsoft

@Stephane Lalancette do your clients have the prerequisite 1903 cumulative and servicing stack updates installed?

 

See prerequisites listed here: 

https://support.microsoft.com/en-us/help/4517245/feature-update-via-windows-10-version-1909-enableme...

or here:

https://docs.microsoft.com/en-us/configmgr/sum/get-started/configure-classifications-and-products?wi... 

 

If you have the prerequisites installed, what does the state of the enablement package update report as for the clients in deployment monitoring?

Microsoft

@polaris @Oleg K Where in WSUS/ConfigMgr are you seeing the OS build number incorrectly represented as 18362 instead of 18363? In ConfigMgr, I see the Operating System Build correctly represented:

clipboard_image_1.png

Occasional Visitor

@Rae_Goodhart I am just using WSUS but it looks similar to the screenshot you have posted (without the correct build/CU of course)

Super Contributor

Yep, in WSUS there is no Operating System Build column. It is called "Version" column and it shows 18362.449 for some reason for 1909, although it should be 18363.476. And it looks like it also shows it wrong for 1903 for me. It should be 18362.476, but it shows 18362.449. It's like it got stuck after it received these new 1909 updates.

Microsoft

@Oleg K @polaris The Version in WSUS is based on the version of the Windows update client, which does not change to 18363, it's more of a binary version.  For the CU issue, not all cumulative updates patch the component of Windows that is the Windows update client, and in this case .476 appears to not have updated the Windows update client itself, so the Version remains. I don't believe this is related to 1909/1903 enablement package, it just happens that this cummulative update didn't need to make any changes in the Windows update client component of Windows.

Super Contributor

So, WSUS admins have no reliable source of information about a real version of Windows 10? It seems that smaller feature updates have their own problem now. Or we should just approve them and hope they install without checking (no Needed shown at least) :)

Senior Member

@Oleg K

 

You would expect the 1909 release to contain any CU's inbetween 1903 and 1909, and the version/build number reflecting this - alas version should be 10.0.18363, not 10.0.18362.

 

And please note that I'm refering to the Install.wim, not individual files.

 

I appears MS managed to make a total mess out of this, that everyone now has to spend numerous hours to Work around - total Waste of everyones time. MS please call in some proffesionals….

Senior Member
"You can verify that the Windows 10, version 1909 update was successful by running Winver, versioning APIs, WMI, and other common interfaces, and verifying that the operating system build number is 18363. Because of the common baseline, even after installing Windows 10, version 1909, individual system file versions will still appear as 18362." Any chance of that not being the case eventually? For one example, 1909 machines report to WSUS as 18362, and that pretty much blows all the reporting I pulled from WSUS out of the water... Seems very half-baked.
Respected Contributor

@AceTech30 you can install in on your surface, the only update block that I've seen is this

https://mspoweruser.com/microsoft-blocks-windows-10-v1909-update-for-pcs-with-old-avg-and-avast-anti...

Respected Contributor

@ajc196 

I wish it was tested internally on real hardware with Microsoft's test group (if any still left?) before public release so things like that could have been identified.

Occasional Visitor

Please, where will I find the enhancement package to it on.

Respected Contributor

@Kwaw210 by "enhancement package", are you referring to the standalone cumulative update for 1909? if yes then here you can find it:

https://uupdump.ml/

 

p.s all links are officially downloaded from Microsoft servers

Regular Visitor

@Kwaw210 

 

How is your device being managed, getting updated today?  Via Windows Update, or managed locally from WSUS?  Both are covered above in the blog, both Windows Update managed and Self Managed. 

 

 

 

 

Occasional Contributor

Updated to 1909 on my HP Elitebook and now Skype for Business and Teams apps both fail to login.   This is a corporate environment so a bit challenging when these stop working.  I can still access Teams via browser so very odd that just the app got broken.

Occasional Visitor

If using WSUS, make sure you also have the Upgrades checkbox checked in the Options > Products and Classifications section under the Classifications tab.

And @Half_Penny , that sounds like what we started experiencing recently.  You can fix it by attempting to log-in with a non-existent user like Arbdargardawal@yourcompany.com and then when it fails to login, the user cache will be cleared and it will let you log in again with your proper credentials.  Re-installing Teams also seems to work, but this is faster.

Occasional Visitor

When we began the rollout of 1909, we tested it on our Technology Department computers before installing to any other machines in the School District. We had various "strange" issues. A couple of machines were simply like we has performed a complete reinstall of the OS. We had to install all apps. We had to install printers. We had to setup the machines like they were fresh out of the box. One machine had to have Office reinstalled. Needless to say, none of the test machines were right. All had something wrong with them. But as long as 3 days later, some of the machines corrected themselves and were OK again??? I hope the next version of Windows 10 doesn't come with so many "strange" quirks.

 

We held off pushing out 1909 for a while.

Occasional Visitor
Just a quetion because it has been puzzling me for weeks now. I have a multi-bnoot machine on which I run 2 versions of Windows 10 (Both Dutch) -1: Windows 10 Pro N (the one I most frequently use) -2: Windows 10 Pro (regular, non N) Strangely enough the "November 2019 Update" ran flawlessly on the the 'Non N' version contrary to the N version, which does download the files, installs up till almost 100% but never really finishes. Could the difference between "N" and non N explain this? Can I do something to get it running Or is it a matter of your programmers, who perhaps did not realise the differences between the 2 versions? I had an equal problem installing the previous update. I am keen on reactions
Occasional Visitor

Làm thế nào để thiết bị của bạn được quản lý, được cập nhật ngày hôm nay?