In fairness, your Know-How as is presented in this topic does not help many outside the handful inner circle that have to follow the thread like the CCP. You constantly edit and nuke posts as someone scared for dear life if the CCP finds out or something, then you taunt users with legitimate questions as if it's their fault for not paying attention to the overwhelming volume of edited Qs without As. Oh and the "haters" and the "copy-cats" - you don't like them much. Doh? That's what happens when you post things your way - it's nerve-racking. Compare that to how abbodi1406 does it, from the ground up user-oriented with clear topics, aggregated links in his signature and etc - letting the knowledge flow, not scatter it. He even went the trouble to provide a clear, complete and working guide for 2021 LTSC in letter and spirit of the original post by whatever127. Is that really to much to ask for an overview post of what you've been cooking over the years, maybe a link to it in your signature?
Missed it I'm just an old NSA guy, not as speedy as the new blood Hopefully you've taken it as intended, constructive criticism.
CMGE_V2022-L.1345 Fatal error after sfc /scannow Is this error due to license.rtf file, same as CMGE_V2020-L.1207 ? Windows\System32\zh-CN\Licenses\Volume\EnterpriseG\license.rtf If so, then where can I get the correct license.rtf file for CMGE_V2022-L.1345 ? P.S. I don't look at CBS.log because I'm still testing the Chinese version, but I don't know Chinese at all
No. The issue is the same as 17763 caused by those 4 Wallpapers folders at WinSxS. It seemed that I had asked you about this. No reply from you, then I tested it myself. https://forums.mydigitallife.net/th...struction-project.80939/page-324#post-1720106 But, you'd better test it again with original Wallpapers. Becuase the license.rtf is also OEM.
It's OK to test in en-US, because those packages being added to system are original. Only non-original system packages will cause integrity violations issue.
Sure, I could try getting EnterpriseG ru-RU even with a working SPP. And yes, I stopped bothering with unstaged stuff, mainly due to my laziness.
Aside that the obvious license switch, the way could be "If the mountain will not come to Mahomet, Mahomet will go to the mountain". I mean shouldn't be that hard to take all the MUIs in one language say ru-RU and replace the string on their header with zh-CN to fool the system (MUIs are not signed dlls). But I have little idea on how to do a batch editing using a resource hacker (or hex editor), maybe @abbodi1406 maybe @BAU ?
That might be true, but I don't think the passive translation strings are in effect - that's just for display. There are other values in the main dll with probably a language code that gets checked. edit: Applegame12345's approach might work. tho all these are "improper" hacks