The AchieVer Posted April 17, 2019 Share Posted April 17, 2019 Microsoft Finds Bug in Windows 10 Cumulative Update KB4495666 Microsoft says it discovered an issue in the latest cumulative update for Fast ring insiders, so the company decided to put the rollout of 20H1 preview builds for these users on hold. 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.Fix coming this weekAs a result, the software giant decided to pull the 20H1 update for Fast ring insiders until a new cumulative update is released to resolve the bug. “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,” Microsoft explains. “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.” The new cumulative update is expected this week, which means that Fast ring insiders should be able to update to Windows 10 20H1 preview builds in just a couple of days. Windows 10 20H1 is a preview of the next spring update, and Microsoft previously shipped these builds to the Skip Ahead ring exclusively. Last week, however, Microsoft merged the Skip Ahead and Fast rings to provide both with 20H1 builds. Source Link to comment Share on other sites More sharing options...
The AchieVer Posted April 17, 2019 Author Share Posted April 17, 2019 Windows 10: Buggy patch stalls testing of 20H1 preview Microsoft puts the brakes on Windows 10 20H1 testing as it works on a fix for a flawed update. Microsoft is fixing an error in last Tuesday's security update that prevented testers from installing a preview of a Windows 10 feature update expected in early 2020. Last week Microsoft pushed its first 20H1 build to testers in the Windows Insider program's Fast Ring, but the release of Build 18875 failed for some testers, who were unable to install the update and saw various errors messages. Windows Insider boss Dona Sarkar has now confirmed that last Tuesday's security update KB4495666 preview build 18362.53was 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 core issue is a "migration failure" that happens as Windows 10 tries to update to the new build. 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. For now, Microsoft has stopped offering Build 18875 to Insiders on Build 18362.53 and has stalled the release of new 20H1 builds until it unblocks the release for testers. Microsoft last week merged Skip Ahead and Fast Ring testers so that now both groups will be testing 20H1 builds, rather than 19H2 as was expected. Microsoft plans to release 19H2 bits to insiders this spring. Meanwhile, it's moved the Windows 10 May 2019 Update over to the Release Preview test ring for a final round of testing before releasing it to the general public. It's possible Windows 10 19H2 will be a minor update. The 19H2 release will have 30 months support for Enterprise and Education releases versus 18 months for the H1 releases. The change in pace could help convince enterprises running Windows 7 to upgrade to Windows 10 before the end of Windows 7 support on January 14, 2020. Source Link to comment Share on other sites More sharing options...
Microsoft is fixing an error in last Tuesday's security update that prevented testers from installing a preview of a Windows 10 feature update expected in early 2020. Last week Microsoft pushed its first 20H1 build to testers in the Windows Insider program's Fast Ring, but the release of Build 18875 failed for some testers, who were unable to install the update and saw various errors messages. Windows Insider boss Dona Sarkar has now confirmed that last Tuesday's security update KB4495666 preview build 18362.53was 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 core issue is a "migration failure" that happens as Windows 10 tries to update to the new build. 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. For now, Microsoft has stopped offering Build 18875 to Insiders on Build 18362.53 and has stalled the release of new 20H1 builds until it unblocks the release for testers. Microsoft last week merged Skip Ahead and Fast Ring testers so that now both groups will be testing 20H1 builds, rather than 19H2 as was expected. Microsoft plans to release 19H2 bits to insiders this spring. Meanwhile, it's moved the Windows 10 May 2019 Update over to the Release Preview test ring for a final round of testing before releasing it to the general public. It's possible Windows 10 19H2 will be a minor update. The 19H2 release will have 30 months support for Enterprise and Education releases versus 18 months for the H1 releases. The change in pace could help convince enterprises running Windows 7 to upgrade to Windows 10 before the end of Windows 7 support on January 14, 2020. Source
Recommended Posts
Archived
This topic is now archived and is closed to further replies.