Home
%3CLINGO-SUB%20id%3D%22lingo-sub-658864%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658864%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EBy%20Scott%20Duffey%20%7C%20Sr.%20PM%2C%20Intune%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EIn%20early%20versions%20of%20Windows%2010%201903%20(builds%20older%20than%2018362.145)%2C%20there%20was%20a%20known%20issue%20several%20of%20you%20found%20where%20online%20licensed%20Microsoft%20Store%20for%20Business%20(MSfB)%20apps%20deployed%20through%20Intune%20failed%20to%20install.%20If%20these%20apps%20were%20named%20as%20part%20of%20the%20Enrollment%20Status%20Page%20(ESP)%20configuration%20to%26nbsp%3B%20%E2%80%9CBlock%20device%20use%20until%20these%20required%20apps%20are%20installed%20if%20they%20are%20assigned%20to%20the%20user%2Fdevice%E2%80%9D%20then%20this%20might%20have%20caused%20a%20timeout%20to%20the%20ESP%20and%20impacted%20device%20setup.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20fix%20for%20this%20issue%20has%20now%20shipped.%20There%E2%80%99s%20several%20options%20now%20to%20resolve%20or%20workaround%20this%20issue%2C%20including%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUpdate%20all%20Windows%2010%201903%20devices%20with%20the%20Windows%2010%20May%20update%20(2019-05%20Cumulative%20Update%20(KB4497935))%20%3CA%20href%3D%22https%3A%2F%2Fwww.catalog.update.microsoft.com%2FSearch.aspx%3Fq%3DKB4497935%22%20target%3D%22_self%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%22%3Ehttps%3A%2F%2Fwww.catalog.update.microsoft.com%2FSearch.aspx%3Fq%3DKB4497935%3C%2FA%3E.%20This%20update%20includes%20a%20fix%20to%20the%20StoreInstall%20CSP%20where%20the%20issue%20is%20resolved.%3C%2FLI%3E%0A%3CLI%3EDeploy%20the%20offline%20licensed%20version%20of%20MSfB%20apps.%3C%2FLI%3E%0A%3CLI%3ERemove%20online%20licensed%20MSfB%20apps%20as%20blocking%20in%20the%20Enrollment%20Status%20Page%20profile.%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-658864%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20latest%20Windows%20release%20fixes%20an%20occasionally%20referenced%20error%20using%20Microsoft%20Store%20for%20Business%20apps%20deployed%20through%20Intune%20on%20Windows%2010%201903.%20You%20can%20apply%20the%20KB%20article%20now!%20Read%20more%20below.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-658864%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMSfB%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-661741%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661741%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20lets%20say%20we%20have%20an%20autopilot%20deployment%20that%20gets%20stuck%20here.%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20recovery%20process%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20removing%20the%20blocking%20of%20the%20ESP%20allow%20it%20to%20proceed%20with%20a%20reboot%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20few%20stations%20stuck%20..%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20get%20the%20user%20(no%20local%20admin)%20to%20the%20Settings%20-%26gt%3B%20Account%20-%20%26gt%3B%20Work%20Settings%20-%26gt%3B%20Info%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Device%20sync%20status%3C%2FP%3E%3CP%3ELast%20Attempted%20Sync%3A%3C%2FP%3E%3CP%3EThe%20sync%20could%20not%20be%20initiated%20(0x80190190)%3C%2FP%3E%3CP%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20going%20to%20try%20a%20local%20non-mdm%20reset%20(company%20portal%2C%20manually%20installed%20doesn't%20think%20the%20device%20is%20enrolled)%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-666014%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666014%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218462%22%20target%3D%22_blank%22%3E%40Consult-a%20null%3C%2FA%3E%26nbsp%3B%20I%20believe%20the%20best%20way%20to%20fix%20the%20stuck%20machines%20is%20to%20deploy%20the%20KB%20and%20reboot%20the%20machines.%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-671849%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-671849%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20more%20guidance%20that%20might%20help%20you%20in%20testing%20the%20update%3A%3C%2FP%3E%0A%3CP%3EYou%20can%20download%20the%20KB4497935%20patch%20and%20copy%20the%20msu%20file%20to%20the%20USB.%20When%20you%20get%20to%20the%20Region%20page%20in%20OOBE%2C%20press%20Shift%20%2B%20F10%20to%20open%20command%20prompt.%20Go%20to%20the%20usb%20and%20run%20the%20msu%20file.%20This%20will%20install%20the%20patch%20and%20reboot.%20Once%20rebooted%20it%20will%20go%20back%20to%20the%20region%20page%20and%20you%20can%20continue%20the%20installation%20as%20normal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678268%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678268%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F116732%22%20target%3D%22_blank%22%3E%40Scott%20Duffey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20really%20liked%20this%20announcement%2C%20but%20after%20testing%20we%20have%20to%20state%20that%20this%20is%20only%20true%20for%20the%20%22generic%22%20store%20apps%20(e.g.%20Company%20Portal%2C%20OneNote).%20%3CSTRONG%3EIt%20is%20still%20the%20case%20that%20the%20deployment%20process%20halts%20with%20our%20own%20LOB%20store%20apps%20in%201903%3C%2FSTRONG%3E%2C%20which%20we%20require%20to%20deploy%20in%20the%20AutoPilot%20process%20as%20well.%20Is%20that%20already%20known%20at%20Microsoft%20and%20are%20you%20working%20on%20this%20as%20well%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678307%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678307%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F238655%22%20target%3D%22_blank%22%3E%40Thomas%20Haller%3C%2FA%3E%26nbsp%3BAre%20you%20saying%20that%20you%20have%20some%20online%20licensed%20MSFB%20apps%20that%20are%20still%20not%20being%20delivered%20after%20applying%20the%20update%20and%20that%20the%20common%20theme%20with%20the%20failed%20apps%20is%20that%20they%20were%20developed%20in-house%20and%20submitted%20to%20the%20store%20via%20the%20dev%20center%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIm%20not%20aware%20of%20any%20issues%20with%20that%20scenario.%20As%20I%20understand%20the%20fix%20to%20the%20CSP%2C%20how%20the%20app%20got%20to%20the%20store%20shouldn%E2%80%99t%20make%20any%20difference.%3C%2FP%3E%0A%3CP%3EI%E2%80%99d%20make%20sure%20that%20the%20your%20app%20can%20be%20installed%20manually%20on%201903%2C%20if%20that%20doesn%E2%80%99t%20work%20manually%20then%20there%20might%20be%20something%20wrong%20with%20the%20app.%20If%20that%20works%20but%20still%20fails%20via%20Intune%2FStore%20CSP%20please%20raise%20a%20support%20call%20with%20us%20and%20we%20can%20follow%20up.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682818%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682818%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%20had%202%20test%20devices%20that%20were%20running%201903%20(Build%2018362.30%20-%20clean%20install%20from%20Media%20Creation%20Tool).%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EBut%20Shift%20%2B%20F10%20wasn't%20working%2C%20I%20got%20the%20pop-up%20asking%20for%20credentials%20and%20after%20entering%2C%20the%20command%20prompt%20just%20didn't%20show.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20did%20work%20for%20me%20was%20%22ctrl%2Bshift%2Besc%22%20-%26gt%3B%20File%20-%26gt%3B%20New%20Task%20-%26gt%3B%20cmd%3CBR%20%2F%3Eand%20then%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Ewusa.exe%20D%3A%5Cwindows10.0-kb4497935-x64_e1e15758afc9d32ca57779428d145cfba3a12e4b.msu%3C%2FPRE%3E%3CP%3ED%3A%5C%20%3D%20location%20of%20my%20USB%20device%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F116732%22%20target%3D%22_blank%22%3E%40Scott%20Duffey%3C%2FA%3EAny%20idea%20when%20a%20new%20build%20(%26gt%3B%3D%20.145)%20is%20released%20to%20the%20media%20creation%20tool%20or%20VLSC%3F%20When%20checking%20the%20properties%20from%20MediaCreationTool1903.exe%20under%20details%2C%20the%20version%20shows%2010.0.18362.1.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20I%20downloaded%20the%20.ISO%20file%20again%20and%20checked%20the%20install.esd%20(or%20install.wim)%20to%20get%20the%20specific%20build%20number%20but%20it%20was%20still%20the%20same%20.30%20version.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3CSPAN%3EIsn't%20there%20a%20better%20way%20to%20check%20the%20version%20without%20downloading%20the%20ISO%20over%20and%20over%20again%3F%3C%2FSPAN%3E%26nbsp%3B%20%3C%2FP%3E%3CP%3E%3CSPAN%3ESame%20with%20the%20Volume%20Licensing%20Service%20Center%20only%20shows%20version%20number%201903%20not%20build%20number.%3CBR%20%2F%3E%3CBR%20%2F%3EAnother%20option%20is%20slipstreaming%20the%20msu%20into%20Windows%20but%20a%20full%20download%20of%20a%20Windows%2010%201903%20build%2018362.145%20or%20higher%20would%20just%20be%20so%20much%20easier.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EJelle%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683071%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90033%22%20target%3D%22_blank%22%3E%40Jelle%20Revyn%3C%2FA%3E%2C%20Please%20see%20Michael's%20comments%20around%20the%20availability%20of%20the%20new%20ISO%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Intune%2FWindows-10-1903-Autopilot-always-fails-at-user-app-deployment%2Ftd-p%2F477619%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Intune%2FWindows-10-1903-Autopilot-always-fails-at-user-app-deployment%2Ftd-p%2F477619%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-696033%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-696033%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90033%22%20target%3D%22_blank%22%3E%40Jelle%20Revyn%3C%2FA%3E%26nbsp%3BIgnore%20me%2C%20i%20pasted%20and%20submitted%20into%20the%20wrong%20open%20tab!%20Sorry%20for%20the%20confusion%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-695955%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695955%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRIKE%3EI've%20installed%201903%20from%20MPN%2C%20gone%20into%20Audit%20Mode%20to%20get%20the%20auopilot%20info%20and%20uploaded%20to%20Intune.%20Then%20as%20per%20above%20I%20have%20installed%20the%20update%20and%20sysprepped.%20This%20gives%20the%20AUTOPILOTUPDATE%20message%20so%20I%20installed%20the%20June%20update%20to%20bring%20the%20build%20number%20to%2018362.175%2C%20sysprepped%20again%20which%20also%20gives%20the%20same%20error%20message.%20I%20then%20sysprepped%20with%20generalise%20which%20also%20gives%20the%20message.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EWhat%20am%20I%20missing%3F%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECommented%20on%20wrong%20thread%2C%20please%20ignore%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-695977%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316490%22%20target%3D%22_blank%22%3E%40danmurphy%3C%2FA%3E%3CSTRIKE%3EWhat%20%22AUTOPILOTUPDATE%22%20message%20are%20you%20talking%20about%3F%3C%2FSTRIKE%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRIKE%3EThe%20bug%20that's%20fixed%20in%20builds%20older%20than%2018362.145%20is%20that%20the%20autopilot%20process%20fails%20to%20install%20MSfB%20apps%20that%20are%20marked%20as%20%22required%22%20in%20the%20Enrollment%20Status%20Page%20(ESP).%3C%2FSTRIKE%3E%3CBR%20%2F%3E%3CBR%20%2F%3EPS%3A%20Why%20are%20you%20sysprepping%3F%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fmniehaus%2F2018%2F10%2F25%2Fspeeding-up-windows-autopilot-for-existing-devices%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%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%3ECheck%20Michael's%20blog%20about%20Speeding%20up%20Windows%20Autopilot%20for%20existing%20devices%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700350%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700350%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F116732%22%20target%3D%22_blank%22%3E%40Scott%20Duffey%3C%2FA%3E%26nbsp%3BAre%20you%20saying%20that%20you%20have%20some%20online%20licensed%20MSFB%20apps%20that%20are%20still%20not%20being%20delivered%20after%20applying%20the%20update%20and%20that%20the%20common%20theme%20with%20the%20failed%20apps%20is%20that%20they%20were%20developed%20in-house%20and%20submitted%20to%20the%20store%20via%20the%20dev%20center%3F%3CEM%3E%20%3CSTRONG%3EYES.%20We%20even%20resubmitted%20the%20app%2C%20but%20this%20not%20change%20anything.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIm%20not%20aware%20of%20any%20issues%20with%20that%20scenario.%20As%20I%20understand%20the%20fix%20to%20the%20CSP%2C%20how%20the%20app%20got%20to%20the%20store%20shouldn%E2%80%99t%20make%20any%20difference.%3C%2FP%3E%3CP%3EI%E2%80%99d%20make%20sure%20that%20the%20your%20app%20can%20be%20installed%20manually%20on%201903%2C%20if%20that%20doesn%E2%80%99t%20work%20manually%20then%20there%20might%20be%20something%20wrong%20with%20the%20app.%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3EThis%20works%20fine.%26nbsp%3B%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20that%20works%20but%20still%20fails%20via%20Intune%2FStore%20CSP%20please%20raise%20a%20support%20call%20with%20us%20and%20we%20can%20follow%20up.%20%3CSTRONG%3E%3CEM%3EWill%20do%20this%2C%20as%20we%20have%20this%20issue%20in%20different%20tenants.%20Still%20no%20one%20else%20with%20the%20same%20issue%3F%26nbsp%3B%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-741640%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-741640%22%20slang%3D%22en-US%22%3ETried%20a%20build%20with%20the%20latest%20Win10%201903%20(June%20release)%20Image%20and%20found%20that%20the%20Install%20STILL%20hung%20when%20trying%20to%20install%20apps%20from%20MSfB%20(company%20portal).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-741988%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-741988%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16798%22%20target%3D%22_blank%22%3E%40Ivan%20Webb%3C%2FA%3Ewhat%20error%20did%20you%20get%3F%20And%20I%20assume%20it%20hung%20when%20you're%20using%20the%20ESP%20(Enrollment%20Status%20Page).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-774359%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774359%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16798%22%20target%3D%22_blank%22%3E%40Ivan%20Webb%3C%2FA%3E!%20Just%20to%20confirm%2C%20with%20the%20most%20recent%20update%2C%20deploying%20the%20offline%20licensed%20version%20of%20MSfB%20apps%2C%20and%20removing%20the%20online%20licensed%20MSfB%20apps%20as%20blocking%20within%20the%20Enrollment%20Status%20Page%20profile%2C%20that%20the%20issue%20still%20persists%3F%3C%2FP%3E%0A%3CP%3EIf%20installing%20the%20app%20manually%2C%20does%20the%20app%20install%20without%20any%20issues%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777406%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777406%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20doesn't%20look%20like%26nbsp%3B%3CSPAN%3EKB4497935%26nbsp%3B%20fixes%20the%20problem%20for%20us.%26nbsp%3B%20We%20have%20PCs%20on%2018362.239%20which%20can't%20install%20any%20apps%20from%20the%20Company%20Portal.%26nbsp%3B%20They%20could%20when%20they%20were%20on%201809.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-782465%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-782465%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16798%22%20target%3D%22_blank%22%3E%40Ivan%20Webb%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153916%22%20target%3D%22_blank%22%3E%40Daryl%20Theobalds%3C%2FA%3E!%3C%2FP%3E%0A%3CP%3EFor%20the%20apps%20you%20are%20having%20an%20issue%20with%2C%20are%20they%20LOB%20apps%20in%20the%20MSfB%20or%20public%20apps%3F%3C%2FP%3E%0A%3CP%3EA%20quick%20note%20that%20we've%20had%20other%20customers%20raise%20similar%20issues%20as%20you've%20both%20commented%2C%20and%20we%20are%20currently%20investigating.%3C%2FP%3E%0A%3CP%3ELet's%20raise%20a%20new%20support%20case%20via%20the%20Intune%20Admin%20console's%20Help%20and%20Support.%20Our%20support%20team%20would%20be%20happy%20to%20further%20assist%20with%20resolving%20your%20issue.%20Feel%20free%20to%20direct%20message%20us%20with%20your%20support%20case%20number%20for%20follow%20up!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785419%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Take%20Action%20to%20Ensure%20MSfB%20Apps%20deployed%20through%20Intune%20Install%20on%20Windows%2010%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785419%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune%20Support%20Team%3C%2FA%3E%26nbsp%3B%20The%20apps%20we%20are%20unable%20to%20install%20are%20standard%20public%20apps%20such%20as%20'Windows%20Voice%20Recorder'.%26nbsp%3B%20I%20have%20logged%20a%20ticket%20with%20support.%20Will%20let%20you%20know%20how%20I%20get%20on.%3C%2FP%3E%3C%2FLINGO-BODY%3E

By Scott Duffey | Sr. PM, Intune

In early versions of Windows 10 1903 (builds older than 18362.145), there was a known issue several of you found where online licensed Microsoft Store for Business (MSfB) apps deployed through Intune failed to install. If these apps were named as part of the Enrollment Status Page (ESP) configuration to  “Block device use until these required apps are installed if they are assigned to the user/device” then this might have caused a timeout to the ESP and impacted device setup.

 

The fix for this issue has now shipped. There’s several options now to resolve or workaround this issue, including:

  1. Update all Windows 10 1903 devices with the Windows 10 May update (2019-05 Cumulative Update (KB4497935)) https://www.catalog.update.microsoft.com/Search.aspx?q=KB4497935. This update includes a fix to the StoreInstall CSP where the issue is resolved.
  2. Deploy the offline licensed version of MSfB apps.
  3. Remove online licensed MSfB apps as blocking in the Enrollment Status Page profile.
17 Comments
Occasional Contributor

So lets say we have an autopilot deployment that gets stuck here. 

What is the recovery process? 

 

Will removing the blocking of the ESP allow it to proceed with a reboot?

 

I have a few stations stuck .. 

 

When I get the user (no local admin) to the Settings -> Account - > Work Settings -> Info

 

"Device sync status

Last Attempted Sync:

The sync could not be initiated (0x80190190)

"

 

 

I am going to try a local non-mdm reset (company portal, manually installed doesn't think the device is enrolled)

 

 

Microsoft

@Consult-a null  I believe the best way to fix the stuck machines is to deploy the KB and reboot the machines.

 

 

Microsoft

Some more guidance that might help you in testing the update:

You can download the KB4497935 patch and copy the msu file to the USB. When you get to the Region page in OOBE, press Shift + F10 to open command prompt. Go to the usb and run the msu file. This will install the patch and reboot. Once rebooted it will go back to the region page and you can continue the installation as normal.

New Contributor

Hi @Scott Duffey 

We really liked this announcement, but after testing we have to state that this is only true for the "generic" store apps (e.g. Company Portal, OneNote). It is still the case that the deployment process halts with our own LOB store apps in 1903, which we require to deploy in the AutoPilot process as well. Is that already known at Microsoft and are you working on this as well? 

Microsoft

Hi @Thomas Haller Are you saying that you have some online licensed MSFB apps that are still not being delivered after applying the update and that the common theme with the failed apps is that they were developed in-house and submitted to the store via the dev center?

 

Im not aware of any issues with that scenario. As I understand the fix to the CSP, how the app got to the store shouldn’t make any difference.

I’d make sure that the your app can be installed manually on 1903, if that doesn’t work manually then there might be something wrong with the app. If that works but still fails via Intune/Store CSP please raise a support call with us and we can follow up.

 

New Contributor

I had 2 test devices that were running 1903 (Build 18362.30 - clean install from Media Creation Tool).

But Shift + F10 wasn't working, I got the pop-up asking for credentials and after entering, the command prompt just didn't show.

 

What did work for me was "ctrl+shift+esc" -> File -> New Task -> cmd
and then

 

wusa.exe D:\windows10.0-kb4497935-x64_e1e15758afc9d32ca57779428d145cfba3a12e4b.msu

D:\ = location of my USB device

 

 

@Scott DuffeyAny idea when a new build (>= .145) is released to the media creation tool or VLSC? When checking the properties from MediaCreationTool1903.exe under details, the version shows 10.0.18362.1.

So I downloaded the .ISO file again and checked the install.esd (or install.wim) to get the specific build number but it was still the same .30 version.

Isn't there a better way to check the version without downloading the ISO over and over again? 

Same with the Volume Licensing Service Center only shows version number 1903 not build number.

Another option is slipstreaming the msu into Windows but a full download of a Windows 10 1903 build 18362.145 or higher would just be so much easier.

 

Jelle

Microsoft
Occasional Contributor

I've installed 1903 from MPN, gone into Audit Mode to get the auopilot info and uploaded to Intune. Then as per above I have installed the update and sysprepped. This gives the AUTOPILOTUPDATE message so I installed the June update to bring the build number to 18362.175, sysprepped again which also gives the same error message. I then sysprepped with generalise which also gives the message.

 

What am I missing?

 

Commented on wrong thread, please ignore

New Contributor

@danmurphyWhat "AUTOPILOTUPDATE" message are you talking about?

The bug that's fixed in builds older than 18362.145 is that the autopilot process fails to install MSfB apps that are marked as "required" in the Enrollment Status Page (ESP).

PS: Why are you sysprepping? Check Michael's blog about Speeding up Windows Autopilot for existing devices

Occasional Contributor

@Jelle Revyn Ignore me, i pasted and submitted into the wrong open tab! Sorry for the confusion

New Contributor

@Scott Duffey Are you saying that you have some online licensed MSFB apps that are still not being delivered after applying the update and that the common theme with the failed apps is that they were developed in-house and submitted to the store via the dev center? YES. We even resubmitted the app, but this not change anything.

 

Im not aware of any issues with that scenario. As I understand the fix to the CSP, how the app got to the store shouldn’t make any difference.

I’d make sure that the your app can be installed manually on 1903, if that doesn’t work manually then there might be something wrong with the app.

This works fine. 

 

If that works but still fails via Intune/Store CSP please raise a support call with us and we can follow up. Will do this, as we have this issue in different tenants. Still no one else with the same issue? 

Regular Visitor
Tried a build with the latest Win10 1903 (June release) Image and found that the Install STILL hung when trying to install apps from MSfB (company portal).
New Contributor

@Ivan Webbwhat error did you get? And I assume it hung when you're using the ESP (Enrollment Status Page).

 

Hi @Ivan Webb! Just to confirm, with the most recent update, deploying the offline licensed version of MSfB apps, and removing the online licensed MSfB apps as blocking within the Enrollment Status Page profile, that the issue still persists?

If installing the app manually, does the app install without any issues?

Senior Member

It doesn't look like KB4497935  fixes the problem for us.  We have PCs on 18362.239 which can't install any apps from the Company Portal.  They could when they were on 1809.  

Hello @Ivan Webb@Daryl Theobalds!

For the apps you are having an issue with, are they LOB apps in the MSfB or public apps?

A quick note that we've had other customers raise similar issues as you've both commented, and we are currently investigating.

Let's raise a new support case via the Intune Admin console's Help and Support. Our support team would be happy to further assist with resolving your issue. Feel free to direct message us with your support case number for follow up!

Senior Member

@Intune Support Team  The apps we are unable to install are standard public apps such as 'Windows Voice Recorder'.  I have logged a ticket with support. Will let you know how I get on.