[DISCUSSION] Windows 11 Enterprise/IoT Enterprise (N) LTSC 2024 (24H2 / 26100.x)

Discussion in 'Windows 11' started by Enthousiast, Apr 26, 2024.

  1. °ツ

    °ツ MDL Addicted

    Jun 8, 2014
    921
    1,208
    30
    I have tried LTSC 2024 several times but always found it slow/sluggish compared to LTSC 2021 but I never thought about that it's because of Windows Defender. Yesterday I installed .8655 and disabled Defender using WinNTSetup and now it's fast. I had issues with 25H2 and 26H1 so hopefully this one will be stable.

    I also noticed that there is improved dark mode, file dialog is now dark and when I click to add new tab in File Explorer there is no white background appearing. So while LTSC does not receive feature updates it does receive improvements like this, maybe the improved dark mode is not considered a feature update. This is nice.
     
  2. scaramonga

    scaramonga MDL Senior Member

    Oct 27, 2012
    443
    275
    10
    Yeah, one if the first things I remove is Defender. It's a system hog.
     
  3. Atari800XL

    Atari800XL MDL Expert

    Apr 3, 2011
    1,000
    1,758
    60
    ...and WinNTSetup, by "JFX", disables it in a very clean and transparent way.
    I can recommend it
     
  4. scaramonga

    scaramonga MDL Senior Member

    Oct 27, 2012
    443
    275
    10
    #3724 scaramonga, Jun 29, 2026 at 23:23
    Last edited: Jun 30, 2026 at 00:08
    I remove that garbage @ image level, long before first boot, like most of the crap ;)


    FYI

    CrossDeviceResume.exe (RESUME) is the latest 'irritant' that plagues LTSC, along with all 24/25/26H+ variants.

    This thing persists, and although it don't run all the time, it pops in and out when it feels like it, and there is no way to prevent it from doing so. Renaming, and/or, replacing with a dummy file etc., will give one an error if done so, likewise, with .reg fixes. Us over @ NTLite have been on this for a while, and, unfortunately, MS have us beaten on this one. It hogs the CPU needlessly when running, so unless you need it?, it's best got rid of.

    The bad news, it can't be got rid of. The good news, if stopped upon boot, it won't return again, until a shutdown or restart (ATM, coz knowing MS, they will change this).

    So the solution (ATM) is to create a 'scheduled task' to kill it upon login, which works rather well indeed :)

    Not ideal, but at least one can reboot knowing it's going to get nuked at start.

    PowerShell (Admin)

    schtasks /create /sc OnLogon /delay 0000:03 /tn "\Microsoft\Windows\Shell\Kill CrossDeviceResume.exe" /tr "taskkill /im CrossDeviceResume.exe /f" /ru SYSTEM /f

    If your like me?, and have 'Process Lasso Pro', then I have it set to kill whenever it decides to awake, but not necessary, as the above set task suffices, as once initially killed (and believe me, I have monitored ;)), it won't return again until system reboots or logs off.

    Your welcome :)