Q: How do you deduce the last 16 characters in manifest/assembly name? I'm trying to use @iamaHUN's 19041.1 licenses for EnterpriseS(N)Eval, but it's kind of painful to use DISM logs just to check what 20348 wants to accept.
? I have seen some using 17763 - It's difficult to download this 20348.1 client test package English version Please post on an accessible link or cloud189
FACT: Starter(N)Edition.xml and default product policy need to be modified for 20348 because 15063 is too old Q: Does modifying default product policy work for win+x in windows 11?
@gallium119 - the structure is perfect for client mode Get some rest man, I know what you are passing through The challenge lies ahead for the upgrades - I have spent the last 4 years of my life trying to figure this out
I checked LTSC only. Missing these packages: Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseSEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1 and Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseSNEval-Eval-Package~31bf3856ad364e35~amd64~~10.0.20348.1 Evaluation, System will load this Eval package to install Evaluation Key. If missing, it won't activate after Rearm. Then? The user will ask you how to activate it after Rearm.
1. Activateable by tsforge 2. These packages are NOT in system packages It should be possible to directly modify amd64_microsoft-windows-s..prisesneval-default_31bf3856ad364e35_10.0.20348.1_none_07c610995a4ceb92 and amd64_microsoft-windows-s..rpriseseval-default_31bf3856ad364e35_10.0.20348.1_none_9ef25675429eaaaa to change default key to eval key Spoiler Whatever, this is not system package, doesn't mean that I get the system package structure wrong Can you download and check what is wrong with the structure?
Oh, too late. For my new "Neutral", I'd deleted all my "Reconstruction" scripts. And I don't redo 25398 and other AC builds. Sorry.