registry key Archives

Winsage

May 8, 2025

Security update causes new problem for Windows Hello for Business authentication

Microsoft has indicated that a range of products, including their own and third-party solutions like smart card authentication products, single sign-on (SSO) systems, and identity management platforms, may be experiencing issues linked to a specific feature. This has led to an increase in support calls within certain organizations, particularly affecting machine-to-machine authentication. To mitigate disruptions from logon failures, Microsoft recommends that organizations temporarily change the registry key AllowNtAuthPolicyBypass from ‘2’ back to ‘1’, as detailed in KB5057784.

Winsage

April 15, 2025

How to upgrade your ‘incompatible’ Windows 10 PC to Windows 11 now

On October 14, 2025, Microsoft will stop providing security updates for Windows 10 PCs unless users enroll in the Extended Security Updates program. Upgrading to Windows 11 on machines older than five years may result in an error message about CPU compatibility, as Microsoft will not change the requirement for a Trusted Platform Module (TPM) version 2.0. While automatic upgrades may be hindered, there are workarounds for most PCs designed for Windows 10. To upgrade, the computer must boot using UEFI, support Secure Boot, and have an enabled TPM (version 1.2 is acceptable). Users can check their system's BIOS mode and TPM status using the System Information utility and the Trusted Platform Module Management tool, respectively. If UEFI is not an option or if the PC lacks a TPM, an undocumented hack can be used to bypass compatibility checks. A new restriction with the Windows 11 version 24H2 update requires CPUs to support SSE4.2 and PopCnt instructions, making upgrades impossible for PCs built in 2008 or earlier. Most Intel CPUs from 2009 and AMD CPUs from 2013 should meet this requirement. Users can bypass CPU checks and accept any TPM version through a registry edit, which requires running the Setup program from the current Windows installation. The process involves creating a registry key and modifying its value. Alternatively, the Rufus utility can be used to create a bootable USB drive that circumvents compatibility checks, but it cannot bypass the restrictions for very old CPUs lacking support for SSE4.2 and PopCnt instructions.

Winsage

April 4, 2025

Windows 11 Enterprise machines can now get updates while you work—no reboot required

Microsoft has introduced a hotpatch update system for Windows 11 Enterprise builds, specifically for version 24H2, which allows updates to be applied without requiring a system restart. This feature is beneficial for corporate environments, as it helps maintain productivity and reduces CPU usage during updates. While quarterly updates will still necessitate a reboot, the hotpatching system represents a shift from the previous monthly reboot requirements. To enable hotpatching, organizations must meet specific requirements: a subscription to Windows 365 Enterprise or Windows 11 Enterprise (E3, E5, or F3), a client running Windows 11 Enterprise 24H2 (build 26100.2033 or higher), activation of Visualization-based Security (VBS), and an AMD or Intel x64 processor. For Arm64 devices, the hotpatch system is in public preview and requires a registry key modification. Hotpatch updates will follow the standard update schedule applicable to both Windows 10 and Windows 11 23H2 devices, with each release assigned a distinct KB number. This feature is only available for Windows 11 Enterprise clients and does not extend to Windows 11 Home or Pro machines.

Winsage

April 2, 2025

Microsoft adds hotpatching support to Windows 11 Enterprise

Microsoft has made hotpatch updates available for business customers using Windows 11 Enterprise 24H2 on x64 systems, allowing seamless installation of security updates without device reboots. Hotpatching modifies in-memory code of active processes to deploy updates without interrupting user activities. Devices under a hotpatch-enabled quality update policy will receive updates quarterly, with no restarts required for eight months of the year. A Microsoft subscription is necessary to activate hotpatching, and devices must meet specific prerequisites, including an x64 CPU and enabled Virtualization-based Security. Hotpatch updates can be managed through Microsoft Intune, and devices on Windows 10 and versions 23H2 and lower will continue to receive standard updates. Microsoft initially introduced hotpatch support for Windows Server Azure Edition in February 2022 and has expanded testing to include Windows 11 24H2.

Winsage

February 13, 2025

Power Automate vs RoboTask: Here’s what you should use to automate your PC

Power Automate and RoboTask are automation tools for Windows 11 users that aim to simplify repetitive tasks with minimal coding. Power Automate is developed by Microsoft and is pre-installed with Windows 11, offering many features at no additional charge, while RoboTask is a third-party application that requires a paid license after a 30-day trial. Power Automate has a modern interface that integrates well with Windows 11, making it easier to record workflows, whereas RoboTask has over 300 actions, including advanced capabilities like registry key manipulation. RoboTask can run automations based on various triggers, while Power Automate requires an internet connection to function and excels in integrating with Microsoft Office and cloud services.

