Because LTSB will never be upgraded by WU there won't be an ESD available. ISO: https://forums.mydigitallife.net/th...refresh-pc-mobile.70297/page-200#post-1305920
I saw this post, but it does not have the pt-BR (Portuguese Brasilian) there, just EN and en-gb? I would like pt_windows_10_enterprise_2016_ltsb_x64_dvd Can you help me?
Yes it was a known issue on 15063 till (iirc) 15063.332. After the update back then it was solved. It has nothing to do with ESD.
hmm off topic but I don't resist Sir maybe mean installed system instead only kidding sorry my friend myself make this millions of times
Hello my friend, Being honest I do not know how to use svf to do this, could you give me a light on using it? Thanks in advanced, Marcelo "Sushi"
Go to @GezoeSloog's profile page and download the svfx tool, download the en-US source iso and the desired svf patch.
uup-converter-wimlib-13 - Support for pointing convert-UUP.cmd to UUP directory path from command line e.g. Code: convert-UUP.cmd C:\uupdl\uup\16288.1\AiO\en-us\amd64 - Support for ARM64 architecture - New manual options (see ReadMe.txt for details) SkipISO: do not create iso file (setup media folder will be preserved) SkipWinRE: do not add winre.wim to install.wim - Companion script multi_arch_iso.cmd to create Multi-Architecture ISO (x86/x64) mainly to combine two x64/x86 UUP distributions into one ISO you can also use it on any two x64/x86 ISOs (starting windows 8) see ReadMe.txt for more info
Thanks for the separate ISOx86/ISOx64>multi-architecture ISO script ps, it only works at the multi-architecture iso part when the iso contains install.wim, not install.esd: Spoiler: Error ISOx86/ISOx64 (2 x Install.esd)>Multi-ISO Code: ============================================================ Extracting ISO files . . . ============================================================ ""Win.10.1703.RS2.AiO.x64.NL.Sept.17.iso"" ""Win.10.1703.RS2.AiO.x86.NL.Sept.17.iso"" ============================================================ Checking ISO distributions Info... ============================================================ [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx64\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [ERROR] Can't open "ISOx86\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. Error: Detected ISO distributions have the same architecture. Press any key to exit.
I see "UUP" is gone from the converted ISO filename? 16288.1 Multi-Architecture ISO creation: Code: ============================================================ Extracting ISO files . . . ============================================================ "16288.1.170909-0851.RS3_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO" "16288.1.170909-0851.RS3_RELEASE_CLIENTPRO_OEMRET_X86FRE_EN-US.ISO" Code: ============================================================ 1 - Create ISO with 1 shared install.wim 2 - Create ISO with 2 separated install.wim 3- Exit The "-" is placed incorrect? ============================================================ > Enter your option and press "Enter":2 Code: ============================================================ Preparing ISO Info . . . ============================================================ ============================================================ Preparing Boot Manager settings . . . ============================================================ ============================================================ Creating ISO . . . ============================================================ CDIMAGE 2.53m CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. For Microsoft internal use only. Scanning source tree (2000 files in 189 directories) Scanning source tree complete (2006 files in 189 directories) Computing directory information complete Image file is 7353860096 bytes (before optimization) Writing 2006 files in 189 directories to 16288.1.170909-0851.RS3_RELEASE_CLIENTPRO_OEMRET_X86-X64FRE_EN-US.ISO 100% complete Storage optimization saved 748 files, 82094080 bytes (2% of image) After optimization, image file is 7277787136 bytes Space saved because of embedding, sparseness or optimization = 82094080 Done. Press any key to exit.
Yes, only install.wim is supported (forgot to mention that) UUP label not needed even in convert-UUP.cmd but just to keep things as-is
Is there any advantage to doing this method to make an 15063.0 ISO with the UUP tool and then adding the Cumulative Updates etc. through W10UI.cmd? Or better just to add the updates to the official March 1703 ISO?
Wait, the updates are already included? Edit: Never mind. But what I'm asking is it better to add the Cumulative Updates to the official March 1703 extracted ISO or use the UUP tool and add them to that ISO using W10UI.cmd?
The two have nothing to do with eachother. The UUP files are 15063.0, march release, the CU is now at 15063.632.