JFX

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.

These problem, looks like you guy using old version of shellstyle.dll with Creators Update. Not all old themes are fully working with newer windows. Post same version infos!

Don't get it, what's wrong with setting computername in unattend.xml?

dledit.7z

Disk management/diskpart uses SetVolumeMountPoint() API. I use just like imdisk, DefineDosDevice() API. Let's say it's like the subst.exe command. There were problems with the diskmgnt way back in the old XPPE days.

Oh, I see how this is going to end. Well devdevadev, better stick on the reboot forum. They have much better batch file skills than I have.

What do you want with the drive letter, if you don't know it let WinNTSetup decide.

You should use 1 syspart for both installations! And yes at some point you need to change the boot order with bcdedit.exe, to boot the second OS and continue it's setup. This will require basic batch file skills. There is not secret in how WinNTSetup detects the syspart drive. for MBR disk scheme there is only 1 active primary partion for EFI there is only 1 partition which have the PARTITION_SYSTEM_GUID guid. However it assigns the Z:\ as a dosdevice, so disk management or unelevated explorer will not show it.

Yes. Yes. Only, if you use the same syspart and install the newest system last.

Yes, you can use a VHDX. But I don't know about about trim support. Microsoft is only talking about the new Hyper-V Generation 2 emulation that supports it. They did not mentioned native VHD(X) boot. VHD and VHDX use the same driver and it's the drivers job to tell the OS that VHD(X) is located inside a SSD. It should than pass through the trim command. So I would guess both or neither formats support trim.

It are just the offset inside the ISO like jaclaz explained. I've made tool for that: ISO2Offset.7z

Have added command line support for range downloads. GWT -range:8808448-9236127 -out:"X:\bootmgr" -title:"Download Win8.1 Bootmgr" -link:/download/B/9/9/B999286E-0A47-406D-8B3D-5B5AD7373A4A/9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X86FREE_EN-US_DV5.ISOGetWaikTools.zip

I would use curl and a Win8.1 Enterprise ISO. curl -o"bootmgr" -r 8808448-9236127 http://care.dlservice.microsoft.com/dl/download/B/9/9/B999286E-0A47-406D-8B3D-5B5AD7373A4A/9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X86FREE_EN-US_DV5.ISO

Yes, registry permissions are no problem. For me the SearchOrderConfig tweak Atari800XL mentioned is enough, but maybe that has changed once again.

Yes, the folder you select will be recrusively scanned for *.inf files. However Dism will create a driver package for every inf file, so don't add too many.

Hi ilkertezcan, 1) It's no bug, I'm going to remove support for WinNTSetup_x86.exe running on x64 OS. Reason: There are some API's that can not work in WoW64 emulation, I though i could find a good solution, but it would just makes thinks to complicated. Also there is an faster x64 version available, don't know why sp many people want to run the x86 version. 2) Good, will add it to help. 4) Not so sure I like to add that.

Hi Sergei, The name comes from the XML of the WIM file. <DISPLAYNAME> is used. If this does not exists than <Name> is used. See: imagex -info wimfile.wim

Good, the ini option would be: [WinNT6\READY] BootSect=0 But better you set all GUI options and create a new ini file.

Your log file is from version 3.8.7.3, the bug should be already be fixed in the current version.

Log file is in the ?:\Windows\WinNTSetup.log. How you disable the bootsector update, command line or ini file?

During setup or during WinNTSetup ? In case WinNTSetup update the bootsector, it will be logged in the logfile. I tried with Terabyle MBR.exe utlility, that add Press F?? Key boot option. Works with NT6.x installs.

@click-click Tweaks are now read and save from the new ini sections [WinNT5\TWEAKS] and [WinNT6\TWEAKS] Same with bootsector and BCD stuff [WinNT5\READY] Yes, it breaks old ini files, but makes it easier to edit then with an editor.