JFX Posted October 19, 2023 Author Share Posted October 19, 2023 WinNTSetup 5.3.3 - fixed wim capture regressions - fixed trusted installer could not access temporary drive letters - automatically switch to wimlib, for non solid ESD (fix wimgapi crash) - wincopy commandline volume mode can use filemode as fallback - vhd drives can be saved and loaded from ini file Link to comment Share on other sites More sharing options...
dimo70 Posted October 19, 2023 Share Posted October 19, 2023 (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 October 19, 2023 by dimo70 Link to comment Share on other sites More sharing options...
JFX Posted October 19, 2023 Author Share Posted October 19, 2023 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. 1 Link to comment Share on other sites More sharing options...
dimo70 Posted October 19, 2023 Share Posted October 19, 2023 (edited) I updated our helper NTHelper for WinNTSetup 5.3.3 Edited October 19, 2023 by dimo70 1 Link to comment Share on other sites More sharing options...
Sonic Posted October 21, 2023 Share Posted October 21, 2023 winnt setup not start if missing Tools\x64\wimlib.dll. A popup to inform would be nice. Link to comment Share on other sites More sharing options...
JFX Posted October 21, 2023 Author Share Posted October 21, 2023 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. Link to comment Share on other sites More sharing options...
Sonic Posted October 21, 2023 Share Posted October 21, 2023 not deleted , but updated manually my base folder... I like to check what files changed ... deleted the older wimlib but missing copy the new .... Link to comment Share on other sites More sharing options...
sharicov@gmail.com Posted October 21, 2023 Share Posted October 21, 2023 (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 October 21, 2023 by sharicov@gmail.com Link to comment Share on other sites More sharing options...
JFX Posted October 22, 2023 Author Share Posted October 22, 2023 (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 October 22, 2023 by JFX Link to comment Share on other sites More sharing options...
sharicov@gmail.com Posted October 23, 2023 Share Posted October 23, 2023 (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 October 23, 2023 by sharicov@gmail.com Link to comment Share on other sites More sharing options...
JFX Posted October 23, 2023 Author Share Posted October 23, 2023 (edited) Good, I will add a fallback for RunAsTI setting. About the crash, is there anything in windows eventlog? Edited October 23, 2023 by JFX Link to comment Share on other sites More sharing options...
sakatgg Posted October 24, 2023 Share Posted October 24, 2023 (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 Edited October 24, 2023 by sakatgg Link to comment Share on other sites More sharing options...
JFX Posted October 25, 2023 Author Share Posted October 25, 2023 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 Link to comment Share on other sites More sharing options...
sakatgg Posted October 25, 2023 Share Posted October 25, 2023 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. Link to comment Share on other sites More sharing options...
Antonino Posted October 26, 2023 Share Posted October 26, 2023 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). Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now