JFX

No, it expects a generalized source with \Windows\System32\Recovery\WinRe.wim. But you could use driver integration from "Local Windows Installations" window, which let's you browse for WinRe.wim.

and another one goes ... Version 21.04 - removed ADK 8.1 options

WinNTSetup 4.6.1 - fixed wofcompress process did not start - new driver mode option to integrate into WinRE - driver mode option saved to ini - wimlib capture appends date time in case to avoid duplicate image name - ini option WimCaptureAddTimeStamp added WinRE driver integration is not yet default, click on the "D" button and check WinRE option

Yes, I'll add an option for WinRE driver integration. Just not sure how to identify critical from non critical drivers.

Glad it works now. The command window is separate process you can close WinNTSetup while it's running. The Wofcompress.exe tool is merge in and can be also used from command line: WinNTSetup_x64.exe wofcompress.

Hmm, try if 4.6.0.1 fixed it.

WinNTSetup 4.6.0 - fixed vhd detection regression - fixed dism dowload was missing logprovider.dll - fixed possible freeze caused by PathCompactPath - fixed possible freeze with "-noapply" mode - fixed some High DPI issues - fixed commandline iso attach did not return errorlevel for driveletter - dismount of vhd with hidden bootpart will force remove all it's drive letters - driver integration now uses dismapi, trys to avoid adding drivers of different architecture - driver export now sorts by driver class - move Tools\WimBootCompress.ini to Tools\Compact\ - logging content of internal VHD BCD store - added Win7USB3 driver integration / post install fix option (see Tools\Win7USB3\ReadMe.txt) - added wofcompress option - added remove autocheck option *Last 3 are right click features: https://ibb.co/NmXNbY0

Hi Renodos, not really, WinNTSetup needs an WIM or ESD image to work with. However, you could capture this WTG to a WIM file and use this - let's call it backup.wim - as source. Only downside with this is that no Recovery menu option (WinRE) will be created.

Yes, but you should focus more on your system: Check if there is a image in: %AppData%\Microsoft\Windows\AccountPictures that matches HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AccountPicture, SourceId. Clear thumbnail cache. Try to temporary chance the picture.

There is no problem with avatar here, 19043.844 with SIB 2.9.8.

WinNTSetup 4.5.1 - VHD GUI will be saved to ini - ini option BootMountExclude supports DiskID - fixes listview font on non darkmode

Right, for 2 equal disk vendor name is useless here, next version will support disk id.

Run from admin cmd.exe: WinNTSetup_x64.exe disks

WinNTSetup 4.5.0 Final - Dropped 32-Bit version, system requirements are now Windows 7x64 + - VHD functions no longer uses diskpart.exe - VHD Attach / Detach supports ISO files - VHD Creation supports GPT Partitionsttyle - VHD Install will always create internal boot files depending on partition style - new default VHD creation type MBR - BIOS/UEFI - added VHD command line options /gpt and /mbr - fixed instant VHD creation cylinder bug - fixed iso mount does not select install.swm - Fixed open file dialog pattern not working on default WinPE 3.x + - Fixed wimgapi capture build number on H2 Systems (19041 instead 19042) - Support multiple "-regtweaks" cmdline switches - Workaround Win10 MessageBox Font bug - added ini option [vhd] bootpartsize - new ini option "RemoveBootMountsOnExit" - ini option BootMountExclude supports Vendor name - rewrote all file and registry recursion functions to use iteration - command line VHD creation uses expandable by default - command line VHD ignores disk size for expandable type - removed NT5 uxtheme patch - DPI-Awareness for Imdisk - Darkmode and DPI-Awareness for Bootice - ARM64 password reset - fixed ARM64 uxtheme patch

RC3 is out, if there no bugs anymore, this one will be final soon.

RemoveBootMountsOnExit does remove the mounted boot partitions (active primary or ESP) usually mounted as Z:. There was a bug with this option, you will need the re-download RC2.

WinNTSetup 4.5.0 RC2 - new ini option "RemoveBootMountsOnExit" - rewrote all file and registry recursion functions to use iteration - command line VHD creation uses expandable by default - command line VHD ignores disk size for expandable type - fixed iso mount does not select install.swm

WinNTSetup 4.5.0 RC1 - ini option BootMountExclude supports Vendor name - fixed VHD drive letter assignment - fixed Windows 7/8 compatiblity

They have an EFI folder on the second partition. Hidden Sectors should be equal to diskpart now. Both use the offsets from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment I guess this is a Grub problem, they booting attach to VMWare in BIOS and UEFI mode.

WinNTSetup 4.5.0 Beta 3 - fixed VHD Creation system default partition alignment - increased VHD creation volume arival timeout - set errorcode in case hitting volume arival timeout - fixed instant VHD creation cylinder bug - new default VHD creation type MBR - BIOS/UEFI - added VHD command line options /gpt and /mbr

It's properly the timeout I set. It's currently waiting only 500 ms for the newly created volumes be recognized by the OS. I really should do something about error 0x0 message.

You could try the fixed VHD with GPT layout for your UEFI RAMOS. Indeed, with the new VHD function the "system default" for alignment currently don't work and uses biggest value of 4096 hidden sectors.

WinNTSetup 4.5.0 Beta 2 - removed NT5 uxtheme patch - fixed mounting boot partition regression - improved bootice darkmode

Replace these 2 in C:\Windows\System32\drivers VMware-workstation-full-16.1.0-17198959.exe\VmciSockets.cab\vmci.sys_Vista.20BE52C5_0815_4F26_9816_FB06A9A9F012 VMware-workstation-full-16.1.0-17198959.exe\USB.cab\_driver_hcmon_sys_win7_x64.AB568CC9_1F06_4225_B985_9531B0D3BB56

Fragmentation does not matter with SSD and recommending something that writes multiple GB on a flash disk would be wrong.