Clean install via UUPDUMP iso

Mooly · Jul 1, 2021

And it has just thrown the same error message out and stopped.

JAM83 · Jul 1, 2021

Mooly said:
That all looks good Jimbo. Exactly what I have been doing.
Trying again now and as before the initial few seconds of the run generate errors but it does go past that. It will be another 5 minutes or so before I know if it has worked or not.

When I see those initial errors I really wonder whether there is any point letting it carry on, I don't know if they are really relevant or not.

Hey bud. See my post #13 on this thread. That may still be the reason it's causing errors.

Bree · Jul 1, 2021

Ed Tittel said:
I just built an ISO based on the initial release "Insider Preview 10.0.22000.51 amd64" by selecting only Windows 10 Pro as my image target. Others are reporting issues with more complex or later sources...

I asked UUPDump to include two editions, Pro and Home. That had no problems building the ISO either.

Bree · Jul 1, 2021

jimbo45 said:
...just selected Windows pro when creating the iso via UUPDUMP and boot was OK. .... Setup on boot does allow you to use local account...

Yes, as it was with W10 , W11 Pro does retain that option, it's W11 Home that doesn't have it. Or rather, it doesn't show it as an option. To use a local account on Home you should set up while not connected and at the 'let's get you connected' screen press Alt+F4.

jimbo45 · Jul 1, 2021

Bree said:
I asked UUPDump to include two editions, Pro and Home. That had no problems building the ISO either.

Hi there
I think in some cases it's not actually building the ISO from UUPDUMPbut creating a bootable device that actually boots when you try and install from scratch.

I'm going to see what happens now the UUPDUMP servers have settled down a bit to select more editions and see if I can get a bootable version.

Believe me when people think they can get things almost foolprofingly workable I can usually break it. !!!

Perhaps some of these big corporations should pay me MEGABUCKS to test things for them. !!!

Cheers
jimbo

Bree · Jul 1, 2021

jimbo45 said:
I think in some cases it's not actually building the ISO from UUPDUMP but creating a bootable device that actually boots when you try and install from scratch.

I had that problem with my 22000.51 ISO, the install.wim was larger than 4GB so making a conventional Fat32 usb was not possible. My solution was to copy the contents of the ISO to a folder on a usb ntfs HDD, then boot to a command prompt from a bootable usb stick. At the command prompt just run the Setup.exe from the folder on the HDD.

Ghot · Jul 1, 2021

Select edition for Windows 11 Insider Preview 10.0.22000.51 (co_release) amd64, English (United States)

Without all the updates, the ISO is smaller. And will be 22000.1, rather than 22000.51

Mooly · Jul 1, 2021

JMedlock83 said:
Hey bud. See my post #13 on this thread. That may still be the reason it's causing errors.

Thanks, everything points to them having problems, however... I have got a W11 USA English to complete OK and so have created bootable media from that. Went and did the swap of boot files from a USA W10 build and hey presto, it upgraded without a hitch on my 9 year Dell Vostro laptop which is an early i5 processor, legacy boot and no TPM.

All good so far, just need to look at if/how I customise that start menu now as I had the W10 highly configured. AOMEI first while the goings good and that looks to have run OK.

grumpus · Jul 1, 2021

I used the uup dump link Windows 11 Insider Preview 10.0.22000.51 (co_release) amd64 to build a win10 pro iso yesterday, but the resulting iso was named 22000.1_PROFESSIONAL_X64_EN-US.iso and the build it installed was indeed 10.0.22000.1. Is that what y'all are seeing as well?

Ghot · Jul 1, 2021

grumpus said:
I used the uup dump link Windows 11 Insider Preview 10.0.22000.51 (co_release) amd64 to build a win10 pro iso yesterday, but the resulting iso was named 22000.1_PROFESSIONAL_X64_EN-US.iso and the build it installed was indeed 10.0.22000.1. Is that what y'all are seeing as well?

That's oif you choose the option without the updates included. When you check Windows Updates, and get the updates, it should then be 22000.51

grumpus · Jul 1, 2021

