Windows 10 1903 Autopilot always fails at user app deployment stage

You can download the KB4497935 patch and copy the msu file to the USB. When you get to the Region page, 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. I tried this and everything was installed without any issues.

Not sure how supported this is but it works and it makes it possible to use the Media Creation Tool with current release of 1903 until they have fixed it.

Michael Niehaus Not fixing this maybe acceptable for the new machine scenario but for many people who rely on users having an easy way to rebuild from publicly available media (USB Stick) not fixing this for 2-3 months is really bad.

I think in this case Microsoft should provide the ability to select the build required when using MCT otherwise the service is useless because we cannot rely on getting a working build without providing users a USB Stick from VL download or a custom slipstreamed ISO which isnt really acceptable IMO.

Chris

Michael Niehaus, this will not work for most organisations. Ours included. When deploying a new machine, it is preferred to use a USB-stick to ensure its a clean setup.

Neil_a_Consultant, do not worry about duplicate devices in Windows Defender ATP. A new Windows installation will create a new machine, which makes sense. The old machine cannot be manually deleted from ATP but once your data retention period reaches its X days for that device, it will be automatically removed. Even manually off-boarding a machine will not help.

TToP89  I have discovered that if you can get the device updated, then do a Intune FreshStart - it seems to retain the needed KB.

Of course Windows Defender ATP now sees the device multiple times (because historically this is a different device).

I also worry because some devices in my environment show up multiple times in the Devices->Device Enrollment->Windows Enrollment->Devices blade (aka Dashboard->Device enrollment - Windows enrollment -> Windows Autopilot devices).

I believe the duplicates are because some devices were registered through MSfB back in the early days - and now those are the devices that are getting pushed to 1903.

Michael Niehaus  So how are admins supposed to deploy this 1903 image to machines enrolled in AutoPilot if this won't be updated until then?  Not able to roll back imaging sticks back to 1809 using MCT either....

Chris Snell The media will likely be updated in 2-3 months, including the latest update at the time.  OEMs will ship new devices with this fix preinstalled.

Michael NiehausJust wanted to confirm that the build available when you create a USB Stick from the Media Creation Tool is 18362.30

Please advise when 18362.145 will be available when using the MCT.

Thanks

Deleted 

My issue is intune autopilot can t install windows store application (entreprise portal)

when i update windows 10 with the preview all is working fine

Michael Niehaus 

Today 30/05 ive just built a1903 from the Media Creation Tool  https://www.microsoft.com/en-gb/software-download/windows10 and im getting the same failure during AutoPilot on the Account Setup Stage. I got into the OS and installed Company Portal from the MS Store and it moved on.

Please advise when the Media Creation Tool build will be updated. 

Thanks

The fix is in build 18362.145 (and later), delivered via KB4497935.  It’s been available since 5/24 for devices in the Insider rings (including “Release Preview”).  The update is available for download from the WU catalog:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4497935

Thanks,

-Michael