Support Tip: Take Action to Ensure MSfB Apps deployed through Intune Install on Windows 10 1903

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.  

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)

Neil_a_Consultant  I believe the best way to fix the stuck machines is to deploy the KB and reboot the machines.

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.

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? 

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.

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

Jelle Revyn, Please see Michael's comments around the availability of the new ISO

https://techcommunity.microsoft.com/t5/Microsoft-Intune/Windows-10-1903-Autopilot-always-fails-at-user-app-deployment/td-p/477619 

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

TheAutisticTechieWhat "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