Microsoft has acknowledged today a new issue preventing Windows Insiders running the build 18362.53 to update to the 20H1 build 18875. The Windows Insider team said that this migration failure has forced them to stop distributing the latest 20H1 build to Insiders on build 18362.53, who will soon receive a cumulative update to fix the migration issue.
— Windows Insider (@windowsinsider) April 16, 2019
As a reminder, the build 18362.53 was the latest cumulative update for the Windows 10 May 2019 Update, and it was released last week on Patch Tuesday. Windows Insiders on the Slow and Release Preview rings will continue to test the May 2019 update for the time being, while the Fast Ring has now merged with the Skip Ahead ring for testing 20H1 preview builds.
While Microsoft is working on this cumulative update for the build 18362.53, the company won’t release any new Windows 10 20H1 build until the fix is ready. “Our goal is for this to happen by the end of this week,” the said on the Windows Insider blog today.
You can read the full announcement below:
A huge thank you to all the Windows Insiders who reported and up-voted feedback on receiving 0xca00a000 and/or 0x80242016 errors when attempting to download and install Build 18875. Your feedback has been immensely helpful in the investigation of the issue. We have determined that there is an issue with the Build 18362.53 (KB4495666) Cumulative Update that was released early last week which has caused updates to Build 18875 to fail. The issue only impacts 19H1 to 20H1 updates and occurs due to a migration failure as the OS attempts to update to the new build. To resolve this issue, we are creating a new Cumulative Update that will need to be applied on top of Build 18362.53 first before Insiders will be able to update to the latest 20H1 builds. As we work on this new Cumulative Update, we have stopped offering Build 18875 to Insiders on Build 18362.53 and holding off flighting a new 20H1 build until we can deliver the fix to unblock Insiders. Our goal is for this to happen by the end of this week. We’ll share additional updates as available.
If you’ve been affected by this migration issue, you’ll just have to wait for the new cumulative update for build 18362.53 to be released, and we’ll let you know as soon as we get more information about it.