However, the lack of auto-updates gives us hope that the telemetry is really cut here, so Microsoft is “pulling the rubber” with the official registration process and the official auto-update of the new version of CMGE 2022-L. This is a user benefit, I hope. I don't see a problem to download the update myself from the Mickrosoft website.
Q: What does Unstaged Insider Preview ISO install? A: Only packages defined in Edition mum, and language pack. And it installs each Edition as defined by EditionMatrix.xml.
Yes, it works. IoT has 10 years of support and EnterpriseS (21H2) has 5 years of support, so IoT has the upper hand. However, I don't like IoT because Activation is only possible here(for IoT) as a "Digital License". I don't want and I won't have a "digital collar" from Microsoft. Such idea: I install EnterpriseG and do activation (offline) for 410 years. Then I do an EnterpriseG --> IoT edition change. Now IoT has no activation. Then I do an update for this “non-activated” IoT. Then I revert the IoT --> EnterpriseG edition, now I have 410 year activation again. This is interesting... If IoT has 10 years of support, then can I do this "Upgrade" for 10 years?
My two cents If you are really concerned about Telemetry better reconstruct an EnterpriseS and Activate with KMS(38) With EnterpriseS you can "AllowTelemetry" to "0" Security = no Windows diagnostic data is sent from your device. With EnterpriseG you can only "AllowTelemetry" to "1" Required diagnostic data = gathers a limited set of data that’s critical for understanding the device and its configuration. (How I) Disable Telemetry in Windows 10 Enterprise / Education / LTSC / Server (Offline) https://forums.mydigitallife.net/th...lemetry-repository.63874/page-66#post-1686849 (How I) Install Latest Cumulative updates (online) -- In this order Code: @echo off rem == add latest servicing stack update == dism /online /add-package:SSU-19041.1371-x64.cab /norestart rem == add latest cumulative update == dism /online /add-package:Windows10.0-KB5009543-x64.cab /norestart rem == add latest .NET framework 3.5 and 4.8 update == dism /online /add-package:Windows10.0-KB5008876-x64-NDP48.cab /norestart pause
CMGE update support period is decided by the contract between CMIT company and Microsoft. When CMGE reaches End of Service, Microsoft may take EnterpriseG off LCU. Your quick switch is good only while EnterpriseG is still supported. (It actually updates EnterpriseG, not ioTEnterpriseS.) Two ways to use Windows Update as long as IoTEnterpriseS; 1. Convert EnterpriseG to EnterpriseS and use IoTEnterpriseS. 2. Add EnterpriseS. (When EnterpriseG is not supported by LCU, Holographic and Dolby won't be updated. You can update them manually if they are in the LCU.)
This is a very interesting question... Has anyone done such comparisons, EnterpriseG vs EnterpriseS ? Ok, what benefits do you see in the CMGE_V2022-L.1345 [zh-CN] --> [en-US] rebuild instead of just using the original Windows 10 21H2 EnterpriseS [en-US] + your Registry change? Please don't say that 410 years of activation is an advantage.
Q: Is it OK to install UUP cab packages? A: No. Some of them have to be extracted to install correctly. Reminder: cab 100% installed is not equal to successfully installed. The update will prove it.
If it's about telemetry then setting "AllowTelemetry" to "0" is what separates Enterprise (LTSC), Education and Server from other SKUs With my script/s I have more control rather than rely on what CMGE and MS decides is Telemetry or not