Windows 10: Create Windows 10 ISO image from Existing Installation

None of the methods (Part One, Two or Three) in this tutorial transfer the activation status in any version or edition of Windows. ISO itself is just as any Windows install media containing / including no license.

Activation, regardless if using Windows install media like ISO images created per this tutorial or any other valid install media to install Windows is always based on either a product key, volume activation or digital license (Windows 10 only).

Whatever install media you use, you have to use a valid activation method. In case of Windows 10, if the computer you use ISO created as per this tutorial has a valid digital license for the same edition it will be automatically activated.

In case of Windows 7, 8 and 8.1 you need to activate with a valid product key, whatever install media you use. The methods told in this tutorial have nothing whatsoever to do with activation, they do not help in preserving or transferring an activation.

The ISO images created as per Part Two or Part Three in this tutorial are just normal install media; customised, yes, yet nothing more than Windows install media.

 

Having strange issue with 14986 ISO per Part One, a standard ISO. Windows does not let me run Sysprep (step 1.10). Luckily the log files are quite clear although long, I am inspecting the issue, not going to bed before it's resolved *Smile

 

OK, found culprit, easy to fix.

Will test this first thoroughly, only post solution when absolutely sure it works.

 

Guys don't use methods in Parts One and Three in build 14986 before we've found a solution for an annoying issue: the HoloLens app is misbehaving, causing sysprep to fail when /generalize switch is used. Generalizing works in every other build of Windows 10.

I am sure a solution exists, it just needs to be found. I've been on it almost a full day and night, it's now 6:13 AM and I have to take a break. In the mean time methods in Parts One and Three can be used in every version and build of Windows from Windows 7 to Windows 10 build 14971.

Method in Part Two works perfectly even in build 14986.

 

Thanks for the update.

 

Hi,
@Kari:

Just a minor detail:

Assuming you wanted to link to the tut that shows how to label partitions, I noticed the hyperlink is missing.

Also:

 

Missing tutorial link added.

Typo fixed.

Thanks Frank *Smile

 

OK, still searching for solution for this irritating, annoying Sysprep issue in build 14986.

Methods in parts One and Three work perfectly, fail proof in every version of Windows from 7 to 10 build 14971. They do not work making a Windows 10 Build 14986 ISO!

Ironically, because of the new upgrade system and missing ESD file the first version / build we would really need methods in parts One and Three is build 14986, but this build adds a new app (Holographic Viewer) which makes Sysprep with /generalize switch to fail. Sysprepping without /generalize switch works just perfectly, but as the switch is needed to make a standard ISO, methods in parts One and Three are useless in and only in the build they would really be needed for the first time!

When running Sysprep command with /generalize switch on any other Windows version and edition since Windows 7 RTM, it works. When doing in W10 build 14986, you'll get this error message:



Checking the logs you'll find several errors, all caused by this:
Code: 2016-12-15 14:07:04, Error SYSPRP Package HolographicViewer_1.0.0.0_neutral__cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.[/quote] I know how to reprovision app packages, how to remove them and so on. I know Sysprep, my first Sysprep related tutorial on our sister site Seven Forums is over 6 years old and all together my Sysprep related tuts on Seven Forums, Eight Forums and here on Ten Forums have had over 5 million views, with thousands of replies from mostly satisfied users.

Yet, now I am desperately staring a PowerShell window, trying to find correct commands to work around this stupid issue. The new app added to 14986 seems to be impossible to remove or reprovision. See what I mean, in screenshot I am first searching it to get full appx package name, then trying to remove it:



It's a no go, error message (red in screenshot) saying this:

I've tried all valid & supported as well as all not so kosher ways I know to work around this. Have found nothing yet.



Note Creating a customized ISO per method in Part Two works exactly as told in tutorial.

Methods in parts One and Three work at the moment only when doing an ISO image of Windows 7, 8, 8.1 or Windows 10 all builds up to 14971. Do not try these methods with Windows 10 build 14986.

I am working on it!

 

What happens if you remove it prior to starting this process?

 

My understanding is that once Kari found out what the hangup was, he tried to remove the holographic thingy.

 

There's no way to prevent it. Build 14986 adds this app, and as soon as it's added generalizing will become impossible.

This is of course so serious bug that Microsoft simply has to fix it but at the moment it will not work. I have still several ideas to test for a workaround but as each of them includes an in-place upgrade from earlier build to 14986 which I must perform to be able to test, it takes time.

Correct.

 

The irony in this is that the app causing this issue is an app most of us will never need nor be able to use!

 

Indeed. Wonder what else Creator's Update will break before they finally fix it....

 

After several re-installs today I finally got 14986 immediately I logged in to Windows Insider. Whoop!

I'm going to try Option 2 tomorrow.

No new Builds till 2017. 14986 ISO to Slow*Ring next week.

 

Ok, I seem to have made a successful ISO. Installing now.