startup process

Winsage
January 12, 2026
A new tool named EDRStartupHinder was unveiled on January 11, 2026, which allows attackers to inhibit the launch of antivirus and endpoint detection and response (EDR) solutions during the Windows startup process. Developed by security researcher Two Seven One Three, it targets Windows Defender and various commercial security products on Windows 11 25H2 systems by redirecting essential system DLLs during boot using the Windows Bindlink API and Protected Process Light (PPL) security mechanisms. The tool employs a four-step attack chain that includes creating a malicious service with higher priority than the targeted security services, redirecting critical DLLs to attacker-controlled locations, and modifying a byte in the PE header of the DLLs to cause PPL-protected processes to refuse loading them. This results in the termination of the security software. EDRStartupHinder has been tested successfully against Windows Defender and other unnamed antivirus products, demonstrating its effectiveness in preventing these security solutions from launching. The source code for EDRStartupHinder is publicly available on GitHub, raising concerns about its potential misuse. Security teams are advised to monitor for Bindlink activity, unauthorized service creation, and registry modifications related to service groups and startup configurations to detect this attack vector. Microsoft has not yet issued any statements regarding patches or mitigations for this technique.
Winsage
November 5, 2025
Microsoft has acknowledged an issue affecting Windows 11 versions 24H2 and 25H2, as well as Windows 10 version 22H2, where users of specific Intel-based devices encounter unexpected BitLocker recovery screens after installing updates released on or after October 14, 2025. This problem is linked to devices with Connected Standby technology, which affects the startup process but does not indicate a continuous encryption issue. Entering the recovery key resolves the prompt, and subsequent boots do not trigger additional prompts. Microsoft has activated a Known Issue Rollback (KIR) to address the issue without requiring users to uninstall previous patches. Server editions of Windows are unaffected, and users are advised to monitor the Windows Release Health dashboard for updates.
Winsage
August 12, 2025
Maintaining a computer's performance requires regular software upkeep in addition to physical care. An annual deep clean is advisable, with more frequent maintenance being beneficial. 1. Uninstall unused applications using the built-in Settings app or a tool like BCUninstaller, which can bulk uninstall and identify leftover files. 2. Run debloat scripts, such as Chris Titus Tech's Windows Utility, to remove bloatware and manage privacy settings. 3. Disable unnecessary startup apps through the Task Manager to optimize boot times. 4. Check for driver updates manually under Advanced options > Optional updates, and visit manufacturer websites for graphics drivers. 5. Run a malware scan using MalwareBytes for periodic checks. 6. Delete temporary files via System > Storage > Temporary files in the Settings app, and manage cached files in web browsers.
Winsage
August 7, 2025
Secure Boot is a feature in Windows 10 and Windows 11 that prevents unsafe applications from launching during startup, helping maintain a malware-free environment and serving as a prerequisite for anti-cheat systems like EA's Javelin. It is mandatory for upgrading to Windows 11 but not required for Windows 10. To check if Secure Boot is enabled, users can type "msinfo" in the Windows search bar and verify the Secure Boot State and BIOS Mode in the System Summary. If Secure Boot is off or unsupported, users may need to change their BIOS Mode to UEFI and enable Secure Boot. To enable Secure Boot, TPM 2.0 must be enabled, and the Windows boot drive must be GPT. If the drive is MBR, it can be converted to GPT using the command "mbr2gpt /validate /disk:0 /allowFullOS" followed by "mbr2gpt /convert /disk:0 /allowfullOS." After ensuring UEFI mode is set by disabling Compatibility Support Module (CSM) in the BIOS, users can enable Secure Boot by navigating to the Boot or Secure Boot menu in BIOS and setting it to enabled.
Winsage
June 11, 2025
Microsoft's June updates address a significant vulnerability identified as CVE-2025-3052, which allows attackers to gain control over a PC via bootkit malware by bypassing the Secure Boot feature. This memory corruption issue enables unsigned code to run during the boot process, compromising the system's chain of trust. The vulnerability allows an attacker to sign a compromised UEFI application with Microsoft’s third-party certificates, granting it unrestricted execution rights. Although the flaw has not been exploited in real-world scenarios, it has been present since late 2022. Microsoft has released a patch for this flaw, and users of Windows 10 or 11 are advised to download the latest updates to protect their PCs. Additionally, June's Patch Tuesday addressed a total of 66 weaknesses, including another Secure Boot flaw (CVE-2025-4275) and a zero-day vulnerability (CVE-2025-33053).
Winsage
May 30, 2025
Microsoft rolled out update KB5058405 for Windows 11 23H2 to address critical security vulnerabilities, but users are reporting significant issues, including boot failures with error code 0xc0000098. This problem affects both Windows 11 23H2 and 22H2, primarily in virtual environments like Azure Virtual Machines and on-premises virtual machines hosted on Citrix or Hyper-V. Home users with Windows Home or Pro editions are less likely to experience this issue. The error indicates a missing or corrupted ACPI.sys file, which is essential for managing hardware resources and power states. Microsoft is currently investigating the issue and has not yet provided a resolution.
Search