JFX

Hi abbodi1406, The log is placed in the Windows folder of the chosen installation drive. Seems a wim index without <arch> in the xml is interpreted as x64. Will fix this.

I'm still curious about the exact time that is written to the log file Something like this: Successfully applied WIM Image. (Operation took: 1:03 min)

No, there is no verify made and temp folder is set to be the installation drive. Do you measured yourself or are the 7 minutes from the WinNTSetup.log?

Is there any way to exclude programs form showing up in recent used list? Windows 7 has a NoStartPage registry entry for this, but SIb seems to ignore it.

Time difference could be caused by disk caching, here on a ryzen + ssd system I get simular times for both (around 2 minutes +- 5 seconds).

Interesting, thought they wanted to deprecate imagex, but now it proves to be useful again. Seems to work nice, just wonder does wimgapi/imagex 16299 works for you? I'm always getting something like this: But it is working fine with wimgapi 15063.

Yes, Microsoft does not allow OS upgrades with VHD(X) boot. Easiest way would be to boot the VHD in Hyper-V and make the upgrade there.

Yep, DISM command line does not allow more than one /SWMFile parameter. And *.* is not accepted, so it requires that all files have the same extension.

Wimgapi is actually able to use cab files as reference, but yes for wimlib I convert them on the fly.

Uploaded a new Beta version, with improved support for UUP sources. No need for uup.txt and no conversion of *.cab files is needed, but you should stick with old wimgapi.dll (15063 RS2) as newer one seems to be buggy.

Hmm, I also can't download any file from OneDrive currently. Here is a mirror: WinNTSetup3.rar

I'll add this tweak to the one that hides cortana and this taskswitcher. Have no good idea about that edge window, but why not disable egde completely. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MicrosoftEdge.exe] "Debugger"="NUL"

The ADK also has web installer, so it's easier to just download the needed files. http://download.microsoft.com//download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/adk/adksetup.exe or save another MB: http://download.microsoft.com//download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/adk/Installers/Application Compatibility Toolkit-x64_en-us.msi http://download.microsoft.com//download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/adk/Installers/0a3a39d2f8a258e1dea4e76da0ec31b8.cab http://download.microsoft.com//download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/adk/Installers/83bd1072721871ea0bdc4fab780d9382.cab http://download.microsoft.com//download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/adk/Installers/f7699e5a82dcf6476e5ed2d8a3507ace.cab

Okay Final version 3.8.8 is online. Fixing a few bugs that were left in the last Beta.

I rewrote the tool a few times, File size was usually reduced a lot. But now there is a new version 17.10 without upx wich bigger again.

I'm waiting for the new ADK to call it Final/RTM. But if takes to long we can have a few more Beta versions.

I assume one of the tweaks had a key starting with [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet] instead of [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001]. With Beta3 it's supported again, as it really will cause a BSoD.

You can send me the reg tweaks folder, so I can compare it with the old method.

Don't know it should not make any difference.

Yes, what just a typo

Didn't succeed is bit vague. WinNTSetup's -ref parameter is similar to the one of imagex/wimlib or dism's /SWMFile switch. Anyway just add an empty file called uup.txt, if it exist you don't need the command line. Beta2 is out and fixes another issue with these ESD files. BTW: you have to convert the cab files yourself first to esd.

There is a lot of code changes in the beta. Next one will have a change log. Well UUP should work now. You can add a UUP.txt in the same folder as the esd files than you don't need to use cmdline.

Yes, it should be supported, but will require the command line ref option. There is no way to tell that these esd are not standalone ones. I did try it yesterday and today. I choose the fully unattended option. But maybe the problem is my poor Internet speed. Well it took some hours to download these 5 GB.

Hmm, wasn't able to download these UPP dumps without errors. Currently the -ref: cmd parameter is ignored in this case, but will be fixed in next version.

Hmm, right click on the unattend label and check/edit the xml if necessary.