Announcing Windows 10 Insider Preview Build 16226 for PC Insider

After six failed attempts to upgrade from build 16215 and getting the error “Some updates were cancelled. We’ll keep trying in case new updates become available”� and trying every conceivable solution then starting over Clean Installing the latest Windows Insider build 16193 released on the windows Insider site and again trying to update to 16226 I was finally successful on that third attempt.

After creating a Bootable USB and testing it I now have a Clean Install of build 16226 up and running.

After update just won't install (every restart brings back previous build xx215), reseted updates and start downloading again.

.BT folder is more than 15 GB! Most of it in NewOS folder.

AndreTen said:

After update just won't install (every restart brings back previous build xx215), reseted updates and start downloading again.

.BT folder is more than 15 GB! Most of it in NewOS folder.

Andre....after you clicked restart, did you get the "Configuring Updates", or did it just do like a normal restart and come back to the welcome signin screen. Kinda quick like.

f14tomcat said:

Andre....after you clicked restart, did you get the "Configuring Updates", or did it just do like a normal restart and come back to the welcome signin screen. Kinda quick like.

Just normal restart. Circuling dots before restart were there a bit longer ...

And again just restart without installing configuring. This time (after Windows update reset) it was a bit different - Windows was aware, that install went wrong. And started another install

I'll probably cancel this one and try to make in-place upgrade. (have the ISO now)

AndreTen said:

Just normal restart. Circuling dots before restart were there a bit longer ...

And again just restart without installing configuring. This time (after Windows update reset) it was a bit different - Windows was aware, that install went wrong. And started another install

I'll probably cancel this one and try to make in-place upgrade. (have the ISO now)

That's what I was getting at. I had the same issue on my second OS in dual boot. I did it thru the ISO, and it was fine. Can't prove it, but I think it has something to do with the recovery partition. When you're done, you'll probably see a new Recovery Partition at the end of the OS of 450-460 MB.

f14tomcat said:

That's what I was getting at. I had the same issue on my second OS in dual boot. I did it thru the ISO, and it was fine. Can't prove it, but I think it has something to do with the recovery partition. When you're done, you'll probably see a new Recovery Partition at the end of the OS of 450-460 MB.

One (of 2 GB) is already there. Could it be Macrium?

AndreTen said:

One (of 2 GB) is already there. Could it be Macrium?

Only if you put it there. Macrium puts a hook into the BCDdata to run from your "C:" drive. Did you put Kyhi on a 2GB? What I meant was an update sometimes will create a new recovery at the tail end of your OS partition if the existing one is too small. Doubt that 2GB has anything to do with it.

f14tomcat said:

Only if you put it there. Macrium puts a hook into the BCDdata to run from your "C:" drive. Did you put Kyhi on a 2GB? What I meant was an update sometimes will create a new recovery at the tail end of your OS partition if the existing one is too small. Doubt that 2GB has anything to do with it.

No, it's Windows recovery (empty thou).

I got bounf of errors on every update attempt. Error 3 is there like 20 times (credential problems) and error 10 - enhanced storage

Description AuthenticateSession
Param1 0x1
Param2 0x60000001c
Param3 0x900000006
Param4 0x0
CmdStatus 0x12