10532 now fails to install, does win10 update process ever work?


Recommended Posts

ok I made a new iso with the media creation tool and did a proper clean install.

I ran a sfc scan within an hour of the install but this was after it forcefully downloaded loads of updates, it detected 2 corrupt files which were different to before and did fix them,

This time it successfully registered me as an insider and I configured the fast ring.  I am aware there is a delay before the new build will be offered so thats what I am waiting for now.

Before I did this clean install I did try the 10532 iso as an upgrade again but that failed in same spot as before.

still fails, same place, it would seem the only way I can keep latest build is to clean install the latest build (although that might fail), the upgrade process is flawed.

It's something you're doing wrong, all updates have installed fine on my cheap laptop, but I don't "tweak" or run "fixes" on my systems, this isn't XP anymore 

What have i tweaked?

Just because it works on your laptop it doesnt mean its a bug free process.

Its actually a very simple process thats hard for the end user to get wrong.

You install the OS.
You activate insidder testing
You install the inssider update

You talk as if its something that requires high skills.

Given there is 1000s of hits on google with the same issue its clear there is a bug of some sort.  Or are you going to say all these people including IT specialists and system admin's are "doing something wrong".

Also even if this was a "tweaked" system as you put it, the process needs to be able to handle that.
 

for the curious I managed to install 10532 cleanly using the ISO I made from the install files downloaded from windows update.

I was twice asked for a key which I selected "not now", it says evaluation copy in the bottom right corner which I hope is correct, it is activated.

So it seems in my case with my hardware, the upgrade process has an issue but not the clean install process.

All I can say is I am glad this hasnt touched any of my production machines, so yeah sorry to the fans some more bad news.

I enabled 3 features from programs and features.

HyperV
telnet client
.net framework 3.5/4.0

On 10240 this does work, but on 10532 after the reboot it progresses up to 100% completion but after 99% it says it cannot apply the changes and does another couple of reboots to undo them.

Now I am aware 10532 is not supposed to be clean installed, isnt supported by microsoft, whether or not that has anything to do this with this issue, no idea.  The clean install I guess is a proof of concept to see if my hardware can run 10532 at all, it can it seems.

I will try these one at a time to see if its a particular one that fails.

I do have a theory why the OS update from 10240 to 10532 may be failing, I am using a 128gig ssd which is formatted as 110gig to maintain free space for performance.  I wonder if it is running out of space during the upgrade process even tho it is supposed to check if enough space exists.  I will test this by going back to 10240, copying a large file to the ssd so is less space and will see if it fails earlier in the process instead.

Its HyperV thats broken, telnet and .net are fine, I suspect now since I had it enabled in 10240 that could be why the upgrade failed, so will be trying again without HyperV.

Edited by Chrysalis

It seems like something specific to your hardware, some piece it just doesn't like for whatever reason, Hyper-V looks for specific things from what I remember, but today most if not all CPUs sold support what it requires so that shouldn't be the issue.  Maybe it's the chipset or some other controller that's making it freak out when it tries to upgrade or something?  

If 10240 upgraded and ran everything fine and a clean install of 10532 is the only way it'd work for you then something was tweaked/changed under the hood and it's having a fit with your configuration, you have another test system to try out maybe?   All I can say for now is if 10532 is not good to go to wait for the next one, probably later this month if not sometime this coming week.   Then try again and see if it works.

Turn hyper-v off.. 10532 kept failing to install for myself until this was removed.

A google for 10532 not installing lead me to this solution as I wanted it installed to get Cortana Australia to work.

at the moment I still cannot see if upgrades without HyperV enabled as the upgrade still isnt been offered on this install after nearly 24 hours, sorry. (I want to do an online update rather than use the iso if possible).

Thanks for your feedback tho burnz, seems we may have got to the bottom of this based on your reply. :)

Chrysalis, have you tweaked or made changes in the registry with your previous builds, or are there some other issues with your machine that you've noticed before when running other OSes?  I've never had one single issue, and it seems like you are plagued with them.

 

is this the slow ring or fast ring?

looks good here now, its still updating but its past the copying files stage and now on the drivers and features.  It was done via windows update it showed up not long after the previous post.

Will spread the news about HyperV as is dozens of other sites with same problem reported.

--edit--

So is now on 10532 via official update.

Personal observations, is bad the driver update is changed from my preference of no drivers via windows update back to automatic, naughty microsoft, but the nvidia drivers were not overwritten.
Existing driver configuration was lost, e.g. I had to configure my NIC again to disable large send buffers, and redisable 2 hdd's I had disabled prior to update.
Task manager "forgot" its configuration, I had to reconfigure logical cpu's amd kernel usage display as well as enable the mroe details again. in addition "always on top" and the minimize option needed setting again.
All other changes I made seem intact.  Although wasnt many, the other changes were replacing defender with nod32, setting IE as default browser and pinning it to the taskbar, enabling powershell on context menu, enabling small icons on control panel, adjusted some startup settings in control panel and visual options, adjusted swap file size, and changing name of the network workgroup.

So two of us now confirming the HyperV bug,

Edited by Chrysalis
added post upgrade details
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.