I've tried UUPDL v0.14.39 but, for me, it's still offering only 17686.1003 Maybe @s1ave77 is still working on it
This build installed via WU The previous 2 builds failed with a GSOD immediately after 75% of installation. Still no sign of sets, I reckon the clean install I did a few builds back has killed them on this PC (sets do work on a tablet using the same MS account)
14.42 Successful Thank you 17692.1000.180609-1317.RS_PRERELEASE_CLIENTPRO_OEMRET_x86FRE_EN-US.ISO 17692.1000.180609-1317.RS_PRERELEASE_CLIENTPRO_OEMRET_x64FRE_EN-US.ISO
s1ave77 Can you explain just what went wrong with the 17692 UUP Download ? Was it from Microsoft's Server side ? We had 14.39 then 14.42 before we could download the 17692 UUP Files.
I did a test and all went well. Code: ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Preparing Reference ESDs . . . ============================================================ CAB->ESD: microsoft-onecore-applicationmodel-sync-desktop-fod-package-amd64 CAB->ESD: microsoft-windows-hello-face-migration-package-amd64 CAB->ESD: microsoft-windows-hello-face-package-amd64 CAB->ESD: microsoft-windows-internetexplorer-optional-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-basic-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-handwriting-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-ocr-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-speech-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-texttospeech-en-us-package-amd64 CAB->ESD: microsoft-windows-mediaplayer-package-amd64 CAB->ESD: microsoft-windows-quickassist-package-amd64 CAB->ESD: microsoft-windows-tabletpcmath-package-amd64 CAB->ESD: openssh-client-package-amd64 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating boot.wim . . . ============================================================ Using LZX compression with 8 threads Archiving file data: 936 MiB of 936 MiB (100%) done "ISOFOLDER\sources\boot.wim" original size: 388560 KiB Using LZX compression with 8 threads Archiving file data: 1011 MiB of 1011 MiB (100%) done "ISOFOLDER\sources\boot.wim" optimized size: 383840 KiB Space saved: 4720 KiB ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 8 threads Archiving file data: 7144 MiB of 7144 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 261 MiB of 261 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 216 MiB of 216 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 227 MiB of 227 MiB (100%) done ============================================================ Adding winre.wim to install.wim . . . ============================================================ ============================================================ 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 (500 files in 36 directories) Scanning source tree complete (936 files in 83 directories) Computing directory information complete Image file is 4352344064 bytes (before optimization) Writing 936 files in 83 directories to 17692.1000.180609-1317.RS_PRERELEASE_CLIENTMULTI_UUP_x64FRE_EN-US.ISO 100% complete Storage optimization saved 5 files, 32768 bytes (0% of image) After optimization, image file is 4354381824 bytes Space saved because of embedding, sparseness or optimization = 32768 Done. Press any key to exit. Did you check if there is enough free disk space on c:\ and on the partition you run UUP>ISO v16 on?
MS constantly altering the packages lists for new builds. Fetching those is entirely @mkuba50 magic, the script only maintains the Reference Builds needed for the fetches.
Did you figure out any solution for Classic Shell not working. Through trial and error, I now know that v 4.2.2 works fine on this build. Its not good enough as the latest, but at least gets the job done.