Windows 10: Create Windows 10 ISO image from Existing Installation

Hi,

LOL.

Basically it's about bringing an OEM Recovery DVD containing W10 V10.10240 and all its modifications to the setup routine to ensure OOB experience does not require end user interference up to current W10 V10.1607 by editing the image in such a way that OOB experience remains as perfect as it was using V10.10240.


To that end I need to understand a) what exactly the modifications achieved, b) what is no longer needed and c) what is still needed and what needs to be done for this to be achieved.

This is because the hardware was and still is to this date more advanced than what is contained in any currently available standard Win10 installation distro.
Since this an OEM recovery DVD I also want to make sure all the OEM stuff is up to date.

Why?

Because:
a) I want my Recovery DVD to install W10V10.1607 instead of 10.10240 straight away in case I need it.
b) Whenever I decide to sell off this machine I'd like it to offer the most current version of W10 and its drivers to my buyer.

Including the raft of language support the original DVD offers and no standard Win 10 version offers straight out of the box so to speak.

So far I achieved a working OEM 10.1607 OEM dvd image but that version too has its problems that need ironing out.
Therefore I'd like to work further on this little project until it becomes as perfect as the original OEM edition was.

Hope this clarifies it a bit, *Wink

Frank.

 

Interesting. WinX tries to make good on updating the drivers for my computer, but I end up using Snappy Driver Install to fix all of the little things. It works a lot better than anything else that I have seen. The drivers that I can easily update myself (video card, HD audio, etc.) I do, but some of the mor obscure drivers I am not able to easily update and that is where SDI comes in (such as the dreaded Marvell 9123 SATA contrller which gives me my SATA III connections).

 

I've installed 14965 in Hyper-V. It won't set up Fast or Slow ring. Says not connected to Internet. I am connected to the Internet so I'm guessing a problem with the servers.

Time for IV Caffeine.

 

I always install using a local account, then when on desktop after installation switch to Microsoft account. That way I get my user profile folder named as I want to instead of five letter abbreviation*from my Microsoft account email.

What you describe happens often to me in Hyper-V if I forget to switch to Microsoft account before trying to opt in and select ring. A fix is to restart, switch Windows user account to Microsoft account, restart again and now the Insider settings should work.

On rare occasions I've had to make a new local admin account, sign in to it, switch to Microsoft account and use it to get Insider builds. And, of course, if everything else fails then reinstall and switch to Microsoft account before going to Insider settings.

When done, when Insider ring has been selected, simply switch back to local account if preferred.

 

OK. I'm logged in with MS Account. I'll wait a while longer and see what happens. I seem to recall I had a similar problem when I installed a Build direct to my PC. It solved it self after a bit.

I think I've got a better grasp of the Tutorial now.

 

Got that once again earlier tonight when testing clean install with new ISO made according to Part One of this tutorial and then trying to get Insider builds started.

You can clearly see that Internet connection is OK:

 

I got the same thing earlier today as well. Created one VM, and then went to change IP settings and it just sat there spinning. Meanwhile, created a second VM and then went to chagne IP settings in it and it was instantaneous. Went back to first VM, and rebooted and change was instantaneous there, too.

Both VMs ggot 14986 immedaitely as well.

 

On fast ring now

 

Me too *Smile

 

Trying it right now...





Edit:
It took exactly 10 mins to 100%..

 

If the E: volume labelled Insider is that contains the Windows installation you want to capture, you should be OK *Smile

Just out of interested, which ISO are you doing (standard, one with accounts & pre-installed software or one with pre-installed software only)?

With my ailing historic hardware, I am so jealous for you guys with modern rigs...

 

@Kari , I am doing the one with pre-installed programs with account.

I ran into a problem which I was able to fix (because I know what to do) but some may find it difficult to sort out.

After 100% completion of saving the image (install.wim), I restarted back to my Insider installation, and this:





So I ran the Macrium WinPE and fixed the boot issue and it's ok now.

But when I boot up on my daily 1607 OS, I lost access to my Data drive which contains 2 partitions for Data and Games.









I had to manually add "authenticated users" to get access back to both partitions:





Now everything is back to normal but I haven't finished the ISO creation yet.

You may want to verify if this is an issue with one computer running 2 versions of Windows 10.

I will have to continue later finishing up the ISO.. *Smile

 

Hi,

Oh yeah, that's really confusing to Windows (not just W10) when running two Win installsl inside the same box.
I avoid that as much as possible but when messed up I install and run Sysinternals subinacl.msi to rese the default authentication permissions.

Removing the assigned drive letter to the one not in use often helps as well.

Cheers, *Wink

 

Thanks for your input.

I don't normally have issues with 2 OSes running on my main machine (one is GPT and the other is MBR disk). I don't get boot issues even after updates/upgrades. the problem only came up when trying this ISO creation but no big deal for me. I've seen worse.
And I do keep images so it's really easy to go back if worse comes to worse.
Just sharing what I've been through while trying this method.

 

Hi,

My pleasure. *Smile

That part I don't understand. How could that happen. Strange.

Cheers, *Wink