[DISCUSSION] Windows 10 Enterprise/IoT Enterprise (N) LTSC 2021

do you want to permanently remove Windows defender packages from your running OS or just want to toggle between enabled & disabled whenever needed ?

 

Likely need to add some package if this functionality is not already hidden somewhere in LSC 2021.
@abbodi1406

 

toggle on / off when I want

 

toggledefender by bau works perfectly fine

 

First, disable TamperProtection:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Features]
"TamperProtection"=dword:00000004
"TamperProtectionSource"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender]
"DisableAntiSpyware"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection]
"DisableBehaviorMonitoring"=dword:00000001
"DisableOnAccessProtection"=dword:00000001
"DisableScanOnRealtimeEnable"=dword:00000001

 

You need to login to view this posts content.

 

Here is the topic about Edge - turning on - shutdown - deletion.
Read the last few sides.
- https://forums.mydigitallife.net/threads/microsoft-edge.79237/

These are online ways - because this is what he asked.

 

by bau / aveyo works perfectly plus sordum defender tool also work perfectly plus andyfull latest updated defender tool also work perfecty too . decision is always yours & suggestion is always ours.

 

You need to login to view this posts content.

 

Can uninstall LTSC 2019 product then inplace upgrade then enter LTSC 2021 product key?

 

I mean can I uninstall LTSC 2019 product key then inplace upgrade then enter LTSC 2021 product key?

 

You need to login to view this posts content.

 

Just installed "en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f" over the top of LTSC 1809. After reading A LOT of posts I was expecting I would need to do some tweaking to get up and running again, not sure what I did "wrong" but I didnt even have to re-activate. Most of the privacy settings in O&O and PrivacyRepair were still enabled and Defender was still disabled as well as Windows Firewall. Default programs didn"t change either. One thing I do notice is that ioT isn't enabled, winver reports the version as 21H2 (OS Build 1944.1348) so assuming that KMS 8.4 that I had enabled pre update may have something to do with that. Should I leave as is or update activation with KMS_VL_ALL? My Office 2019 install was unaffected.

 

IOT iso has normal LTSC and IOT sku indexes. If you were on LTSC already, it upgraded to LTSC index. You could technically change the key to the IOT key and activate with the luzeadev tool still. AFAIK the only difference between the skus is the CBS package regarding the activation. LTSC allows you to use many different activation methods and keys. I'm unsure about IOT sku and changing keys.

 

Thanks for the reply. Nah I wont bother trying to change to IOT. So I should be good leaving the 1809 KMS 8.4 activation in place? Asking because I had a different version "go bad" on me a few years ago, server couldn't be found, so updated to 8.4 and been good since. What about the "SppExtComObjHook.dll" requirement for auto activation? Will the KMS 8.4 method work to auto update?

Thanks

 

Latest KMSVLALL should work just fine. I believe luzeadev also handles the latest kms method. Most people prefer the HWID method as you don't have to mess with activators after that. It just auto-detects your hw and auto-reactivates. But you would need to swap your key to the IOT key for that as LTSC currently doesn't allow it.

 

Run your own kms server in a 5mb app in any android phone, no need to install anything on any system & you can carry this kms server in your pocket.
https://forums.mydigitallife.net/threads/kisskms-2-8-0-kms-server-app-android.72455/
@murphy78