reboot

Winsage
May 19, 2025
Many users are experiencing issues with Windows 10 versions 22H2 and Windows 10 Enterprise LTSC 2021, particularly those with Intel Trusted Execution Technology (TXT) on tenth-generation or later Intel processors with vPro support. Users who have BitLocker enabled and installed the KB5058379 patch released on May 13 may need their BitLocker recovery keys due to a bug causing lsass.exe to terminate unexpectedly, leading to an Automatic Repair cycle or a reboot loop. Microsoft has acknowledged the issue and is working on an Out-of-band update. Meanwhile, workarounds, such as disabling TXT, pose security risks. Microsoft also announced significant layoffs affecting thousands of employees.
Winsage
May 18, 2025
Windows 10 users are facing issues due to the mandatory KB5058379 update, which has caused some PCs to boot into Windows Recovery mode and prompted the need for a BitLocker key. Some users have also experienced a Blue Screen of Death (BSOD). The update primarily affects devices with Intel Trusted Execution Technology (TXT) using 10th generation or later Intel vPro processors, particularly on Windows 10 versions 22H2 and Windows 10 Enterprise LTSC 2021. Microsoft is working on a resolution and plans to release an Out-of-band update soon. Affected users are advised to disable Intel TXT in the BIOS to complete the update successfully and avoid further issues. Windows 11 is not impacted by this problem.
Winsage
May 17, 2025
Microsoft will end update support for Windows 10 in October 2025, but new patches are still being released. The latest cumulative update, KB5058379, has caused issues for users, especially those with devices from Dell, Lenovo, and HP. Microsoft is aware of the problems and has not yet deployed a fix as of May 16, but has provided a temporary workaround. For users affected by the BitLocker bug, Microsoft Support recommends the following steps to regain access: 1. Disable Secure Boot in BIOS/Firmware settings. 2. If issues persist, disable all virtualization technologies in BIOS/Firmware settings. 3. Check the Microsoft Defender System Guard Firmware Protection Status via Registry Editor or GUI method. 4. If firmware protection settings are restricted by Group Policy, disable them using Group Policy Editor or Registry Editor. A system restart is required for these changes to take effect, and these workarounds should only be temporary until a patched update is released. Disabling certain BIOS settings may compromise system security.
Winsage
May 16, 2025
Microsoft is winding down support for Windows 10 this October and has released update KB5058379, which has caused unexpected BitLocker recovery prompts for some users after a restart. This issue has been confirmed by Microsoft representatives on forums, although it is not mentioned in the update's release notes. The problem predominantly affects devices from manufacturers like Dell, HP, and Lenovo, and the specific cause is unclear. Microsoft has provided workarounds, including disabling Secure Boot and virtualization technologies, checking Microsoft Defender System Guard Firmware Protection status, and disabling firmware protection via Group Policy or Registry Editor.
Winsage
May 16, 2025
Users are experiencing BitLocker Recovery screens and Blue Screens of Death (BSOD) after installing the Windows 10 update KB5058379. This mandatory update addresses significant security vulnerabilities, but Microsoft claims to be unaware of any new issues. Some users have found that disabling Intel TXT can help complete the installation. Reports include a user experiencing consistent BSODs after the update and another who resolved boot issues by changing BIOS settings. The end of support for Windows 10 is approaching on October 14, but Microsoft 365 applications will still receive security updates afterward. Windows 11 users are not affected by these issues.
Winsage
May 16, 2025
The Windows 10 KB5058379 cumulative update, released on May 13, 2025, has caused unexpected BitLocker recovery prompts for some users after installation and reboot. Reports indicate that affected devices, including those from Lenovo, Dell, and HP, automatically boot into the Windows Recovery Environment and display the BitLocker recovery screen. Users have experienced various issues, such as needing BitLocker keys to start up or devices refusing to start. A workaround involves disabling Intel Trusted Execution Technology (TXT) in the BIOS. Microsoft has not publicly acknowledged the issue but support representatives are aware and working on a resolution. Microsoft has provided steps to resolve the issue, including disabling Secure Boot and virtualization technologies, checking Microsoft Defender System Guard Firmware Protection status, and disabling firmware protection via Group Policy or Registry Editor.
Winsage
May 12, 2025
The Emergency Restart method in Windows 11 can be initiated by pressing CTRL + ALT + DEL and holding the CTRL key while clicking the power button. This prompts a message warning that any unsaved data will be lost and confirms the restart. It serves as an alternative to a hard reset, especially useful for unresponsive computers, and is beneficial for laptops without a dedicated power button. Users have reported successful restarts without adverse effects. Additionally, the Command Prompt can be used to restart the machine by typing "shutdown /r".
Tech Optimizer
May 12, 2025
Defendnot is a tool that disables Windows Defender by using the Windows Security Center (WSC) API, presenting itself as a legitimate antivirus solution. It was created by a developer named “es3n1n” and follows the removal of a previous tool called “no-defender.” The tool engages directly with WSC, which disables Windows Defender when third-party antivirus software is installed to avoid conflicts. Defendnot was developed through reverse engineering of the WSC service and involves understanding how WSC verifies processes. It registers a phantom antivirus product using COM interfaces and undocumented Windows APIs, leading Windows to disable its built-in protection. The tool requires administrative privileges to operate and adds itself to autorun to maintain its functionality after a reboot. Security experts express concern about its potential misuse by malware authors, while it also provides insights into vulnerabilities in Microsoft’s security architecture.
Tech Optimizer
May 12, 2025
Cybersecurity developers have created a tool called defendnot, which disables Windows Defender by utilizing undocumented Windows Security Center (WSC) APIs. This tool is a successor to the no-defender project, which was taken down due to DMCA challenges. The developer reverse-engineered WSC’s validation algorithms and identified Taskmgr.exe as a suitable process to host the necessary code. Defendnot persists across reboots by adding itself to Windows autorun and can be managed via a command-line interface with options to disable Windows Defender and Windows Firewall. Unlike its predecessor, defendnot does not use third-party antivirus code. Security experts warn that disabling protection mechanisms should only be done in controlled environments by knowledgeable users.
Search