According to my experience is not mandatory to start from EN-US image, just use the image in your language and skip the language pack installation
Yes and no I mean there is a difference between server and client, but no difference between LTSC/Pro/Enteprise and so on. Yepp. Perhaps 17763 is the worst windows version to use it (the best are 14393 and 1904x)
No. I am afraid that 19041.1149 Certificates Product policy won't support remotefx gpu, because you said it works as of 19041.868. If yes with 17763 Certificates, I rather use 17763 Certificates for the feature, and the system is fully 19041.868. OK. You test 19041.868 firstly.
Not sure. I tested the real LTSC 19044.1288 with Hyper-V and RemoteFX removed and re-added from 19041.868 and it works (not rock solid but it works). So, I guess, the policies are not a problem
You just look, no need to reply. 1. OEM key for HWID activation. 2. Target Feature update version set to 2004. 3. winre is also updated to 19041.868.
To be clear MS blocked the feature via driver and executable modifications For example until .868 Synth3dVsc.sys is 66KB Synth3dVsp.sys is 105KB After .868 they are both 7kb So why block via policy something that doesn't work anyway?
Server 2022 (20348) and 1904x/22xxx do support RemoteFX GPU - if it is installed as upgrade on system where it was used. You can add new VMs. For fresh systems DDA is recommended. GPU-part for newer systems
I tried creating a vanilla LTSC, but was unsuccessful as noted here, so I tried your create.cmd with the 1,2,3 XML you said to use, but I get the same error (Error: 3) I did using the XML files posted by MSMG. I did export (index 2) and used the Pro install.wim as input for the LTSC creation. edit Oh s**t, I somehow ended up using an old download from @huynhlam2 and did not realize there was a new one. EnterpriseS_x64_19041.1_en-US.zip 1642667 2021-11-21 (old) EnterpriseS_x64_19041.1_en-US.7z 1202522 2021-11-27 (new) This time I got further, but the EnterpriseS.log shows an error
This daily OS is my very first 19041.1 Enterprise LTSC, which has repairable integrity violations. Now, being updated to date with a row of LCUs by Windows Update, no more.
@balanadi B: its old build with mixed 19041.x + 17763.1 packages. So dont use this A: its completely EnterpriseS 19041.1 (all packages from 19041.x). And use this with the updated fix for 1.xml 2.xml 3.xml (Option 1 or 2 - work same): https://forums.mydigitallife.net/th...struction-project.80939/page-283#post-1708613
Code: 1.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" /> </package> </servicing> </unattend> 2.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> 3.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.21" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="1\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum" /> </package> </servicing> </unattend> 4.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> Better method fix Windows-Defender-AM-Default-Definitions-Package and remove Package_for_RollupFix-Package-amd64-19041.21.1.1.cab.