@xinso I just read the code you #13471 shared. I didn’t read it in detail before #13426. #13472 Modded_CU_Package.cmd names the package versions that need to be modified as the version number of the CU package. I will change it later when I get home. Corresponds to the version number of Professional, sorry Spoiler: Original post in Chinese @xinso, 我刚看了你#13471分享的代码,之前#13426我看得不够详细, #13472 Modded_CU_Package.cmd 把需要修改的包版号本统一命名为 CU 包的版本号,晚点我回到家后再修改为对应 Professional 的版本号,抱歉
Try to make what you wish come true is more important. Any working way is good way. Don't neglect any. You may need it someday.
He is very friendly and intelligent... And modest. I don't ask him\her, he\she tried his\her best for me when he\she saw my suffering about my problem.
Do repair content packages exist for each build? For example I tried to get them for 10240.16384, however the only thing I get is 0x800f081f error. @pivotman319
I'm stuck at SSU. My DOS command expand.exe failed to extract SSU folders. It was fine in the past and is fine for other builds. BTW, The official SSUs and CUs do not support Non-Professional. i.e. It needs customization for other Client Editions.
I didn't see this post, sorry. What do you mean by "customized"? To me, customization is "Rearrangement" as Microsoft does different arrangement to different editions or packages.
Modded_CU_Package.cmd 202311231012 Add detect %TP% files if or not EXIST Professional version in %TU_LCU% , if EXIST set LVER_N=Professional version MSU_to_esd_and_Modded_CU_202311231012.rar SHA1: 3f8975c7e80680b2f02f2d4fe899a2515c022ef0 pixeldrain.com/u/8QptKGu5 [Credits] @xinso, gailium119, abbodi1406