Thanks to update the language files.

 

On 6/3/2020 at 11:23 AM, JFX said:

WinNTSetup 4.2

- no longer needs Tools\DarkMode.msstyles
- disabled multicore feature on 32bit Host by default
- fixed hotfix uninstall on Windows 7 Host
- fixed WIMBOOT:WIMCOPY mode on Windows 10 2004 Host
- cmdline -noapply does not need a sources defined anymore
- fixed NT5 install did not overwrite existing txtsetup.sif
- cmdline VHD-CREATE and VHD-ATTACH return errorlevel for driveletter
- updated wimlib to v1.13.3 Beta1

*v4.2 will be the last 32-Bit version, 4.3 will require Win7x64 as HostOS!

Plus:
- Undocumented nice feature for Unattended Install 
  where
  LocalAccount = UserName
  FullName = RegisteredOwner
  Organization = RegisteredOrganization

Thanks for this handy feature 

Another topic, I have serious BSOD problems with Windows 10x64 version 2004 as described in

BSOD Crashes Windows 10 since May Update

What do you think about it ?

Edited June 7, 20206 yr by wimb

5 hours ago, wimb said:

What do you think about it ?

On my machines Win 10 2004 is quite stable actually.
But I experience some explorer.exe crashes and 1 instability thanks to nVidia driver.
So I'm back to 1909 at the moment.

Thank you for sharing your experience regarding Win 10 2004.

I decided also to stay at 1909 until BSOD problems are solved ....

The bootmgr files released since 2020 silently fail to be updated by bcdboot command.
For the bootmgr x64 versions of january and april I got failure of setup for install in VHD of Win 7/8 x64 and Win10x86 

The problem is fixed by Microsoft with the latest release of bootmgr x64 of Win 10 version 2004 
This Win10x64 bootmgr file of 11-05-2020 as tested by me allows Install of 7x64 and Win10x86 in VHD booting in MBR BIOS mode.

Edited June 16, 20206 yr by wimb

That error is quite common, but I have my doubts that Microsoft will ever fix it.
It's annoying, but not a big problem. Starting msoobe.exe manually will let you continue setup.

"Windows setup could not configure to run on this computer's hardware" error during Windows 7 or Windows 10 installation"

2 hours ago, JFX said:

That error is quite common, but I have my doubts that Microsoft will ever fix it.
It's annoying, but not a big problem. Starting msoobe.exe manually will let you continue setup.

"Windows setup could not configure to run on this computer's hardware" error during Windows 7 or Windows 10 installation"

Thanks for the info on using msoobe.exe to fix the annoying Windows setup error.
I tried to use msoobe.exe to fix the error but it did not work for me 
I have hope that 2004 version of bootmgr can prevent the error .... In any case that worked for me. 

Edited June 17, 20206 yr by wimb

1 hour ago, wimb said:

I tried to use msoobe.exe to fix the error but it did not work for me 

Interesting maybe an different problem.
Is there anything in written in \Windows\Panther\setuperr.log?

1 hour ago, JFX said:

Interesting maybe an different problem.
Is there anything in written in \Windows\Panther\setuperr.log?

Yes

2020-06-17 16:24:52, Error                 TOOL   BCD: File is not system store. File: \Device\HarddiskVolume4\Boot\BCD Status: 0
2020-06-17 16:24:52, Error      [0x0e00b3] TOOL   Sysprep_Specialize_Bcd: There was an error opening the system store. Status=[0xC0000098]
2020-06-17 16:24:52, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll; dwRet = 0x3ee
2020-06-17 16:24:52, Error                 SYSPRP SysprepSession::ExecuteAction: Failed during sysprepModule operation; dwRet = 0x3ee
2020-06-17 16:24:52, Error                 SYSPRP SysprepSession::ExecuteInternal: Error in executing action for Microsoft-Windows-Sysprep-SpBcd; dwRet = 0x3ee
2020-06-17 16:24:52, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0x3ee
2020-06-17 16:24:52, Error                 SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x3ee
2020-06-17 16:24:53, Error      [0x060435] IBS    Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x3ee

The bootmgr files released since 2020 silently fail to be updated by bcdboot command.
For the bootmgr x64 versions of january and april I got failure of setup for install in VHD of Win 7/8 x64 and Win10x86

In MBR mode booting with bootmgr x64 version 29-04-2020 (1909 update) then there is a mismatch with booting Win10x86 VHD during Setup.
Normally WinNTSetup will update bootmgr file (by using bcdboot ?) so that it corresponds to Windows to be installed.
The bootmgr versions since 2020 refuse replacement by bcdboot.exe

The issue is solved by Microsoft with bootmgr of version 2004 that also is not updated by bcdboot, but allows to Install 7x64 Or 10x86 version in VHD without the reported error.

hi,

will the capture wim create custom.wim if there is install.wim? (wimboot) reference: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/dn605112(v%3dwin.10)

4 hours ago, josywong said:

will the capture wim create custom.wim if there is install.wim?

No, it's only a simple capture option. If the file exist it will append else a new WIM file will be created.

Hello, Could you please help, I'm trying to install Win10 x64 different versions using WinNTSetup 4.2 with compression greater than 4kexpress, as a result, the system does not boot. A message appears that the hal.dll file is corrupted or does not exist. with 4kexpress compression, the system boots normally. i'm trying your scripts with diskpart as well.. 

8kexpress, 16kexpress and lzx compression methods have yellow color, only 4kexpress and non compression methods have green color. 

 

Hi Slava09,

what is the exact version of your Win 10?
I think I removed compression exclusion for Windows 10 as Microsoft fixed it in 1803 or 1809 builds.

JFX, i tried different versions on VMWare - Win10 1607, 2004, 1909, as a result, Windows did not boot up. Would you please check on your side. i would prefer to install 1607 with 16K EXPRESS or LZX.

WOFCompress.exe works good, Windows boot up, but i would prefer to use WinNTSetup. buy the way, in WOF Compress GUI 3.3 - Window "Drive or Folder" did not work in Win Boot PE. 

 

 

WOF_Compress_x64.exe Version 3.3 is working OK in Win10XPE made according to Win10_Install.pdfand in ChrisPE Environment.

Can you give Link for the PE that you are using ?