Jump to content

Recommended Posts

Posted (edited)

JFX, thank you for new version!

But what means  "wim capture regressions" ?

And one more question: Is it safe to check "merge ide" checkbox to stay allways checked, or recomended not to be checked?

Edited by dimo70

Posted

Last version could fallback to xpress compression and also ignoring the compression level.

I don't think "merge ide" will cause any problems, but i would not recommend to use it without reason.
I is really only thought to apply or copy a not generalized image to different hardware.
 

Posted

Hmm, just don't delete the files it comes with.
Unless there are critical bugs or needed changes for Windows 12, no further development is planed.

Posted

not deleted , but updated manually my base folder...
I like to check what files changed ... deleted the older wimlib but missing copy the new ....

Posted (edited)

@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!"

Edited by sharicov@gmail.com
Posted (edited)
21 hours ago, sharicov@gmail.com said:

@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.

Is a crashdump created or can you post the error information from event log?

 

21 hours ago, sharicov@gmail.com said:

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!"

Newer version will execute "Tools\x64\WIMHost.exe" to apply the WIM file.
If no error code is displayed, it could only mean that the program did not even start.

Maybe an antivirus program intercept here or WinNTSetup is located on a network share.

WinNTSetup tries to run WIMHost.exe with "trusted installer" rights maybe that is the problem.

Add a WinNTSetup.ini next to WinNTSetup_x64.exe with following contain, and try again.

[WimHost]
RunAsTI=0

 

Edited by JFX
Posted (edited)
17 hours ago, JFX said:

Is a crashdump created or can you post the error information from event log?

 

Newer version will execute "Tools\x64\WIMHost.exe" to apply the WIM file.
If no error code is displayed, it could only mean that the program did not even start.

Maybe an antivirus program intercept here or WinNTSetup is located on a network share.

WinNTSetup tries to run WIMHost.exe with "trusted installer" rights maybe that is the problem.

Add a WinNTSetup.ini next to WinNTSetup_x64.exe with following contain, and try again.

[WimHost]
RunAsTI=0

 

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).

Edited by sharicov@gmail.com
Posted (edited)

Good, I will add a fallback for RunAsTI setting.

About the crash, is there anything in windows eventlog?

Edited by JFX
Posted (edited)

I am deploying Win11 23H2 22635.2486 EN into dynamic VHD,
I have the same error as sharicov@gmail.com
Helped with advice
[WimHost]
RunAsTI=0
But at the end there is also an error, the boot files were not created (you can see it on the screenshot in TotalCmd)
in WinNTSetup v531a everything is fine

BCD settings on screen 2

 

222.jpg

333.jpg

Edited by sakatgg
Posted

The RunAsTI problem will be fixed.

Are you sure the second problem isn't caused by this NTLite source?
Please post the log file H:\Windows\Logs\WinNTSetup\*\WinNTSetup.log

And what happens if you manually run bcdboot.exe?

bcdboot H:\Windows /s H: /f BIOS

Posted

The problem is solved; in the lightweight Win11 from which WinNTSetup v5.3.3 was launched there was no c:\Windows\System32\bcdboot.exe. Added everything worked.

I also checked that indexing was turned off - it turned off normally. Thank you.

Posted

thank u ever so much jfx. Everything works here, but I am not so significant a tester, as I have always run ur winntsetup from powerrunx64.exe. so no issues so far. the only think that did not work at the outset was wimmization with winlib, which I righted immediately by switching to w**api or something like that (the alternative provided, I mean).

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

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