Testing the recently released 1903 with two Autopilot tenants and with both they always fail at the user stage when trying to install apps. These apps are just normal store apps, Company Portal, Forticlient, Translator. If you skip waiting and install them manually, the setup completes, but it just won't install store apps by itself.

@Coert Kastelein this a known issue with the 1903 builds, I'm told the latest Insider Fast build (18881) has the fix. The bug was that all store app installs fail when using Intune or any MDM to install Microsoft Store for Business apps, they install like you said manually just fine. Try the 18881 version

@Coert Kastelein Thanks for your response yesterday. I went through the steps you advised on build 18362.30, but the only build update I am offered is 18875.1000. Even though I selected the Fast ring without Skip ahead.

@Darren Littlefield I tried the same and also not going beyond that version. I suppose MS engineers have even earlier access to these builds. Expecting it soon. Perhaps @Eric Orman can provide more info.

@Coert Kastelein Just one question, isn't 18885 (20H1) the next build of Windows? This wont be the May release build? As this was the 'skip ahead' version. I want to make sure our business will be inline with the release version and not a version ahead.

It's even not the next, bet next next build. Next feature update should be 19H2 scheduled for October 2019. 20H1 is for 2020 spring update. Yeah, this is puzzling that MS jumps this much ahead and there are still no news about 19H2 testing. Btw, in May you will receive 19H1, 18362.xx build. Which i guess won't have that Autopilot fix. Maybe they will release it as a CU fix for the current version, who knows. Maybe they will add it to 19H2 release. Just guessing.

I'm not really sure how these branches join eachother when it comes to bug fixes. They advertise 1903 to be the first release that can fully configure a device during Autopilot deployment, so I don't think the fix for this bug will be introduced after the release of 1903.

@Eric Orman Thanks for the update Eric. Will this be a new patched ISO available on MSDN, or will it be an update only? As we are using autopilot with OOBE it would be time consuming to have to log in, update and then refresh to then autopilot the way we want to. 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:

@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....

@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.

@Consult-a null, 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.

@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.

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.