Windows 10: Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile

The update is proceeding with my Hyper-V VM of 16226. I already moved UUPtoISOsetup.exe to my Onedrive and if I can create the ISO on Hyper-V I'll move or copy it to OneDrive. It then will be available to the physical installation of Windows 10. Heck I can't even stop Insider Editions on the physical drive. I'll try Disk Cleanup.

 

Stopped updates but then still got the retry message. So I tried to re-enable them. I then get the absurdity below.

Updates have been resumed so we are checking for updates to keep your machine current with the latest security and quality updates before you can pause updates again.

Thus I will never get this update unless it is trhough an ISO.

 

Restart was done while I was sleeping. Start PC in the morning and it says Hi!

Doing ISO from Windows.old. All looking well for now

 

As I noted in Post #65 the update to Build 16232 GSOD(ed) at 33%, blaming ha20x2k.sys. I have since searched for that file and found 2 instances in the Temp folder referring to wdm. They were smaller that the other 4 instances on my system drive. I renamed those 2 files.
(I had used the "Browse my computer ... " function from Device Manager yesterday because I was having a distortion problem with my sound system. That installed the WDM drivers. But, that change introduced a nice loud 50 cycle hum! I uninstalled the WDM drivers, rebooted, re-installed the latest driver package from Creative. Rebooted again, still had a 50 cycle hum. Shut down and went to bed.)
When I booted the system this morning the hum had disappeared. But when I attempted to update to 16232, I had the GSOD previously noted.
I finished what I was working on and decided I'd try to update again, without clearing the downloaded files or resetting WU or disabling any of the security programs. And .............. Success *Smile
This update left Firefox as my default browser *Smile, but disabled System Protection. So win some, lose some.

 

Once I have installed upgrade in hyper-v, I simply copy the vhd to my SSD and attach vhd as a drive, and use "bcdboot x:\windows" where X is drive letter when vhd is attached.

This creates a dual boot option for the Insider version. First time you access it, it sets up drivers but nothing else changes.

Far quicker than reinstalling from scratch if you want to dual boot.

 

suggest a 3rd party AV to use with this build.
Seems they fiddle with the system creating glitches, dunno, but tried kaspersky and eset so far.

Every build upgrade i install has 166 3rd party programs and features installed, so it's quite remarkable it works after all these updates...*Confused

 

Wynona, I have noticed the same. There's an easy fix, it has worked every time at least for me: open Defender and get definition update using it. When done and you go back to Settings, you'll notice that it's now checking updates again and when it only finds build upgrade, it starts initialize and download it without issues.

Although not understanding why you tried making ISO before WU was ready, especially when you told earlier that you have already made the ISO, this is a good example about what I meant with my earlier post: not waiting WU to be ready, starting ISO making when WU is still initializing / installing upgrade is really foolish and not recommended.

 

Five and a half hours to the first restart. This is beyond a joke.*Sad

 

Nothing I am doing will help, I am still not getting 16232. Only one VM running US English PRO found it about half an hour ago (10 hours after release), all other editions and language versions simply stating "Your device is up to date".

 

It's strange how some people get delayed like that. I've always got it the first time I've looked.

 

I've usually got upgrade, every edition and language, as soon as it has been released. Now only that US English PRO is coming through although it's still only "preparing" after three quarters of an hour, all other editions in UK English, Finnish, Swedish and German show "up to date".

 

You would have thought you would at least get the German version in Germany.*Confused

 

Four and 3/4 hours from start to desktop. Most of the time taken at the 77% installing stage.

 

77% to 97% took forever.