JFX

It's automatically done, if you install in compact or wimboot mode. Instead of adding lines like: \Windows\System32\DriverStore\FileRepository\urschipidea.inf_*\* to WimBootCompress.ini and keeping the list updated, it now scan the offline registry to catch all installed drivers that are placed in DriverStore folders.

There seems to be an incompatibility with StartIsBack++ 2.9.2 / 2.999 and 7+ Taskbar Tweaker. For most taskbar pinned programs the jumplist is empty. No problem with 2.9.1

WinNTSetup 4.2.3 - fixed Vista images could be applied in compact/wimboot mode - fixed compact:xpress4k using 8k compression with newer wimgapi.dll - fixed some command line ini option combinations - fixed vmware mounted drives disappear on winntsetup exit - new cmdline option regtweaks support wildcard file pattern - new scan offlines services to exclude Driverstore *.sys files from WOF Compression

Thanks, could reproduce it, seems to only happens with UAC disabled.

@Sonic There is no such feature, virtual disk expect mounted iso will still be available after winntsetup closed. @wimb Thanks for the report, seems MS has changed that in wimgapi.dll. Will be fixed in next version.

Some how the VMWare you and I use are quite different I've reuploaded with fix language file and urschipidea in exclusions.

Don't know why it does not work in your cases, but I enabled exclusions for all builds in version 4.2.1. (It can be disabled by ini now, see: Tools\WimBootCompress.ini)

Hi Slava09, what is the exact version of your Win 10? I think I removed compression exclusion for Windows 10 as Microsoft fixed it in 1803 or 1809 builds.

No, it's only a simple capture option. If the file exist it will append else a new WIM file will be created.

Interesting maybe an different problem. Is there anything in written in \Windows\Panther\setuperr.log?

That error is quite common, but I have my doubts that Microsoft will ever fix it. It's annoying, but not a big problem. Starting msoobe.exe manually will let you continue setup. "Windows setup could not configure to run on this computer's hardware" error during Windows 7 or Windows 10 installation"

Version 20.06.1 - option -Get-Range added ex. GWT -Get-Range N:\Win10.iso bootmgr;boot*.efi;*\boot.sdi

On my machines Win 10 2004 is quite stable actually. But I experience some explorer.exe crashes and 1 instability thanks to nVidia driver. So I'm back to 1909 at the moment.

WinNTSetup_x64.exe NT6 -source:C:\WIMBOOT\W10x64-WB.wim -syspart:%VHD_DRIVE% -tempdrive:%VHD_DRIVE% -wimboot -nobootsect -bcd:none -setup

Ah, did not thought that would be a problem, as nobody has mentioned it over time. Thanks for the work. I have uploaded the fixed languages.

@bovirus I don't understand why you have so much fun with language files. About the dialog, it's only the drive format dialog of windows shell32.dll.mui, 28672.

@bovirus This space is reserved for warning icon, for example if you select a Arm64 source. As for the dialog in German language file, it's more personal taste. I prefer Segoe UI font.

Why not add the new strings 1382-1411? @devdevadev If you find someone who split your post into a new the topic, I'll give you some basic batch file hints.

Hi bovirus, The current Italian language file should be Lang\1040.dll. To get current englisch template, right-click on title "create language file" They can be edited with ResHacker. As for the Tabs I think their meaning is understandable and there is not enough space to mention all version correctly.

Always the same, fixing one problem and creating other one Should work now. As for ISO2Offset, nope will not be included. But functionality will be added to GWT sooner or later.

Added help and readme.

WinNTSetup 4.2 - no longer needs Tools\DarkMode.msstyles - disabled multicore feature on 32bit Host by default - fixed hotfix uninstall on Windows 7 Host - fixed WIMBOOT:WIMCOPY mode on Windows 10 2004 Host - cmdline -noapply does not need a sources defined anymore - fixed NT5 install did not overwrite existing txtsetup.sif - cmdline VHD-CREATE and VHD-ATTACH return errorlevel for driveletter - updated wimlib to v1.13.3 Beta1 *v4.2 will be the last 32-Bit version, 4.3 will require Win7x64 as HostOS!

Version 20.06 - added -builddir:{name} command line to set foldername instead of ADK_6 - fixed range option with offset above 2GB in 32bit version - range option supports "care.dlservice.microsoft.com" and "software-download.microsoft.com"

Yes, will fix it in the next days.

Try GWT64.exe, it's properly a problem with signed integers in 32bit version.