Ghot said:
That's oif you choose the option without the updates included. When you check Windows Updates, and get the updates, it should then be 22000.51 :)

A typo in the link name, maybe. The link for the version with the CU errors out every time, about half way through (running the linux script on Fedora 34). Anyway, you're right, no big deal, running WU installs kb5004564 bringing it up to the .51 build.

Ghot · Jul 1, 2021

grumpus said:
A typo in the link name, maybe. The link for the version with the CU errors out every time, about half way through (running the linux script on Fedora 34). Anyway, you're right, no big deal, running WU installs kb5004564 bringing it up to the .51 build.

Right now the UUP servers are seriously overloaded.
Back on June 28th I downloaded both the with and the without updates versions.

The with, came out to 5GB and version 22000.51
The without, came out to 3.4 GB and 22000.1

JAM83 · Jul 1, 2021

I still haven't received the new updated Microsoft Store. I'm also not logged in as an Insider either, but it still should show the update, correct?

kylprq · Jul 1, 2021

Bree said:
I asked UUPDump to include two editions, Pro and Home. That had no problems building the ISO either.

I can verify that if you only choose Home or Pro it's throws errors
so you have to include both Home and Pro versions

NavyLCDR · Jul 1, 2021

Bree said:
Yes, as it was with W10 , W11 Pro does retain that option, it's W11 Home that doesn't have it. Or rather, it doesn't show it as an option. To use a local account on Home you should set up while not connected and at the 'let's get you connected' screen press Alt+F4.

@Bree,

How did you discover the Alt + F4 trick?

grumpus · Jul 1, 2021

JMedlock83 said:
I still haven't received the new updated Microsoft Store. I'm also not logged in as an Insider either, but it still should show the update, correct?

I was not offered CU kb5004564, needed to get up to build 10.0.22000.51, until I enrolled my VM in the insider program. Even then, it was keeping it in the release preview channel, unable to install the CU, because it didn't like the hardware (no TPM or secure boot in Virtualbox). I had to apply a registry hack to get on the dev channel, at which point I could run WU and do the update.
Google "How to Enable Windows 11 Dev Channel on Unsupported Device" for info.

Bree · Jul 1, 2021

NavyLCDR said:
@Bree,

How did you discover the Alt + F4 trick?

It was @Megahertz that drew my attention to it here...

https://www.elevenforum.com/t/install-windows-11-home-using-local-account.23/post-2230

...I then confirmed that it worked here:

https://www.elevenforum.com/t/install-windows-11-home-using-local-account.23/post-2282

martyfelker · Jul 1, 2021

Installed perfectly from UUPDUMP ISO using VMware running on Manjaro Gnome 21.07 (21.1 will use Gnome 40). I am using my Eluktronics lMax-17 laptop with 64 GB of RAM. As they say, it screams. And Windows 11 is OK also. I'll see how far I can push it. Although I dual booting with Windows 11 on a 4 TB SSD I'm tempted to give the whole laptop over to Manjaro.
Update - Created same using virt-manager.

JAM83 · Jul 1, 2021

grumpus said:
I was not offered CU kb5004564, needed to get up to build 10.0.22000.51, until I enrolled my VM in the insider program. Even then, it was keeping it in the release preview channel, unable to install the CU, because it didn't like the hardware (no TPM or secure boot in Virtualbox). I had to apply a registry hack to get on the dev channel, at which point I could run WU and do the update.
Google "How to Enable Windows 11 Dev Channel on Unsupported Device" for info.

I have a supported device. I just think I probably need to enroll in the Insider Program

bobkn · Jul 2, 2021

Bree said:
I had that problem with my 22000.51 ISO, the install.wim was larger than 4GB so making a conventional Fat32 usb was not possible. My solution was to copy the contents of the ISO to a folder on a usb ntfs HDD, then boot to a command prompt from a bootable usb stick. At the command prompt just run the Setup.exe from the folder on the HDD.

That works. There is also a method using "dism" to split install.wim into files that don't break the FAT32 4GB limit. (Not something I do every day, or every month, but there are recipes for it online.)