Winsage

February 12, 2025

Microsoft takes it easy on February’s Patch Tuesday

Microsoft released a total of 63 patches in February, including six previously released ones. Two vulnerabilities, CVE-2025-21418 (CVSS 7.8) and CVE-2025-21391 (CVSS 7.1), are actively exploited and require local access and authentication for exploitation. CVE-2025-21418 affects the Windows Ancillary Function Driver for Winsock, allowing attackers to gain SYSTEM-level privileges on Windows 10, 11, and various Windows Server versions. CVE-2025-21391 affects Windows Storage, enabling local attackers to delete files under certain conditions. Two publicly known vulnerabilities, CVE-2025-21194 (CVSS 7.1) and CVE-2025-21377 (CVSS 6.5), have not yet been exploited. CVE-2025-21194 exposes PCs to potential hypervisor and secure kernel compromises, while CVE-2025-21377 risks leaking a user's NTLMv2 hash with minimal user interaction. CVE-2025-21198, rated at CVSS 9.0, allows remote code execution in high-performance computing infrastructures, requiring network access to a targeted HPC cluster. Excel users should address five patches rated at 7.8, particularly CVE-2025-21381, which has potential for remote code execution through local attack vectors. As of February 11, administrators must configure the StrongCertificateBindingEnforcement registry key on domain controllers to avoid transitioning to Full Enforcement mode by February 2025. CVE-2025-21177 (CVSS 8.7) has been fully mitigated by Microsoft. Adobe released 45 updates, with 31 addressing vulnerabilities in Adobe Commerce, and critical patches for InDesign and Illustrator. SAP issued 21 patches affecting NetWeaver and addressing cross-site scripting issues. Fortinet released security updates for various products, including a critical authentication bypass vulnerability in FortiOS and FortiProxy (CVSS 9.6).

Winsage

February 5, 2025

No Windows 11 hardware requirement workaround for you!

Microsoft has removed guidance on bypassing the Trusted Platform Module (TPM) 2.0 requirement for installing Windows 11 from its help page. This change indicates a potential shift in policy regarding the installation of Windows 11 on PCs without TPM 2.0. The workaround previously involved creating a Windows Registry key but still required TPM 1.2. The removal occurred between December 12 and 14, 2024, according to the Wayback Machine's archives. Additionally, Microsoft tightened another method for bypassing the TPM requirement in August 2024, while third-party applications like Flyby11 are still available but have recently been flagged by Microsoft Defender as potentially unwanted software. These developments suggest that Microsoft is reinforcing its requirement for Windows 11 to be installed on machines with TPM 2.0.

Winsage

February 5, 2025

Microsoft is cracking down on unsupported Windows 11 installs

A support document on installing Windows 11 on unsupported PCs has been removed from Microsoft's website. This document previously provided a method for users to bypass the mandatory TPM 2.0 requirement by modifying registry key values, but its removal indicates a shift in Microsoft's stance against this workaround. The end of support for Windows 10 is approaching, leaving many users on older PCs vulnerable to security risks. The original support article can still be accessed via the Internet Archive’s Wayback Machine.

Winsage

February 4, 2025

Microsoft removes guide for installing Windows 11 on unsupported PCs – but this hack still works

Microsoft is pushing users to transition to Windows 11, which requires devices to have a Trusted Platform Module (TPM) 2.0. The company has removed instructions for a Registry hack that allowed users to bypass this requirement from its support page. The current installation guidelines include legitimate methods such as Windows Update and the Installation Assistant, while warnings against installing on unsupported devices remain. Despite the Registry hack still functioning, Microsoft prefers users not to publicize it, and alternative third-party tools exist for navigating hardware restrictions. The end of support for Windows 10 is approaching in October, increasing the urgency to upgrade, although many older PCs do not meet the upgrade criteria. Microsoft has reiterated the risks of installing Windows 11 on incompatible hardware, including potential compatibility issues and loss of support.

Winsage

February 4, 2025

Microsoft quietly removes official Windows 11 CPU/TPM bypass for unsupported PCs

In October 2021, Microsoft launched Windows 11, version 21H2, and provided a workaround for users with unsupported PCs to upgrade. This workaround involved modifying the Registry to bypass CPU and TPM compatibility checks. However, Microsoft has since removed this workaround from its support documentation after the release of Windows 11 24H2, indicating a shift in its approach. The company now recommends purchasing new hardware for compatibility with Windows 11 and does not endorse upgrades on unsupported devices.