Yesterday I ran the in-place update from Windows 8.1 to Windows 10 build 9926.  Everything went smoothly.  Job done. 

Build 10041 is out and people have had some issues upgrading - rollback or erroring. 

I decided it would be fun to run a live blog. Updating along the way. Isn't it about time we saw a blog with the errors highlighted? Well here it is.

I'm going to run an in-place upgrade from ConfigMgr 2012. At this stage I don't even know if this is possible. Let's find out.

Follow me on Twitter for tweet updates or just refresh the page to see success/failure. 

Here we go

The Windows 10 build 10041 offline ISO is available from Microsoft. Grab it from here.

Copy the install.wim from the sources folder to your ConfigMgr install content location.

and there's my first error. I need the whole CD contents for this and not the wim file. So start again copy the ISO contents to the ConfigMgr content location.

My in-place upgrade will follow the process standard Windows 10 in-place upgrade Task Sequence as detailed here and here

So I need to edit my Windows vNext Upgrade Media's source content location to my new 10041 source location.

Now it's time to update the DP's for the new content.

DP's updating nicely.

Now the content is there.

Time to create my deployment collection. I've added in my device with a direct rule.

and I've deployed my Task Sequence to the collection and made it 'Available'.

Ok - since the Windows vNext Upgrade package was executed yesterday as part of my upgrade from 8.1 to 10, Software Center reports that the package is already installed. However I do have the option to 'Reinstall'. Let's see if this button will weave it's magic.

What happens when I press the button? Well that's expected so a good start.

Off it goes.... Time to switch device. I'm typing this on the Win 10 machine!!

Time to grab a brew. Will I return to an error?

....still going

Well surprise, surprise. We have a Task Sequence failure. 

Time to check the smsts.log. Not sure this is a supported method to upgrade so I'll take a look and see what error has occurred.


My error states:

Failed to run the action: Upgrade Windows.
Unknown error (Error: C1900204; Source: Unknown)

A quick check on the net and I am direct to the MS Technet blog mentioned earlier.

Aaron from MS states: 'check setupact.log under $Windows.~BT, I think this is SKU mismatch. Make sure architecture, language & edition match. '

I'm pretty sure that this was the same version. Let me take a break and investigate. 

What now?

Luckily I kept a copy of the original install ISO for build 9926 on the ConfigMgr server. Taking a look..well, well, it is the EN-US version after all!

I've just grabbed the United States download from the Microsoft download site and I'll follow my steps above to get me back to a state where I am ready for install.

Back in about an hour....

After updating to EN-US release I re-ran the TS and got the same error. Hmm maybe this isn't possible.

Going to park the live blog for now as I've run out of time for now. I'll pick this up tomorrow and try again.

So this does work

It seems that my second ISO still wasn't the correct release. Twitter friend and ConfigMgr blogger Mike Marable picked up the gauntlet last night after taking interest in the live blog. 

He's run the complete install through and an in-place upgrade of Window 10 to Window 10 is possible via the ConfigMgr Task Sequence. That means I'm off to get the correct release and will pick up the live blog later....hopefully today.

Thanks to Mike for taking time out and also for checking the live blog. 

More soon...

...and we have the correct media

To be able to do this I have to match the new Windows 10 release to my previous version. Therefore I have the TAP release on hand to match.

I'm going from:




I've uploaded the source files and DP's as above and retried the install. 

Currently on the Upgrade Windows screen.

Great stuff. Windows is now restarting. We have progress

Now we have the promise of a potentially successful upgrade. Percentage wise we are moving up but still the magical 100% needs to be reached. As they used to say on Stingray 'Anything can happen in the next half hour'.......or more.

Almost there... (apologies for quality of picture)

And we've made it to the other side. Windows 10 build 9926 to 10041 in-place upgrade via ConfigMgr 2012 Task Sequence is a success!

One thing to note. Office has re-configured on first use of Outlook. All fine though.

Lessons learnt along the way

  • To be able to perform the update you need to have exactly the same version to be able to do this. If running from TAP grab the TAP release, if from the Insider program then download from there. Make sure you have the correct region and architecture.
  • Don't use the install.wim file for this. You need the full source files for your upgrade as setup.exe is executed in the Task Sequence. I knew this but made the mistake of copying over the WIM. I'm usually working like a robot pushing out a WIM for an OS install. Not the case for in-place upgrade.

What's next?

Tomorrow I'll set the machine to use the Fast ring and update to 10049 release. Then I can check out the new Spartan browser experience. 

Live blog? Maybe.

Please do feedback if you enjoyed the live blog. I thought it would be a bit of fun to do. If you felt the same and would like to see another edge of the seat ConfigMgr/Windows 10 experience then post a comment and let me know.

Mike Marable contacted me throughout the live blog and, as mentioned, tested this process out over the pond whilst I slept. He went from Win 8.1 - Win 10 9926 - Win 10 10041 and has blogged the experience here. Well worth a read.