xinso does not use 10240 and has no idea about that. To my best knowledge, xinso usually captures\expands\studies whole system to find it out. BTW. 1. Thank you for InternalBuildPackage-ServicingStack-OneCore-InstallOptions-Package~31bf3856ad364e35~amd64~~10.0.10586.0. 2. I don't have 10586.0 Container OS to test it. If convenient, could you please provide 26100.1 one? If not convenient, please never mind.
Anything to do today? New or Old. Old, to improve. Otherwise it'll get corrupt. New, to learn. Otherwise it'll get outdated. Corruption is the most terrible to everything.
Error SXS Unvouched component Microsoft-Windows-FileHistory-UI.Resources, version 10.0.25398.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35} by \??\C:\Users\Administrator\Downloads\mucs\mount\Windows\CbsTemp\1952_82166640\Microsoft-Windows-Client-Features-Package01~31bf3856ad364e35~amd64~en-US~10.0.25398.2274.cat
What did Microsoft change in the latest 25398 update to break it? The cert or? If we generate new .cat will the update install? Any way to bypass?
not only latest update, with .2274/6 same situation let's try bypass for .2207 is https://forums.mydigitallife.net/th...s-reconstructions.88605/page-155#post-1894823, but it's not working for .2274/6 and .2330
I just tried my best to share my experience. For anyone. Now that it had brought hurt to you. I am sorry. I will stop such posts forever.
No worry. You don't have to forgive me. But I still have to say sorry. (Let's call it an end. Thanks.)
1. xinso did share updated 10240 Starter in this thread and the old one. 2. 10586 package come from repair content packages, which 26100 doesn't have.
zhanglin. Long time no see. Let me tell you one thing. Yesterday, I tried to reconstruct WinVOS with gailium119's assistance. The image won't boot to Dos prompt even though the installed packages are the same as official image.