JFX Posted March 28 Author Share Posted March 28 (edited) Yes, noticed there was a problem, should be fixed now. Edited April 2 by JFX Link to comment Share on other sites More sharing options...
suxichao Posted March 28 Share Posted March 28 1 hour ago, JFX said: Yes, noticed there was a problem, should be fixed now. WIMHost_1.2.0.0.zip 34.95 kB · 2 downloads I tried WimHost1.2.0.0, but still encountered the same problem as last time, which was when I deleted the winsxs.ini configuration file in the Default folder of MinWin and encountered an error of 0xc000005. As long as I restored winsxs.ini, there was no problem. This is strange, even if I downloaded the latest version of WinNTSetup from Mediafire and replaced the previous WimHost1.2.0.0, I still get this error. I don't know if Mr. JFX has a self use version of WinNTSetup that he can borrow me to test? Thank you, Mr. JFX, for your tireless answers these days. Thank you very much! Link to comment Share on other sites More sharing options...
JFX Posted March 28 Author Share Posted March 28 Well I can't reproduce it. Where can I download that exact ISO? Did you try with different source, maybe a clean MDSN version? Link to comment Share on other sites More sharing options...
suxichao Posted March 28 Share Posted March 28 (edited) 1 hour ago, JFX said: Well I can't reproduce it. Where can I download that exact ISO? Did you try with different source, maybe a clean MDSN version? Oh, I didn't try the MSDN image, but I just generated a new Win11 ISO using UUPDump and tested it again, and still have this error. It's really strange. I am very grateful to Mr. JFX for his continued attention to these issues, and I hope Mr. JFX has a happy day every day Edited March 28 by suxichao Link to comment Share on other sites More sharing options...
JFX Posted March 30 Author Share Posted March 30 Ok, could generate a crash under some WinPE environments. WIMHost_1.2.1.0.zip Link to comment Share on other sites More sharing options...
wuliyen Posted April 4 Share Posted April 4 On 3/31/2024 at 12:19 AM, JFX said: Ok, could generate a crash under some WinPE environments. WIMHost_1.2.1.0.zip 35.08 kB · 4 downloads WIMHost_1.2.1.0 The following MUI files were removed Required reservations \Windows\System32\zh-CN\dxgkrnl.sys.mui \Windows\System32\zh-CN\dxgmms2.sys.mui \Windows\System32\zh-CN\mpsdrv.sys.mui \Windows\System32\zh-CN\SMCCx.dll.mui \Windows\System32\zh-CN\UevAgentDriver.sys.mui Link to comment Share on other sites More sharing options...
JFX Posted April 5 Author Share Posted April 5 I guess system32 mui folder is a fallback location for it's subfolders. Added recursive scanning for mui candidates. WIMHost_1.2.3.0.zip Link to comment Share on other sites More sharing options...
wuliyen Posted April 5 Share Posted April 5 Some files are located in the WINSXS folder when installed by default, but the MUI files exist in the Languages folder. What should I do in this case? lpq.exe.mui、lpq.exe.mui。。。。 Link to comment Share on other sites More sharing options...
JFX Posted April 5 Author Share Posted April 5 1 hour ago, wuliyen said: Some files are located in the WINSXS folder when installed by default, but the MUI files exist in the Languages folder. What should I do in this case? I would ignore them. If there is no lpq.exe in system32 than that applications is no installed and does not need a .mui file. If it get's installed (by dism) later, it should copy the .mui, too. Link to comment Share on other sites More sharing options...
wimb Posted April 6 Share Posted April 6 (edited) In case booting from USB with PE is not available we can use Windows Shift Restart to arrive in Windows Recovery Environment. In WinRE blue menu Advanced Options we can use Command > notepad > File Open > Run as Admin WinNTSetup_x64.exe and Select Captured WIM file of Windows 10/11 x64 and use Setup for Apply in VHD e.g. Inject New System in VHD next to existing Windows. Thank you for making WinNTSetup v5.3.4 which is working quite well for many cases. Edited April 6 by wimb 1 Link to comment Share on other sites More sharing options...
Antonino Posted April 6 Share Posted April 6 (edited) jfyi, reboot.pro is back down again; woops, now it is back up again Edited April 7 by Antonino Link to comment Share on other sites More sharing options...
suxichao Posted April 9 Share Posted April 9 (edited) When WinNTSetup is releasing the same wim image, using WIMHost 1.2.1.0 will not produce errors, but using WIMHost 1.2.3.0 will prompt a "wimlib error 0x2: The WIM contains invalid compressed data" message. I don't know why this happens.... Do I need to replace my Windows PE? Edited April 9 by suxichao Link to comment Share on other sites More sharing options...
JFX Posted April 9 Author Share Posted April 9 That could happen if you update wimlib, the official version is no longer supported. Link to comment Share on other sites More sharing options...
freqout Posted April 16 Share Posted April 16 This is great. Wondering if this can be used to make the VHD bootable instead of actuing on my local boot partition, and if it can be scripted and completely automated from Powershell. Link to comment Share on other sites More sharing options...
JFX Posted April 17 Author Share Posted April 17 (edited) 10 hours ago, freqout said: This is great. Wondering if this can be used to make the VHD bootable instead of actuing on my local boot partition, and if it can be scripted and completely automated from Powershell. Yes, if you select a different boot drive, your local boot partition will not not be touched. For automation there are many command line options, see F1 - help. Edited April 17 by JFX 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