JFX

WinNTSetup 5.2.1 - fixed NT5 GUI bugs - fixed MBR not written for VHD files (regression 5.2) - fixed error popup with old card reader devices - fixed regimport ignored HKEY_CLASSES_ROOT - fixed noapply mode on NT6 could show NT5 builds - fixed DriveComboExclude not working on subsequent scans - fixed ini save load of driver options - increased border margins for darkmode tool tips

Thanks that fixed it.

I mean the old classic menus not the owner drawed "ImmersiveContextMenu" ones. You can still get them in explorer, if screen reader is used or with a simple IATHook on shell32.dll bool __stdcall _SystemParametersInfoW(UINT uiAction, UINT uiParam, PVOID pvParam, UINT fWinIni) { int iReturn = SystemParametersInfoW(uiAction, uiParam, pvParam, fWinIni); if (uiAction == SPI_GETSCREENREADER) *(int*)pvParam = 1; return iReturn; } But after some time (usually under 30 min) SAB 3.3 seems to remove Clear Type from them.

Back to 3.2.9c. Later version remove Clear Type from my classic context menus

PowerShell takes quite some space, if we re-add all it's NetFX dependencies, it needs.

Listviews group header is hard to read. File operation dialog looks good, but I think a thinner border for the progress bar would look better, BTW: 2 things about the update check and Installation. 1 - If Windows toast notifications are globally turned off, update check show nothing 2 - After update the restarted explorer has Temp folder as working directory

@wimb Thanks for testing. Yes some explorer features got missing especially in newer windows version. Will be fixed when I have enough time. For PowerShell I don't think it has much use in a minimal system. @click-click Resize-able GUI would not help, the resolution of your screen is insufficient. I don't know why GUIScalePlus has that effect on your netbook, maybe some "windows feature"

Better use a tool to change that stuff: System Font Size Changer

Does not happens here. Despite the 120% DPI scale, have you done something with the default system fonts?

GUI size was increased after the last x86 version. But you can manipulate the internal scaling factor by WinNTSetup.ini. [Options] GUIScalePlus=-0.025

WinNTSetup 5.2.0 - fixed capture-cli did not reset console title - fixed console tools stdout could not be redirected - fixed disk name could show trailing spaces - fixed %errorlevel% not set in some cases - fixed apply error and silent command line option did not exist WinNTSetup - fixed free drive letter scan with buggy VMware mountpoints - changed local windows listview uses VHD/VHDX icon - changed WimBoot or CompactOS apply now uses wimlib as default - changed Win7-11-Select.xml will be igored if not all fields are filled - added SecureBoot detection on Windows 7 Host - added MinWin Mode (click on Mode) - added ini option DriveComboExclude simular to BootMountExclude - improved add other OS function

Nope, it's not okay. These Acrylic classic tooltips don't have the same font rendering like classic win32 tooltips. So they appear blurry for some of us.

Pressing F5 should cause a disk rescan.

The "Find and add Windows version already installed" option will scan all partition for Windows installations. It does ignore not currently mounted VHD files. However the "BCD: UEFI combo box" should create a boot entry for the currently for installation selected windows. There is a WinNTSetup.log create inside the \Windows folder for the new installation. It should have logged the BCDBoot.exe command used to create the boot entry. For the "Unattended option" there is sadly no known way to validate it before setup. The file you select is copied to \Windows\Panther\unattend.xml. There should be a \Windows\Panther\Unattend*\setuperr.log if this error has occurred. It should give a hint whats wrong with your unattend.xml.

Did you changed something with bootice? I mean in explorer there is lower case file extension .vhd and inside bootice there is uppercase .VHD. Bootice has some bugs with BCD editing, which could cause exactly this problem. Does "bcdedit -enum" resolves device and osdevice correctly?

Good idea. With the 4 internal disks on my main machine this scrolling is a bit annoying. DriveComboExclude will be added to version 5.2, planned in 1-2 weeks ...

Just shrink your C drive by 100 MB to 1 GB and create a FAT32 partiton from the new free space. Ideally, but not necessary use diskpart's set id with c12a7328-f81f-11d2-ba4b-00a0c93ec93b to mark this partition a ESP. Select this one as boot drive in WinNTSetup and install your Win7. After you successfully booted Winows 7 to desktop you can select the same boot drive but another partition and install your Win10.

You need to partition your drive correctly, there should to be a FAT32 partition as boot drive.

Yes, you need an x64 OS if you want to boot with an X64 UEFI.

Yes, make sure they point to your NTFS partition where the VHD is located.

Shrink the partition, create a new FAT32 around 100MB in size. Mark this one active and copy all boot files from your F: to it. \Boot \EFI \bootmgr

How, is the partition layout? Many UEFI do have no NTFS driver, so you need a FAT32 partition that contains the EFI boot files.

I no longer provide an x86 version, but you can use the last package WinNTSetup_v425_WinXP_Supported.rar.

Good question, Windows 10 natively supports booting from USB 3. Never had this problem.

Yeah, the problem is you did not change the system mount point, it's still points to the old drive. WinNTSetup always set HKLM\SYSTEM\MountedDevices, \DosDevices\C: to avoid this trouble. You could load offline registry and set this value with the binary data from your current system. Or just use WinNTSetup without selecting a installation source.