Why go through the rigmarole of downloading anything from UUPDUMP (and using a script) when you can download a complete ISO directly from MSFT as was originally requested? Do whatever you want. Knock yourself out.
Current directory contains spaces in its path. Please move or rename the directory to one not containing spaces. Press any key to continue . that is what i am getting...
Read the post i replied to and then read my reply again. I never recommended to use any download option but mdl052020 keeps advising to use that uup file list instead of the uup dump download+conversion.
I just responded to what appeared to be a vague isolated request for a link to download an ISO. That's all I did. I guess that was a mistake, because I should have looked into other related posts. I haven't been spending as much time in the thread as I used to. Carry-on with your tech support as usual.
With UUPDump you can Download an ISO for each new Insider Build. With Microsoft, you have to wait till they decide to release an ISO
With the MSFT ISO, you have a bonefide MSFT ISO, that you can download without a script, that is fully functional, right off the MSFT server, that you can install immediately after the download. You don't have to wait for a script to assemble a mess of ESD, and Cab files. The size of the ISO is ALWAYS the same. You can verify the hash code against an MSFT published hash code. After the install of the ISO, Windows Update will update Windows 10 to the latest version and build, immediately. Plus Windows Update will automatically send you driver updates. You don't have to wait for MSFT to do anything. Hell, you could install 19041.1 and still update to the latest version of Windows. It is a waste of time for me to use UUPDUMP.NET for anything other than to download and manually install Windows updates, if I want to. That's all I use UUPDUMP.NET for. If you want to keep wasting time with every little update to Windows 10, then feel free to to use UUPDUMP.NET to build a new unneeded ISO every time there's a new LCU. I'm not impressed with the perceived magic of UUPDUMP.NET.
For those that want to do a clean install, With UUPDUMP you can do it with ISO. With Microsoft, you wait till they decide to release an ISO to do clean install.
That doesn't make sense to me. A clean install is when you put Windows 10 on a bare metal machine or newly partitioned and formatted HD or SSD. The version and build of Windows 10 is not extremely important. For example, you could get an UUPDUMP script, download all the files, and build the 19044.1415 ISO and then clean-install it. OR You could clean-install an older bonefide MSFT ISO, and then let Windows Update modify Windows 10 to 19044.1415. The destination is the same (19044.1415), the journey is different. With UUP, you must get the script, then run the script, get the ISO files, build the ISO and then clean-install it. With an older MSFT ISO, you don't have to do all that up front. You just install the ISO, and let Windows Update modify your clean-install to the latest version, whatever that is at the time. You'll still get the latest version of Windows 10.
That's such an ignorant thing to say. Being able to download specific builds with specific editions is so much value, specially when it comes to insider builds that microsoft rarely if ever gives an iso upfront (plus frequently failing install via WU, the only choice being offline integration). The mess you talk about is exactly, precisely, identically what microsoft themselves do (slower) via Windows Update. All those cabs and esd's don't come from someone's arse - but from microsoft windows update servers. And Windows Update blows! At everything. Speed. Efficiency. Reliability. It's far more greener to download the uup files / esd once vs a full bloated iso twice the size then letting WU get updates and - golem forbids - fail and go on a retard loop deleting perfectly good files and redownloading them.. 5-7 times. Even when you add local script processing costs into the equation WU just blows. As for waiting.. simple uup/esd to iso without updates integration is a mere 3 minutes on a modest pc. With integrating updates, it increases exponentially (30-60m), but it saves a lot more time when actually installing from the media. It's good, green, peace of mind practice to have a "base" iso for clean installs and repairs i.e. the latest esd build that incorporates the "must-have" fixes (data-loss etc). Then just let WU update. I do so myself. It's fine for most. It's not fine for potatoes, for limited bandwidth, for certain regions where ms does not care to give proper servers and after clean install it takes literally days to get "up to date". WU is also historically not fine for tweakers messing with the image to slim it down / add their s**t / etc. People don't really need a reason to crave for the "latest" iso. Might use it, might not. Better to have it if needed. OCD or whatever. It does not matter. uupdump project just satisfies a need others have, it is not affecting you in any way Stop being such a sour pussy and start using scripts, tweaks etc. and make windows to your liking. Because what comes out of microsoft won't ever be a stable, consumer-oriented, finished product.
Bau, please ensure that your brain is engaged before you resort to all that name calling (i.e. potatoes, sour pussy, etc.). Feel free to disagree with my opinion(s), but please make an effort to be civil about it. Using UUPDUMP to create a new ISO, every-time there's a release of a new LCU, is trivial "for me!", is a waste of time, a waste of bandwidth, and a needless drain on MSFT servers. There's nothing green, peaceful, or secure about any of that. There's no peace of mind in building ISOs that are a different size every-time, and that can't even be verified by a consistent hash code. If Windows Update (WU) was as unreliable as you say it is, MSFT would have abandoned it years ago, when I was still working for them as a contractor. The kind of scripting you refer to, is a waste of time for me. I do agree with you about one thing: There's no such thing as Windows "final". Every month it's the same thing, another patch Tuesday.
How is it a waste of Bandwidth ? It takes me less than 2 Min to Download a 5GB UUP Folder. Just to let you know, I am on the Dev_Channel, Beta_Channel & Release_Preview_Channel. so I have a choice between WU or UUP ISO. Do both Win 10 & Win 11.
Get the fury blood clogs out of your eyes read again and don't mix and match. I was quite civil, the sour pussy was just friendly banter. How in the world you reached the conclusion I called you a potato? That's something a less powered PC is conventionally called, not a person, wtf! How quick one runs to the offended card, while just minutes before s**t on a whole project because "not useful to me", "but the poor microsoft servers strain".. (already explained that via WU it invariably wasting more resources). How about you let others waste their time and just not comment like a microsoft drone? And if you do comment, do it on your personal blog if you cannot stand a matched response.
After offline servicing my usual 19041.1 base with the current updates in the updates preview via W10UI, the new iso does not work properly in uefi mode. When I put it on a bootable usb(ventoy), the iso boots up fine, but after language selection it automatically goes into the browse for the missing driver prompt. Could it be something like that setup.exe version mismatch since the DU is still from november?
I recently lost my base W10 Pro only 19041.1 x64 [EN-GB] ISO. Now in UUPD, when I searched for that (v19041.1 ISO), its gone & the lowest ISO available for the 2xxx branch is 19041.113 Currently, I have 19043.1415 UUPD ISO, if I delete the -Windows10.0-KB5008212-x64_eeb176e1: LCU [19041.1415.1.6] & -Windows10.0-KB5000736-x64_2468f082: 21H1 EP [10.0.1.3] -SSU (Not sure about this, should I delete the latest ssu-19041.1371-x64_bdab6b00 (KB5007273) and /or replace with any other dated SSU?) Then after conversion, will I get the 19041.1 ISO? P.S: If anyone has the W10 Pro 19041.1 x64 EN-GB ISO, then requesting to UL it in 1flicher/onedrive/mediafire.