But I could install this build on old PC (11 years old) and virtual installation on laptop 4 month old. So the problem is not the cab or esd files. It's bug that not each one has it.
This build, along with the last couple of builds, won't clean install on my recent Asus Rampage VI Apex x299 setup. It shows the same error as noted before in earlier replies. The problem is rife on the Microsoft forums, and seems to affect more recent equipment.
Code: ============================================================ UUP directory contains multiple editions files: ============================================================ 1. Windows 10 Home (x64 / en-US) 2. Windows 10 Pro (x64 / en-US) 3. Windows 10 Lean (x64 / en-US) 4. Windows 10 Home N (x64 / en-US) 5. Windows 10 Pro N (x64 / en-US) ============================================================ Enter edition number to create, or zero '0' to create AIO ============================================================ > Enter your option and press "Enter": Spoiler: wiminfo ImageX Tool for Windows Copyright (C) Microsoft Corp. All rights reserved. Version: 6.1.7600.16385 WIM Information: ---------------- Path: F:\Decrypters\uup-converter-wimlib-14\17650.1001.180414-2140.RS_PRERELEASE_CLIENTCLOUDE_RET_X64FRE_EN-US\sources\install.wim GUID: {0b70e7e1-1b33-adc3-25ab-953b7897249f} Image Count: 1 Compression: LZX Part Number: 1/1 Attributes: 0x8 Relative path junction Available Image Choices: ------------------------ <WIM> <IMAGE INDEX="1"> <DIRCOUNT>14311</DIRCOUNT> <FILECOUNT>69057</FILECOUNT> <TOTALBYTES>11194708251</TOTALBYTES> <HARDLINKBYTES>5117995416</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D3D4BF</HIGHPART> <LOWPART>0xE57BC707</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D3D905</HIGHPART> <LOWPART>0xF168E4A8</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>CloudE</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.17650.1001;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>17650</BUILD> <SPBUILD>1001</SPBUILD> <SPLEVEL>1001</SPLEVEL> <BRANCH>rs_prerelease</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Lean</NAME> <DESCRIPTION>Windows 10 Lean</DESCRIPTION> </IMAGE> <TOTALBYTES>2494938028</TOTALBYTES> </WIM>
Since when are generic keys country specific? These keys normally can't activate any install by itself.
haha this version of Windows (W10 S) is one joke, I don't want one for my use same if M$FT give me one free hmm I'm out help me I need restart and go back to for my beloved W10 ES EDIT: Well, thank God, I've already removed that crap, running ah! how good it is to be using an OS of "truth"
So is the ISO I downloaded with the MCT via the .BAT file hack the same one that will be available tomorrow via the updaed MCT?
Just a reminder for when Dona releases next Build. If you use UUP Tool to download Files remember to use latest API. If you get errors generally means you have to wait for API update. Download new API, then rerun Tool and it will download missing Files. You don't need to redownload all of the Files.