What Changed in Windows 11
What Windows 11 changed in a normal process list, and in the tools that check one.
- Normal Processes
Why It Matters
A baseline from another edition, build or set-up raises false alarms and misses real ones. Check what a machine runs before you compare it with any tree.
What Happens
Windows 10 reached the end of support on 14 Oct 2025, and 22H2 was its last version, so Windows 11 is the baseline to know, the picture of a clean machine you compare others with. Versions 24H2 and 25H2 take the same monthly updates, so their core trees should match. 26H1, preinstalled only on select new devices, is built on a different Windows core, so check what it shares before reusing a baseline.
Normal now depends on the set-up as much as the build. Credential Guard, on by default from 22H2 on eligible domain-joined Enterprise and Education devices, turns on virtualisation-based security and runs LsaIso.exe beside lsass.exe. Added LSA protection, on by default only on new, enterprise-joined installs that can run hypervisor-protected code integrity (HVCI), makes lsass.exe a protected process.
WMIC is removed from every supported Windows 11 version by the August and September 2026 preview updates, though WMI itself stays. Windows PowerShell 2.0 is gone from 24H2, so a script that asks for it runs in 5.1. From 22H2, Windows Terminal is the default for command-line programs unless someone chose another terminal.
Elevation, running a program with administrator rights, looks different too. Sudo for Windows, from 24H2, opens an elevated command in a new window by default, and in its inline and input-closed modes links the unelevated sudo.exe to a second, elevated one. Administrator protection, off by default but on in the October 2026 Windows security baseline, gives each elevated program a token (the record of who a process runs as) from a hidden, system-generated account.
Two older changes still shift what you compare against. Fast Startup keeps session 0 from the last full boot, so its processes can predate the sign-in by days, and above 3.5 GB of RAM most services run in an svchost.exe of their own. For the tools, built-in Sysmon has been an optional feature since February 2026, and Volatility 3 handles Windows 11 images better from version 2.28.0, so use its current release, 2.28.2.
What Changed, and What It Does to a Baseline
Each row is a change that alters what a clean machine looks like, or what your tools can read. The last column says what to expect on a machine that has it, so you do not flag a normal change as a finding, or miss a finding because a baseline from another build hid it.
| Change | Since | What It Does to a Baseline |
|---|---|---|
| Credential Guard on by default for Enterprise and Education devices that are domain joined, hardware ready and not turned off before | Windows 11 version 22H2 | LsaIso.exe runs beside lsass.exe. WinInit event 13 in the System log says it started, and event 15 says it was set but the secure kernel did not run. |
| Added LSA protection on by default for new installs that are enterprise joined and can run HVCI | Windows 11 version 22H2 | lsass.exe runs as a protected process, which WinInit event 12 in the System log confirms. An upgraded machine does not get it by default. |
| Audit mode for added LSA protection | Windows 11 version 22H2 | Events 3065 and 3066 in Microsoft-Windows-Code |
| Windows Terminal the default terminal (Terminal 1.15 or later, keeping an earlier choice) | Windows 11 version 22H2 | Command-line programs open in Windows |
| WMIC turned off by default, still a feature on demand | Windows 11 versions 23H2 and 24H2 | wmic.exe can still be added back on these versions until the removal below. |
| WMIC removed | The August 2026 preview update for 24H2 and 25H2, and September 2026 for 26H1 | wmic.exe is gone from an updated machine, while WMI and WmiPrvSE.exe remain. |
| VBScript a feature on demand, still on by default | Windows 11 version 24H2 | wscript.exe and cscript.exe still run VBScript. Microsoft plans to turn it off by default around 2027. |
| Windows PowerShell 2.0 removed | Windows 11 version 24H2, from August 2025 | A script or task that asks for version 2 runs in Windows PowerShell 5.1 instead. |
| Sudo for Windows, off until turned on in Settings | Windows 11 version 24H2 | By default the command opens in a new elevated window. In the inline and input-closed modes an unelevated sudo.exe links to a second, elevated one. |
| Administrator protection, off by default and on with the October 2026 Windows security baseline | KB5120998 | Elevated programs run with a token from a hidden, system-generated account, not the person's own. Event 15031 from the Microsoft-Windows-LUA event tracing (ETW) provider records each approval. |
| Built-in Sysmon, an optional feature that is off by default | KB5077241, February 2026 | Sysmon events can come from the built-in feature as well as the Sysinternals download. Microsoft says to uninstall the download before turning the feature on. |
| Services split into their own svchost.exe above 3.5 GB of RAM | Windows 10 version 1703 | Many more svchost.exe copies, though some services stay grouped (Svc |
| Fast Startup on by default | Windows 8 | Choosing Shut down hibernates the kernel session, so session 0 keeps the start times of the last full boot. Restart, or Shutdown.exe, gives a full boot. |
| Better Windows 11 support in Volatility 3 | Volatility 3 version 2.28.0 | Version 2.27.0 had a known issue with some Windows 11 images, so use the current stable release, 2.28.2. |
Red Flags
Each sign below links to the page that shows how to confirm it.
- Normal under Administrator protection, where elevated programs run as a hidden, system-generated account.Wrong Account
- Normal with Sudo for Windows, whose inline and input-closed modes link an unelevated sudo.exe to an elevated one.Wrong Parent
- On Windows 11 with the 2026 WMIC removal installed, a running wmic.exe came from somewhere else.Abused Built-In and Admin Tools
- Normal with Fast Startup, where session 0 keeps the start times of the last full boot, so judge them against it.Unusual Start Time
What Records It
Each record names its log and what must be switched on to get it.
| Record and Where It Lands | What to Read | How to Turn It On |
|---|---|---|
13 Credential Guard (LsaIso.exe) was started and will protect LSA credentials (opens in a new tab)SystemIt is written on a computer running Credential Guard. Its source is WinInit. | Credential Guard started, so expect LsaIso.exe beside lsass.exe on this machine. | On by default |
15 Credential Guard (LsaIso.exe) is configured but the secure kernel isn't running; continuing without Credential Guard (opens in a new tab)SystemIt is written on a computer set to run Credential Guard whose secure kernel did not start. Its source is WinInit. | Credential Guard was set but the secure kernel did not run, so expect no LsaIso.exe, whatever the policy says. | On by default |
12 LSASS.exe was started as a protected process with level: 4 (opens in a new tab)SystemIt is written on a computer whose lsass.exe started as a protected process. Its source is WinInit. | lsass.exe started as a protected process, so tools that are not protected cannot open its memory. | On by default |
3065 A code integrity check determines that a process, usually LSASS.exe, attempts to load a driver that doesn't meet the security requirements for shared sections. However, due to the system policy currently set, the image is allowed to load (opens in a new tab)Microsoft-Windows-CodeIntegrity/OperationalIt is written on any computer that audits LSA protection. That audit is on by default from Windows 11 version 22H2. | In audit mode, on by default from 22H2, an LSA plug-in or driver that would fail the shared section rules.Loaded DLLs shows how to read it. | Turn on audit mode for added LSA protection, which allows the load and logs it. |
3066 A code integrity check determines that a process, usually LSASS.exe, attempts to load a driver that doesn't meet the Microsoft signing level requirements. However, due to the system policy currently set, the image is allowed to load (opens in a new tab)Microsoft-Windows-CodeIntegrity/OperationalIt is written on any computer that audits LSA protection. That audit is on by default from Windows 11 version 22H2. | In audit mode, an LSA plug-in or driver that would fail the signing level rules.Loaded DLLs shows how to read it. | Turn on audit mode for added LSA protection, which allows the load and logs it. |
15031 Elevation Approved (opens in a new tab)Microsoft-Windows-LUA, an event tracing provider rather than an event logIt is written on Windows 11 computers with Administrator protection on. | An elevation approved under Administrator protection, after which the program runs with the hidden account token. | Turn on Administrator protection, and run a trace session for the Microsoft-Windows-LUA provider. |
Sources
- Microsoft Learn: Windows 10 Home and Pro lifecycle (opens in a new tab)
- Microsoft Learn: Windows 11, version 26H1 (opens in a new tab)
- Microsoft Support: February 24, 2026, KB5077241 (OS Builds 26200.7922 and 26100.7922) Preview (opens in a new tab)
- Microsoft Learn: Credential Guard overview (opens in a new tab)
- Microsoft Learn: Configure Credential Guard (opens in a new tab)
- Microsoft Learn: Configure added LSA protection (opens in a new tab)
- Windows Command Line blog: Windows Terminal is now the Default in Windows 11 (opens in a new tab)
- GitHub: microsoft/terminal (opens in a new tab)
- Microsoft Support: Windows Management Instrumentation Command-line (WMIC) removal from Windows (opens in a new tab)
- Microsoft Learn: Deprecated features in the Windows client (opens in a new tab)
- Windows IT Pro Blog: VBScript deprecation: Timelines and next steps (opens in a new tab)
- Microsoft Support: PowerShell 2.0 removal from Windows (opens in a new tab)
- Microsoft Learn: Sudo for Windows (opens in a new tab)
- Microsoft Learn: Administrator protection (opens in a new tab)
- Microsoft Learn: Sysmon (opens in a new tab)
- Microsoft Learn: Service host grouping in Windows 10 (opens in a new tab)
- Microsoft Learn: Fast startup causes hibernation or shutdown to fail in Windows 10 or Windows 8.1 (opens in a new tab)
- Building Windows 8 blog: Delivering fast boot times in Windows 8 (opens in a new tab)
- GitHub: volatilityfoundation/volatility3 releases (opens in a new tab)