Last week Microsoft pushed its first 20H1 build to testers in the Windows Insider program’s Fast Ring. Microsoft hoped that the introduction of revamped Windows 10 Update feature would improve the lives of many users, but a series of buggy updates plagued the OS, and it appears that a new one managed to elude the quality control tests used by the Redmond company.
According to Microsoft, users running Windows 10 build 18362.53 after installing cumulative update KB4495666 can’t move to the Windows 10 20H1 preview builds due to errors 0xca00a000 and 0x80242016.
The issue appears to be caused by this particular cumulative update, and Microsoft says it is related to the migration process when switching from 19H1 preview builds to 20H1. 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 boss Dona Sarkar has now confirmed that last Tuesday’s security update KB4495666 preview build 18362.53 was the source of the problem.
“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,” noted Sarkar.
The company is now working on a new cumulative update that will be applied on top of Build 18362.53, which needs to be installed before Insider testers can update to the last builds from the 20H1 branch.
“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.”
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.