sakatgg Posted February 10 Share Posted February 10 (edited) On 2/8/2024 at 12:44 PM, JFX said: I will release an update, maybe next week. Key support ! for WinSxS.ini from this post https://msfn.org/board/topic/149612-winntsetup-v533b/page/193/#comment-1256786 in the new version planned? Tested on Server 2019 build - works great, Will the new version support Compact LZX for Server 2019? Edited February 10 by sakatgg Link to comment Share on other sites More sharing options...
JFX Posted February 10 Author Share Posted February 10 Good you remind me about CompactOS and Server. It works so I'll remove this limitation. ! for WinSxS.ini will be supported. I think about making this ini optional. That should make things easier for people that just want to remove some files. Link to comment Share on other sites More sharing options...
Antonino Posted February 10 Share Posted February 10 On 12/16/2023 at 4:16 AM, wuliyen said: new Tools\x64\WIMHost.exe failed to load offine registry! error loading:\windows\system32\config\system 0x3 error loading:\windows\system32\config\software 0x3 it sometimes does the same to me, I wonder what files or directories should not be deleted to avoid this from happening Link to comment Share on other sites More sharing options...
JFX Posted February 10 Author Share Posted February 10 \windows\system32\config should never be deleted. If it happens without you using telling it to do, then it's a bug. 1 Link to comment Share on other sites More sharing options...
Antonino Posted February 10 Share Posted February 10 (edited) u referring to the whole folder and subfolders and files I presume. me I have tried !ing all those entries wherever I found I had them \ed, but there is still something that prevents winntsetup from loading system 0x3 and software 0x3. what else coud it be? oh btw, there is another one that cannot derive from users\default\ntuser.dat, so I guess I will have to revise the list and ! the \users\default entry as well. btw, no issues instead if I delete some files in the config after it has loaded the registry, on an ex-post-facto basis. Edited March 20 by Antonino Link to comment Share on other sites More sharing options...
JFX Posted February 13 Author Share Posted February 13 WinNTSetup 5.3.4 - fixed problems starting as TrustedInstaller on some machines - fixed rare heap corruption - fixed CompactOS was ignored for Windows Server versions - Removed offreg.dll (will be downloaded for older Windows) - MinWin uses build number from registry rather than WIM - MinWin removed hard coded pathes - MinWin WinSxS.ini - can use "!" to avoid old components removal - MinWin WinSxS.ini can be deleted - MinWin fixed wincopy mode bug 3 Link to comment Share on other sites More sharing options...
Feudor888 Posted February 14 Share Posted February 14 Thank you! 1 Link to comment Share on other sites More sharing options...
jaclaz Posted February 14 Share Posted February 14 @JFX There is an user of your nice WINNTSETUP that for *some reasons* (I will also post in site and forum issues) cannot register here on MSFN. He posted on reboot.pro, here: http://reboot.pro/index.php?showtopic=22827 what he asks for seems to me reasonable, maybe you can suggest a way (or officially exclude there is one) to directly install on a VHD. jaclaz Link to comment Share on other sites More sharing options...
JFX Posted February 14 Author Share Posted February 14 I would say steve6375 has already given the right answer. WinNTSetup only applies the WIM to the VHD and create boot files. The image is still in sysprep phase and therefor will try to "specialize" the BCD store on first boot. If he immediately boot that VHD with Ventoy it will cause that error. I don't know how Ventoy boot it, but i guess it uses a virtual boot drive like NTBOOT. And that can't be seen later in the boot process. For the "hidden menu" he will need to use newer version. 1 Link to comment Share on other sites More sharing options...
wuliyen Posted February 15 Share Posted February 15 MINWIN Function Description Simplified Chinese ReadMechs.txt Link to comment Share on other sites More sharing options...
JFX Posted February 16 Author Share Posted February 16 Thanks, added and also re-added offreg.dll. Link to comment Share on other sites More sharing options...
dimo70 Posted February 17 Share Posted February 17 NTHelper.zip 1 Link to comment Share on other sites More sharing options...
wuliyen Posted February 17 Share Posted February 17 Single file runtime version，5.34 error，5.33 normal Link to comment Share on other sites More sharing options...
JFX Posted February 18 Author Share Posted February 18 That path is invalid, some API's will misunderstand "..\Tools" to be the parent directory. I doubt you could even open that folder in windows explorer. Link to comment Share on other sites More sharing options...
sharicov@gmail.com Posted February 18 Share Posted February 18 (edited) Server 2022 getting following error with 5.3.4: "The code execution cannot proceed because BCDBoot.exe was not found". 5.3.3b works perfectly well on the same PC. Edited February 18 by sharicov@gmail.com 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