Problem solve Get help with specific problems with your technologies, process and projects.

Interesting Issues in Insider Preview 15042

Late last week MS released a new Windows 10 Insider Preview build. Little did I know that there would be “Interesting Issues in Insider Preview 15042.” But after a couple of failed installs,  I found myself  “bitten” on my Dell Venue Pro 11. That’s when I remembered that the release notes included this warning:

A small percentage of PCs may fail to update to this build due to a corrupt registry key. If your PC appears to be at the spinning dots black screen during boot for an unusual amount of time while updating to this build, hard reboot your PC and then run the following commands in an admin Command Prompt…

Those commands included deleting two  registry keys, and disabling locality state for IPv6 on affected machines. (See the release notes for all the details, please.)

It took three tries to get it installed, but eventually I got Build 15042 up and running.

Interesting Issues in Insider Preview 15042 Lead to Multiple Install Attempts

Ultimately, it would take me 3 tries to get the install to work properly. The first one failed at 77% of the way through the post-reboot phase of processing the upgrade. In the wake of the first failure, I used TenForums guru Kari’s UUPtoISO tutorial to build an ISO from the leftover files. (That’s a nice and unexpected benefit of such a failure, as it turns out.)

Then my second attempt using setup.exe from the mounted ISO file failed in the same part of the install process. That’s when I remembered the warning from the release notes. I’m pleased to say that after following its instructions, the third install try indeed proved to be the charm. I now have a working install of Build 15042 running on my Dell hybrid tablet.

The UUP-to-ISO conversion tool also reads MS-supplied values to construct the ISO file name. Here’s what it produced for this latest build:


This name appears to indicate we’re nearing final status for the beta version of Windows 10. I’m also guessing from the appearance of OEM in this filename that the build is either at or soon to hit OEM release status. That’s usually shared with OEMs 30 days or so before the final release goes public. Thus, the timing is right for an early-to-mid April release for the next Win10 version, as recent news and rumors from Microsoft have led many insiders to expect.