Jump to content

Recommended Posts


Posted
On 8/17/2019 at 10:59 AM, wimb said:

Also the program WinNTSetup crashes when a wrong type of wim file like boot.wim is selected.
May be for the unexperienced user it is good to give WARNING - This WIM file is Not Valid as Installation file

Selecting a wrong type of wim file should be refused by the program.

Now boot.wim can be selected as installation file and then pressing Setup results in program crash.

Posted (edited)

Windows Defender false detection WinNTSetup_x86.exe ->[RSRCEmb] Trojan:Win32/Zpevdo.B   (Beta 2 & Beta 3 of version 4 )

Edited by Sonic
Posted

On my system , cpu is intel Core i5-9600k ( 6 cores without hyperthreading ) WinNTSetup use x3 active cores, is normal ?

Posted

Version 4 uses half of your CPUs physical cores, which seems the be the best trade off.
Using all cores would make the system unusable and it's unlikely that the destination drive is fast enough to actually write all the data in time.

@wimb
I can't really spot the cause, it never happens with debugger on, so I hope Beta 4 now fixes this bug.

 

Posted

Hi, Sergei.

same place, Tools\Win10Builds.ini.
You can edit the ini file to your liking.

Posted (edited)

Wrong type of wim file like boot.wim gives now when pressing Setup - Warning Windows Source invalid
So the crash is gone and this solution is OK.

There is another problem present in 4.0 Beta3 and Beta4
In case wimlib is used and Mode Wimboot Selected then After pressing Setup the program crashes.
Using WimGAPI (all cases) Or wimlib with Mode Wimboot Unchecked Or other Mode are working OK.

In version 4.0 Beta1 and Beta2 this problem did not yet occur.
 

Edited by wimb
Posted (edited)

ok for cpu , I was thinking about wrong hyper threading detection ...

I've just tried the restore system of a Microsoft Surface 3 (Win10 v1511) 4 files with format *.swm ; directly downloader from Microsoft.
WinNTSetup seems apply first swm then error -> Error Applying System image failed! 0x6: Descripteur non valide 
even with wimlib.dll

If i apply with dism or WinNTSetup3.9.4 , there isn't error.

Edited by Sonic
Posted

Hmm, this error is properly caused by the multi core decompression used in beta 4.
You can disable it in the ini with. 

[Options]
UseMultiCore=0

Can you send me the links for these *swm?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...