JFX

For BIOS booting you need to have a active primary partition. You can do this in windows diskmanager.

It's ready when it's ready. If there are no further problems it will be final on Wednesday.

On build 2262?, Clear type has be vanish between preview and 3.6 Final, for tabbar and OK, Cancle, buttons.

There are no other features, it's mainly a bug fix version.

Beta 8 adds ReFS support for Windows 11 Dev builds. ReFS version should be displayed (you need at least the current version 3.9). Format dialog will show this option regardless of the Windows edition, no need for Enterprise or Professional Workstation.

No, all files that are fully stored on local disk are still being captured. Only files with attribute FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS are skipped. It's not possible to capture them. These files will be loaded from cloud storage during first read access. For online VSS capture this wouldn't work because the snapshot is read-only and for offline capture the cloud provider is not running to transfer the data.

Some listview glitches with dark dialogs: - drive properties hardware tab has listview with black text color - security tabs listview items have sticky focus rectangles.

I guess it's UEFI only, there is no ReFS read support in the BIOS version of bootmgr.

Hmm, Microsoft does not seem to give any information about current ReFS limitations. I need to make some tests with it. For now you can use it, by removing checks via WinNTSeup.ini [Options] NoFileSystemChecks=1

WinNTSetup 5.3 Beta 7 - workaround windows 7 Dism /add-driver bug 30 (AMD, NVIDIA drivers with LZSS compression) - workaround EFI NTFS driver bug - fixed capture problem with OneDrive On-Demand files - added combobox script selection to diskpart window - added -diskpart command line switch to bring up diskpart window - added WIM_MSG_ERROR and WIMLIB_PROGRESS_MSG_HANDLE_ERROR Messagebox choice

Dark dialogs are looking great. Only the RICHEDIT50W controls used by "Digital Signature" file properties are still white.

It's seems to run a diskpart script and assign S: and W:, then calls WinNTSetup like this: WinNTSetup_x64 NT6 -source:"D:\sources\install.wim" -wimindex:1 -syspart:S: -tempdrive:W: -unattend:"path_unattend.xml" -compact:xpress4k PS: See, F1 -Help for command line options

https://mega.nz/folder/ObATya7C#oR2t79bT-4MGjKxOAYwkbQ https://www.mediafire.com/folder/53um6k2nmhvd5/

I mean format these lines you posted with the forums code button. As for WMI applications there no easy telling, many using it, but seems to work without it.

Please use code tags. Your list is a bit radical. Most of them are empty folder or space gain is minimal. Deleting wbem folder saves some space but will break all applications that uses WMI. Downlevel folder should be save, if recall correctly it's only be used while servicing from older WinOS. (like Win7/8 uses dism to add drivers to offline Win10/11 system)

Hmm, never got this error message. There is currently no way to skip errors. Can you post log file: %TEMP%\WinNTSetup\Logs\wimlib_error.log (don't close WinNTSetup it will delete the temp folder) @galkinvv Thanks for these tests. I will remove the 2 Messageboxes and silently create/delete the folders in next version.

I've added the temporary creation of the 5 folder in case of UEFI boot file creation on NTFS drive. It shows a message box after creation and deletion. WinNTSetup_x64.7z

Interesting, but I guess this is a very rare problem caused by a specif BIOS. Or the combination of that BIOS plus the creation\formation of the partition with gparted. Can these 5 fives be deleted after creation or are the required?

Good, than it's probably the drive label. GUI is using the filename as drive label. I can't find anything other than it is limited to 32 characters. Beta 6 will now trimm it to 32 chars or rename the label to "VHD" is case of such a problem.

Yes, if the WIM already exists, than a new index will be appended to it.

Happy New Year. If you select the current Windows Installation as source, WinCopy and WimCapture will always create a shadow copy.

Use a clean MinWin default profile without it. I tested it against some Windows 11 ISOs 21H2, 22H2 and also latest DEV.

Well there is only one way to tell if your mysoftware.txt is the problem ...

What happens if you just copy your mysoftware.txt inside the current MinWin profile?

But, without transparency option, wasn't it SAB which changed the title bars to 0x202020 color in dark mode?