November 26, 20232 yr 3 hours ago, Antonino said: sorry dimo, but I cannot see the update, nor can I see the screenshot Hi, see this links: https://www.upload.ee/files/15986935/NTHelper.exe.html Edited November 26, 20232 yr by dimo70
November 28, 20232 yr Dimo, I see some possible malware alerts in ntfs2fat32.exe Attaching Virustotal screenshot
November 30, 20232 yr Antonino, i updated the link You can extract from arhiv and use https://www.upload.ee/download/15999747/a8e8e08347ea1deefc0f/SetupNT.zip Edited November 30, 20232 yr by dimo70
December 3, 20232 yr Author @dimo70 Don't merge the old x86 version into the same folder with newer x64 one. They have different folder layout, so there will be problems.
December 3, 20232 yr JFX, thank you for advise, i will not merge. I thing it will be better to remove my other tools. By fact the only interesting thing in my Helper is DiskPartAsc. It can be used as separated tool befor use WinNTSetup. WinNTSetup must be used only as ist in original tool. Edited December 4, 20232 yr by dimo70
December 4, 20232 yr I'm still somewhat confused how the BIOS option ALL in WinNTSetup is supposed to work. When I boot a VHD from a USB stick and run powershell $env:firmware_type It always returns 'Legacy' when running on my Thinkpad that has CSM support for both UEFI and BIOS. Apparently setting ALL still boots in BIOS mode. If I set the BIOS for the Thinkpad to UEFI only, the VHD won't boot. What else needs to be done or toggled with WinNTSetup so either mode for booting will work? Edited December 4, 20232 yr by click-click
December 4, 20232 yr JFX, if backup system into wim file with your tool, how will be better to restore on another disk later if needed?
December 4, 20232 yr Author 2 hours ago, click-click said: I'm still somewhat confused how the BIOS option ALL in WinNTSetup is supposed to work. The "ALL" is just passed to bcdboot.exe, which than creates BIOS and UEFI boot files. If it does not boot in UEFI mode, than either the boot partition is ignored (maybe it's NTFS) or the UEFI is a bit picky and does not look for the EFI boot loader on a MBR disk. If the UEFI allows it, try to start the loader manually: \EFI\Boot\bootx64.efi @dimo70 Yes just use WinNTSetup to apply the backuped WIM, it will change drive letter assignment and create a new boot entry.
December 4, 20232 yr As long as i use WinNTSetup likes more. Its not only setup tool, but a whole combain Aio Tool. Edited December 4, 20232 yr by dimo70
December 4, 20232 yr yes, the flash is formatted ntfs, How would I start the loader manually: \EFI\Boot\bootx64.efi from the flash?
Create an account or sign in to comment