Ｓｅｃ Ｎｏｔｅ

- Activating Windows using HWID and KMS methods;
- Disabling Windows Defender, SmartScreen, Antimalware, VBS, and UAC;
- Disabling/pausing Windows updates and removing temporary update files;
- Disabling unused and unnecessary system services;
- Disabling keyloggers and telemetry for Windows, NVIDIA, and Intel;
- Disabling services and events related to the collection of user data;
- Disabling data collection tasks in the Windows Task Scheduler;
- Disabling unnecessary network protocols: Teredo, ISATAP, and IPv6;
- Disabling built-in Windows diagnostic tools and disk defragmentation;
- Disabling personalized ads and system banners in Windows, including SCOOBE;
- Disabling system notifications, recommendations, and tips in Windows;
- Blocking Microsoft's shadow domains that collect data via hosts and firewall;
- Uninstalling OneDrive and Microsoft Edge along with clearing all associated data and WebView2;
- Removing standard pre-installed UWP apps in Windows 10/11;
- Removing and disabling AI assistants: Cortana, Copilot, and Recall;
- Customizing the interface: changing themes, window settings, taskbar layout, and icons;
- Configuring keyboard and mouse settings: disabling key filtering, sticky keys, and pointer acceleration;
- Adjusting Windows settings and applying the ultimate performance power plan;
- Adjusting power settings for Realtek High Definition Audio drivers to fix sound delay;
- Viewing the hardware configuration and monitoring system components;
- Compressing and decompressing files and directories using NTFS to save space;
- Clearing RAM, temporary files, icon caches, and securely deleting the Windows.old folder;
- Executing custom scripts (.ps1, .cmd, .bat, .reg) with TrustedInstaller privileges.

There are a lot of places in OneDrive and .NET stuff, also browsers but they have some protection...

Kernullist published his Obsidian research notes.

Authored by dbgman

Author
Matt Nelson

Let me keep it short… use uncommon stuff for static

(here is my conference ┐⁠(⁠ ⁠∵⁠ ⁠)⁠┌)
chain things smart to get past behavior detection.

TL;DR: Two command injection vulnerabilities exist in the Windows Explorer “Open PowerShell window here” context menu due to improper quoting and command injection through user-controlled folder paths. By creating folders with crafted names (e.g., folder; calc), an attacker can trigger arbitrary PowerShell command execution when a user uses Shift + Right-Click → Open PowerShell window here. One variant affects modern Windows 11 builds, while another existed since Windows 10 1703 (2017).

Focus is on real detection primitives like:
PsSetCreateProcessNotifyRoutine(Ex) for process lifecycle monitoring

PsSetLoadImageNotifyRoutine for image/DLL tracking

ObRegisterCallbacks for process/thread handle filtering

kernel → user-mode communication via IOCTL + agent design