[German]Microsoft has stopped the distribution of Windows 10 Insider Preview Build 18362 (from the 19H1 development branch) in Slow Ring because of an installation issue. Addendum: A workaround to recover from this mess has been discovered.
Microsoft is heading to release Windows 10 Version 1903 soon (public release is expected in April 2019). Some blogs have already speculated over the weekend about release candidates. But it looks like it won't work so fast. At least the Insider Preview Build 18362 is causing a lot of trouble for some people.
History: Windows 10 Insider Preview Build 18362
Microsoft had released the Windows 10 Insider Preview Build 18362 from the 19H1 development branch on March 20, 2019 in the Fast Ring. I had blogged about this within the blog post Windows 10: Insider Preview 18362 (19H1) in Fast Ring. The build contained no new features. The announcement was made in the Windows Blog, where also the fixed and unfixed bugs in this build are listed. Then surprisingly two days later, Microsoft released that build on March 22, 2019 in the Slow Ring (and just on a Friday). I blogged about that within the article Windows 10: Insider Preview 18362 (19H1) in Slow Ring, but omitted my doubts whether it's wise.
Microsoft says: Some Insiders facing trouble …
Yesterday (03/26/2019) Microsoft let Insiders know, that there is an issue with Windows 10 Insider Preview Build 18362. In an addendum they wrote within the Windows Blog:
UPDATE 3/26: Over the last couple of weeks, Insiders in the Slow ring have been receiving new 19H1 builds in addition to also receiving Cumulative Updates. After flighting Build 18362 to the Slow ring on Friday, Insiders began reporting they were unable to complete the update. We have discovered an issue with the Build 18356.16 (KB4494123) Cumulative Update that was preventing the update to Build 18362 from completing successfully. This issue only impacts Insiders who are on Build 18356.16 who try to update to Build 18362. THANK YOU to Insiders who reported feedback on this in Feedback Hub and upvoted – your feedback was immensely valuable in helping investigate this issue over the weekend! The team is currently working on a fix now. In the meantime, Build 18362 will no longer be offered to Insiders who are on Build 18356.16, so Insider PCs don't continue to try and take Build 18362 and fail. We will post another update once we release the fix and resume the Build 18362 flight. Thank you!
In plain text, without the whistles and bells, they say: If you are on Windows Insider Preview Build 18356.16 in Slow Ring (that was the last build released to this ring, see Windows 10: Insider Preview 18356.16 (19H1) in Slow Ring), you have a problem. Clients running this build tried to pull the new insider build 18362 from the Microsoft servers after the release last Friday. The upgrade failed and was repeated and repeated again. There were more and more reports Friday from insiders that the upgrade to build 18362 would fail if the cumulative update KB4494123 (build 18356.16) was installed.
Microsoft is currently working on a solution. In the meantime, build 18362 is no longer available to insiders who are on build 18356.16 in Slow Ring. Microsoft wants to prevent insider PCs from trying to update to build 18362 endlessly and unsuccessfully. Microsoft intends to release another update as soon as a fix is available. Only then the test of build 18362 will be continued.
Additional details and workaround: Upgrade error 0x80242016
The installation of the new slow-ring build 18362 fails if the previous build was upgraded to 18356.16 with update KB449412. The installation aborts with error code 0x80242016 at 7 – 8 % progress, as Microsoft has added here.
Error 0x80242016 stands for WU_E_UH_POSTREBOOTUNEXPECTEDSTATE
'The state of the update after its post-reboot operation has completed is unexpected. – see Windows 10: Update errors 0x8024xxxx detailed.
Microsoft hasnow a published workaround in Feedback Hub: The service "Windows Search" must be stopped and disabled before build 18356.16 is upgraded to build 18362.1 (also, if setup.exe from an iso file is used for an inplace upgrade). After a successful installation of the 18362.1, the Windows Search service has the status "Automatic (delayed start)" again.
Cookies helps to fund this blog: Cookie settings