This is considered a normal occurrence. Just run the script again to complete the download of all updates. Don't worry about it.
I've tried man many times. _PreDownloadAllUpdates_x64 always end up with the same error. Running SD10_Renewed_1.8_Start.cmd With this options -> no debug \ Slim image \ iot ltsc \ personal tweaks \ Leads to this error
It probably is supported till end of 2032 (Source: learn.microsoft.com/en-us/lifecycle/products/windows-10-iot-enterprise-ltsc-2021). I am not sure if that is with Extended Security Updates or even without.
In my tests, I have had no problems with the suggested images in the SD10_Renewed_1.8\ISO folder. There is a txt file there with links to download the Client Business Volume and Client Consumer Retail 19045.1826_ESD images. There is nothing stopping you from downloading a more up-to-date version. The difference is that the more up-to-date versions will be larger at the end of the process because they contain more and more things added by Microsoft. Before doing anything with the script, please read the README.txt file that is inside the package. Many times the error occurs because the package was unpacked in a long path, which is not recommended. Unpack directly in a directory (X:\, C:\, D:\) using the "extract here" option, with 7-Zip or Winrar. The script will be able to identify the following ISO images: 1 - Windows_10_Enterprise_LTSC_2021 (all languages) 2 - Windows_10_IoT_Enterprise_LTSC_2021 (en-us) 3 - Windows_10_19045_BUSINESS (all languages) 4 - Windows_10_19045_CONSUMER (all languages)
When you consider all the fallout from the endless litany of user hostile 'features' that Microsoft keeps adding to Windows 11 -- that have absolutely nothing to do with the functioning, maintenance, or ease of use of an Operating System on any level, the litigation, embargos, Microsoft's heavily fudged Windows 11 adoption statistics that are repeatedly a case of exaggeration, and real world one step forward and two steps back to Windows 10, even in the 'Enterprise'... And now Microsoft is formalizing everything it's doing in one big rollout with Recall in a way not unlike what they did with the marketing and lawfare around Internet Explorer -- creating a straw man legal argument that can be defended (with more money and a legal team larger than the GDP and governments of most developing nations, because 'might makes right') that Recall like IE is 'integrated & essential core features of the OS'... When enough people become concerned about getting Tuttle/Buttled, or it actually happens and makes news, if the grotesque performance hit from Recall (it's like the idiotic GameBar on steroids) doesn't do it first; would anyone be shocked to see a five step move back to Windows 10, and updated long term support for every Windows 10 SKU? With all this going on, and Linux distros that are now quietly running Windows application and game binaries with better performance, in a much more secure and private environment that is open, free and the opposite of 'user hostile' -- it's hard to feature how Microsoft can hang on to at least the consumer segment of the OS market... But with enough money and a big enough hammer, more ridiculous things have prevailed on the world... Shame on you Microsoft -- I used to love your products, and they used to make me excited about the future... Now it's only a handful of people that keep your once great and now literally corrupt products working in a sound way (people that won't even take my money) that get my admiration...
I have recently switched to Linux (and am here to look for a slim windows 10 to run in an VM). And in my experience Linux Desktop is not ready yet for the John Doe to switch over. With windows (pre 11 maybe) there are less issues and problems, or at least one already knows how to handle them. I bet people are more likely to switch to an even more closed system, Mac, than to Linux.
No, this would not cause the error. I was updating the script and in the tests I saw that the error was caused by uupdump. Uupdump added a verification test for accessing the website and this prevents the script from accessing the links. Since this is only necessary for Microsoft-Windows-RegulatedPackages files, I decided to download them and include them in the package. This way there is no need to download them. I just tested with pt-br_windows_10_enterprise_ltsc_2021_x64_dvd_f318268e.iso and everything went well, without errors. I will do one more test with 19045.1826.220708-0121.22H2_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO and then I will publish the updated package.
===================== SD10_Renewed_1.9 ===================== Updated to version 1904x.5796 Several changes were made to the script: - Since the uupdump site created an access log, the download links for Microsoft-Windows-RegulatedPackages were no longer directly accessible. So they were removed from the download list and are now part of the package, without the need to download. - Now all appxpackages are not removed. When selecting to keep some appx, it will not be removed, without the need to update at the end. - Updated the hfixes_all.txt and hfixes_ltsc.txt files - Other small adjustments were made Since there were a lot of changes this time, if you encounter any errors, please report them so that we can fix them. Good luck! https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
I am still have this error. =========================================================== Downloading missing Windows 10 22H2/LTSC2021 Updates... =========================================================== Downloading: "microsoft-windows-client-languagepack-package_en-us-x64.esd" Done. WARNING "microsoft-windows-client-languagepack-package_en-us-x64.esd" ERROR Some files has NOT been downloaded correctly Please re-run the script to try again
@left12345 @Taranis01 Unfortunately, this problem is occurring because of the uupdump website, which requires identification to access it. Regarding Regulatepackages, it was resolved, as it is language-neutral. Regarding languagepacks, I think I will also download them to solve this, at least until we find another solution.
===================== SD10_Renewed_1.10 ===================== Updated to version 1904x.5796 Several changes were made to the script: - Since the uupdump website created an access log, the download links for Microsoft-Windows-RegulatedPackages are no longer directly accessible. Likewise, the links for Microsoft-Windows-Client-LanguagePack-Package are also no longer accessible. Therefore, the commands for downloading these resources were removed from the script, maintaining the following options: 1 - Microsoft-Windows-RegulatedPackages: They are now part of the package, without the need to download. 2 - Microsoft-Windows-Client-LanguagePack-Package: The languages de-de, en-us, es-es, fr-fr, it-it, pt-br and ru-ru were added to the package, x64 only. 2.1 - The LanguagePack_links_uupdump.txt file was created for manual download by the user, when necessary. Once downloaded, the file will remain in the hotfixes folder for future use.
Thank SunLion, for wonderful work. my SD10_Renewed_1.10 test completed successfully on VirtualBox, host Windows 10 22H2. no problems for me as I have run SunLion's tools awhile. however, newbie may have a problem, where to place iso file? in my test, I tried wherever, root folder, script folder, sub folder , , , when running, the script failed to locate the iso file. at final, I moved it to default folder, forced the script to run. then no issue. 1 run the script then run _CreateISO.cmd to generate the iso file. 2 performed install test on VirtualBVox. host Windows 10 22H2. Display Name: Windows 10 IoT Enterprise LTSC Build: 19044 Service Pack Build: 5796 apps available: Paint, Snipping.