sharicov@gmail.com

thanks a lot for detailed answer!

Another issue: when trying to create wim from latest windows 10 US downloaded from MS getting following info: Build = 19041 Service Pack = 3803 Only SMALL = WinxShell Version supported Or Use windows 10 x64 Prefer Service Pack = 264 Win 10 Service Pack 2006 = OK for LARGE Version Where do I get this version of Windows 10?

Created wim with latest version of Make_WinPE_Trusted-86, using latest win11 iso Win11_23H2_English_x64v2 (all default parameters) when trying to create vhd as target using winntsetup (latest) getting error: Error windows pe at source. Same error using windows 10 wim made with Make_WinPE_Trusted

Created wim with latest version using latest win11 iso Win11_23H2_English_x64v2 (all default parameters) when trying to create vhd as target using winntsetup (latest) getting error: Error windows pe at source. Same issue with windows 10

it is working now, but I don't know what have changed, iso is the same for sure, usb is also the same, bit it just works, maybe I'd repartitioned the ssd differently (efi partition), not sure...

Cannot install Windows 11 from Win11_23H2_English_x64v2.iso Windows 10 installation works fine (source: Win10_22H2_EnglishInternational_x64v1.iso) Installing on USB disk (Samsung T3) Winntsetup version 5.3.5.2 Tried all ways: normal, VHD and VHDx ways, static and dynamic. Getting VHD BOOT INITIALIZATION FAILED Blue Screen error or BOOT INITIALIZATION FAILED Blue Screen error depends on installation type. Please help.

Server 2022 getting following error with 5.3.4: "The code execution cannot proceed because BCDBoot.exe was not found". 5.3.3b works perfectly well on the same PC.

Dimo, I see some possible malware alerts in ntfs2fat32.exe Attaching Virustotal screenshot

Thanks, now runs well. Is there a way to view/edit the scripts?

Hi dimo70, don't know what it does, but I am getting following error when trying to run it on windows 10 x64 (latest):

Dear JFX. 3 feature requests, if possible: 1. Option to create BCD volume without OS installation (useful with new disk when I already have vhd files and only want a boot menu on start). Of cause vhd entries will be done manually using bootice, or you can just set defaut names such as Windows10.vhd and Windows11.vhd. Ideally with gui for existing partition resize and creation of new EFI partition, but not a must. - Example: DISKPART/SELECT DISK/CREATE PARTITION EFI and populate it with BCD 2.Option to install minimal windows just for technical activities like rename main vhd, restore vhd from the backup etc. Something like what NTDEV's tiny11 script does just built in: https://github.com/ntdevlabs/tiny11builder 3. when VHD created it has an ESP partition, but it's not bootable, could you please add BCD to it when doing setup (kind of "bcdboot C:\Windows /s G: /f UEFI") will greatly help when running the VHD in the Hyper-V) Thanks in advance, really enjoying using your project!

Changing .ini file helped, working well now. Thanks a lot! Only remaining problem is WinNTSetup crashes after completion with no error message, but everything works then (new system appears in BCD menu and operational).

@JFX winntsetup 5.3.3 crashed with windows 2022 datacenter desktop installation to new vhd vhd was created, but winntsetup window closed when ran setup. version 5.3.1 working well for same task with same environment (ran under up to date windows 10 x64) Error window says "Applying System image failed!"

you are welcome, JFX. Command line worked perfectly fine, while same name with the GUI gave an error.

Another bug (not critical): Select location of the boot drive shows inexistent 0 size partitions (screenshots of winntsetup and MS disk manager attached).

@JFXThanks again for the great project! Have a strange VHD related bug in all versions (including beta 5). When creating VHD with symbols (ex. _ or .) getting following error window (attached). VHD is actually created and seen in the disk manager, but not formatted. Can format it manually and map with a drive letter. VHD without symbols in the name works fine. Please fix.

Thanks JFX, You are absolutely right, it was corrupted OS, from another OS VHD creation running perfectly fine! Thanks for the upcoming differencing VHD support!!!

Lately started getting error messages when creating new vhd dynamic files. "Error creating VHD 0x495 - The Volume ID could not be found." After the error VHD file appears and cannot be deleted until reboot or mount and unmount. Also having strange size of 90+MB (dynamic). Either error, or WinnNTSetup hangs while creating the disk, only can be killed via task manager. Windows disk manager creates dynamic VHD without any problem. Error occurs both in 5.2.4 and 5.2.5. Windows 11 Pro build 22000.795 If creating static instant VHD via WinNTSetup it takes really long time (several minutes) while previously it was actually instant. On another point. I am normally running WinNTSetup from read only media (iso file), each time it asks to install ADK, each time getting "Downloading ADK files failed!" and then it works fine, Is it possible to skip the ADK download or not to ask to install it if media is read only? Thanks for great solution! Really great program!!! P.S. I'd recently discovered for myself differencing VHD mechanism built in in windows, is it possible to integrate it in one of the embedded tools of WinNTSetup to create differencing VHD, attaching them to existing VHD and creating BCD entry for it? Would be really nice to have it there!

Mega link is wrong:

Unattended option doesn't work, getting following error on boot:

Thanks for quick response, JFX. You was completely right, issue was capital .VHD, once changed it to .vhd it started booting, which is really strange since my current boot vhd is written in capital and it's working: Answering your previous questions, I just added vhd boot entry in bootice, no modifications. Strange thing, WinNTSetup doesn't add new boot items automatically any more even if I chose "Find and add Windows version already installed" (screenshot attached). "bcdedit -enum" output attached:

WinNTSetup 5.1.12 is not working with the latest Windows 11 build 22543.1000 (x64) Iso image generated on uup dump site. Installing windows into vhd just as with previous builds, no tweaks used/not unattended. On boot gives error 0xc0000225, cannot boot.

@JFX - solved by installing with winntsetup from vmware workstation and exporting the vhd file out. Suppose it can be related to changes BCD mechanism. Also normal windows setup is no more supporting installation to usb sdd that was working previously.

Getting BSD with final Win 11 V21H2 x64 on first boot with WinNTSetup 5.0 b4 With WinNTSetup 5.0 Final getting "windows setup could not configure windows to run on this computer's hardware." error message. (on computer that supports and runs native installed Win 11 V21H2 x64

FYI Uploaded Win Reduce Trusted to Yandex Disk, it says file contain virus. Message from cloud provider: Name: Win_Reduce_Trusted-36.zip Size: 8.4 MB Modified: 16.11.2020 09:41 The file is infected with a virus.