UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files  

DragonFireDon22 said:

One thing I noticed is, when you change EnableUUPScan to 0, it always changes it back to 1 on it's own.

Yes, the reg patch gets reset after every update, so it has to be reapplied.

If you are stuck at upgrading to 15046, then try to do this:

1. Download ActionListParser.zip
2. Uncompress the files to the root of your UUPtoISO folder
3. Run ActionListParser.cmd
4. Once completed Run UUPtoISO.cmd
5. You should have your ISO now.

Hope this helps!

Note: The XMLParser.exe is not signed so your Windows might nag, just let it execute. I wrote this tool for testing purposes and it works for me.

oh, ok. Just DL a copy of this tool just in case. You never know when MS decide to give us a different delivery method again. ;-)

DragonFireDon22 said:

Well, nobody is replying guess I am gonna be start doing what Kari said. I will do a Disk Clean-up then do a disable UUP.

Let me know immediately if I should not be doing that. I hope I am able to do it without any problems...

One fact often forgotten is that Ten Forums is a global site, members coming from all over the world. When you posted about your issue it was late night for you but for us in Western Europe it was just after 5 am, for members in UK & Ireland only 4 AM.

Quite a many of us do sleep and take a break from forums at night. Myself as an example, although I am an insomniac and for instance slept less than three hours last night, I had gone offline about half an hour before your first post and only see about your issue now.

That being said, the Disk Clean-up cleaning temporary installation files trick is the best method to get rid of unwanted build upgrade.

DonCuthbert said:

I have done the Registry edit before. Only one is needed and the other is created based on it. I believe if you simply set the SupportsUUP key to 1 or 0 the other key gets auto-set (or deleted) as a result.

You have to set both values to 0 to disable UUP / enable ESD. EnableUUPScan DWORD will then be removed at next restart. When going back to UUP, enabling it again you should manually re-create EnableUUPScan.

Kari

DonCuthbert said:

Here are some steps to show what my statement was based on:

Yes, that is what should happen, how it should work and I am sure how it works in 99% of cases. I've only seen EnableUUPScan not being automatically re-created once or twice.

When making these tutorials you have to get it as fail proof as possible. If there's even a remote change that a command or procedure which normally works without additional steps but occasionally requires an extra switch, command or step, my instructions will always be based on that rare occasion when extra steps are required. Especially if these extra steps can cause no harm.

Kari