On 7/17/2024 at 10:10 AM, JFX said:

@ibay770 WinNTSetup has reach EOL status.

So  v5.3.5.2 will be the last released version?

 

 

Can we know the reason why it should stop here and now? Aren't there any more margins for improvement?

On 7/17/2024 at 10:10 AM, JFX said:

@ibay770 WinNTSetup has reach EOL status.

It would be very  nice if you can share the Final Program Code and the Final Release of WinNTSetup v5.3.5.2 at GitHub for future generations  

Edited July 31, 20242 yr by wimb

Attaboy! And also for any further improvements; don't forget, higher aims ahead, no matter whose aims!

Ermm... Maybe JFX means "feature complete" status? I believe he mentioned that before.

So hopefully not EOL?

But for now I hope he enjoys a nice vacation...

 

When wimb and jfx co-operate, that'll be the day!!!

 

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.

do not brute-force delete or zerobyte \windows\wbem if u do not want to lose full powershell functionality. u can move it out of the vhd and junction it back into its original place, though, if u feel u need to - it'll work as long as powershell.exe finds it. just one more caveat - the wbem folder is better off being from windows 10 rather than from windows 11. it will work ok in either system, which is not the case with the win11 one.

Well, forget about the above, PowerShell 7 will tell and I will update - well, we are better off keeping separate junctions for win10 and win11, just to be on the safe side. as for powershell, u can have either or both, and play around with various versions of wmiutils.dll, wbemprox.dll and wbemdisp.dll, depending on the win10 build. win11s all work spick&span.

And... yet another caveat: do keep the defauut and public subfolders intact beside your username in the users folder - do not move them anyplace else if u want most of the software (espacially the windows native software) to work ok.

 

Edited August 20, 20242 yr by Antonino

as for the  above-mentioned boot failures and BSODs, I suggest that u should go as far as the 22621 series to install ok. I also recommend a microwin session in advance and a good autounattend.xml install, to avoid useless inconveniencies and redundancies.

Edited August 15, 20242 yr by Antonino

Hi, is it possible to add a "BitLocker" disable option to the system setup when installing the system?

we should ask christoff shenanigan about this, I guess.

 

On 8/16/2024 at 4:22 AM, Nikolay said:

Hi, is it possible to add a "BitLocker" disable option to the system setup when installing the system?

BitLocker is disabled when you use Unattend section. (since May 2024).

Sonic,  Do you mean using the "Win7-11-Select.xml" response file when installing the system?

On 8/9/2024 at 4:58 PM, sharicov@gmail.com said:

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.

The problem may be related to BootDriverFlags in HKLM\SYSTEM\HardwareConfig set to 0. Set it to hex 1c before booting vhdx. You will need to mount the vhdx and use a remote regedit to check to and change the setting .

 

Edited August 18, 20242 yr by click-click

11 hours ago, Nikolay said:

Sonic,  Do you mean using the "Win7-11-Select.xml" response file when installing the system?

yes