712 didn't install copilot on my system, but I have had Edge completely removed from the beginning. Since it used the webview component, this might be a way to avoid it.
It's only shady if you can't read the code and understand what it does. I've never seen anything questionable in the massgravel scripts. The KMS38 exploit is fairly extensively documented here on MDL. It just tricks your system to setting the time-out date for year 2038 instead of 180 days. (At least I think that's the way it works) There's also KMS_VL_ALL method (I'm not sure if it has been updated for this OS yet) that will just re-activate every time you reboot and do 180 days. That uses the dll hook method. These scripts also have the benefit of setting the kms block reg key so that it doesn't try to phone home with MS and let them know that your activation is not from a legit server. I've never actually seen MS do anything about the fake KMS activations. If you get your activation blocked, let us know. It would be interesting to hear about. From what I can tell MS is just doing this to learn where the non-legit activations happen.
Put the AI component under "deprovisioned," and it never installs. Spoiler: image + reg Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned\MicrosoftWindows.Client.AIX_cw5n1h2txyewy] Other precautions to consider: Spoiler: reg Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsAI] "DisableAIDataAnalysis"=dword:00000001 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsCopilot] "TurnOffWindowsCopilot"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "AllowTemporaryEnterpriseFeatureControl"=dword:00000000 ;; 1. optional, idk for sure if they contribute here but a default mdm is microsoft itself [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx] "MdmHosts"=- ;; 2. see 1 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\MDM] "DisableRegistration"=dword:00000001 "AutoEnrollMDM"=dword:00000000
Some problems found 1- bold text & after selected it's becoming normal 2- click on cmd script, have 1-2 sec delay
It is an officially released ISO, atm only available in en-US, later this year MSFT will release them on MVS/VLSC in all languages and with updates integrated.
read this https://forums.mydigitallife.net/th...-2024-24h2-26100-x.88280/page-18#post-1837794 FYI Windows Store Pack updated ( LTSC 2024 and LTSC 2021 ) @Enthousiast https://forums.mydigitallife.net/th...ises-sku-ltsb-ltsc.70741/page-63#post-1837890
Did i ever show interest in store packs? wsreset -i works fine for me and i don't even do that on my installs.
I just manually install AppInstaller and use Winget in PowerShell (eventually in Terminal once I install it via Winget). No way I'm installing the MS Store. LOL
I can't seem to install W11 IoT Enterprise LTSC over W11 IoT Enterprise while keeping personal apps and settings because it is a "different" edition. Is there a way to bypass that check? Trying to move from 22631 to 26100
I actually tried an old trick done back on Windows 10 in registry. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion -> REG_SZ "EditionID" and setting it to IoTEnterpriseS when my old value is IoTEnterprise and it was able to do an in place install retaining all apps. All good now!