non-security updates

Winsage
January 15, 2026
Microsoft concluded all support for Windows Vista and Server 2008 as of January 13, 2026. Most customers lost support in January 2020, but Extended Security Updates were available until January 2023 for most users and until January 2024 for Azure customers. Free security updates, non-security updates, and support options are no longer accessible for the retired codebase. Organizations are encouraged to migrate to Azure for additional security updates. Windows Server 2012 will also reach the end of its ESU on October 13, 2026.
Winsage
November 12, 2025
Microsoft's November 2025 Patch Tuesday addresses a total of 63 vulnerabilities, including one actively exploited zero-day flaw (CVE-2025-62215) related to Windows Kernel Elevation of Privilege. The updates include four vulnerabilities classified as "Critical," with two for remote code execution, one for elevation of privileges, and one for information disclosure. The breakdown of vulnerabilities is as follows: - 29 Elevation of Privilege Vulnerabilities - 2 Security Feature Bypass Vulnerabilities - 16 Remote Code Execution Vulnerabilities - 11 Information Disclosure Vulnerabilities - 3 Denial of Service Vulnerabilities - 2 Spoofing Vulnerabilities This Patch Tuesday marks the first extended security update (ESU) for Windows 10, and users are encouraged to upgrade to Windows 11 or enroll in the ESU program. Microsoft has also released an out-of-band update to assist with enrollment issues. Other companies, including Adobe, Cisco, and Google, have also issued security updates in November 2025.
Winsage
September 5, 2025
Microsoft is concluding official support for Windows 10 in October 2025 and encourages users to upgrade to Windows 11, which is available for free for existing Windows 10 users. Some users prefer to stay on Windows 10 due to compatibility issues or a desire to avoid Windows 11's AI features. Microsoft offers an Extended Security Updates (ESU) program that provides an additional year of security updates until October 2026 for users who wish to continue using Windows 10. Initially, Microsoft considered charging for the ESU program but reversed this decision based on user feedback. Users must enroll in the ESU program before the deadline of October 14, 2025. To find the ESU offer, users can navigate to Settings > Updates & Security > Windows Update. The ESU program will provide security updates only, with no new features, and technical support will be limited.
Winsage
July 27, 2025
In July 2025, Microsoft released non-security updates for Windows 10 (KB5062649) and Windows 11 (KB5062663 for versions 22H2 and 23H2; KB5062660 for version 24H2), introducing AI functionalities, improvements in Settings, and a redesigned BSOD. Companies like Brave and AdGuard are blocking Windows Recall due to privacy concerns. Microsoft is developing a tool for transitioning from older to newer computers and published a guide for Windows 10's end of support on October 14, 2025. The Windows Insider Program released Build 27909, focusing on minor fixes, and introduced an audio-sharing feature. Microsoft disclosed a security breach in SharePoint affecting the US nuclear weapons department and provided fixes. The Surface Laptop 7 was launched with Intel's Core Ultra 200 Series processors and optional 5G connectivity. The Files app received a preview update with a new Omnibar. Meta is transitioning WhatsApp on Windows to a progressive web app, and Firefox released version 141.0 with AI-powered tab groups. Microsoft is testing a cross-device play history feature for Xbox and reversed its decision on Xbox game pricing. EA announced a new Battlefield installment, and Nvidia added new titles to GeForce NOW. Various discounts and a free game, Legion TD 2, were featured in the Weekend PC Game Deals.
Winsage
July 8, 2025
The end of support for Windows 10, originally set for October 14, 2025, has been postponed for certain users, particularly accounting firms, allowing them more time to upgrade. Microsoft has introduced an Extended Security Updates program for select Windows 10 users, which requires a fee per device for continued security updates, but does not include new features or general tech support. A December 2023 report indicates that 47% of accountants still rely on Windows 10, with approximately 25% of Windows 10 PCs actively used in accounting firms. Over half of all devices have migrated to Windows 11, which holds about 52% of the market. Experts recommend delaying upgrades to Windows 11 in favor of Windows 12, expected to be more optimized for AI, with potential hardware investments needed for the transition.
Winsage
April 30, 2025
Microsoft will transition hotpatching for Windows Server 2025 to a paid subscription model starting July 1, 2025, with a cost of [openai_gpt model="gpt-4o-mini" prompt="Summarize the content and extract only the fact described in the text bellow. The summary shall NOT include a title, introduction and conclusion. Text: Microsoft has made a significant announcement regarding the future of hotpatching for Windows Server 2025, a feature that allows administrators to apply security updates without the need for system restarts. As the company prepares for the general availability of this service, it will transition to a paid subscription model starting July 1, 2025. Subscription Details and Preview Phase In a proactive move, Microsoft is encouraging administrators to take advantage of the free preview of hotpatching before it becomes a subscription-based service. This opportunity will remain available until June 30, after which those currently testing the service will be automatically subscribed unless they opt out. “Hotpatching for Windows Server 2025, made available in preview in 2024, will become generally available as a subscription service on July 1st, 2025. With hotpatching, we are taking what was previously an Azure-only capability and now making it available to Windows Server machines outside of Azure through Azure Arc,” Microsoft stated. Upon the subscription launch, hotpatching will be priced at .50 USD per CPU core per month. To utilize this feature in multi-cloud environments or on-premises, users will need both a Hotpatch service subscription and an Azure Arc-connected server running Windows Server 2025 Standard or Datacenter. How to Enable Hotpatching Enabling hotpatching on your server is a straightforward process. First, connect your server to Azure Arc by following the specified steps. Next, navigate to Azure Update Manager within the Azure Portal, select your Azure Arc-enabled server, and check the hotpatching option as outlined in the provided documentation. A Brief History of Hotpatching Hotpatching has been a part of Microsoft's offerings since February 2022, initially available for Windows Server 2022 Datacenter: Azure Edition. This feature allows for the deployment of security updates by patching the in-memory code of running processes, eliminating the need for reboots after each installation. However, it is important to note that servers still require reboots for updates delivered through the standard Windows update channel, which are not included in the Hotpatch program. This includes non-Windows updates, such as .NET patches, and Windows non-security updates. Microsoft began public testing of hotpatching for Windows Server 2025 in September 2024, with further expansions to Windows 11 24H2 and Windows 365 following in November 2024. By April 2025, hotpatch updates will be generally available for business customers using Windows 11 Enterprise 24H2 on x64 (AMD/Intel) systems." max_tokens="3500" temperature="0.3" top_p="1.0" best_of="1" presence_penalty="0.1" frequency_penalty="frequency_penalty"].50 per CPU core per month. A free preview of the service is available until June 30, 2025, after which users testing the service will be automatically subscribed unless they opt out. Hotpatching allows administrators to apply security updates without system restarts and will be available for Windows Server machines outside of Azure through Azure Arc. To enable hotpatching, servers must be connected to Azure Arc and configured via the Azure Update Manager. Hotpatching was initially introduced in February 2022 for Windows Server 2022 Datacenter: Azure Edition and allows for in-memory code updates, but standard Windows updates still require reboots. Public testing for Windows Server 2025 began in September 2024, with general availability for Windows 11 Enterprise 24H2 expected by April 2025.
Winsage
April 28, 2025
Microsoft will launch a subscription-based hotpatching service for Windows Server 2025 on July 1, 2025, priced at [openai_gpt model="gpt-4o-mini" prompt="Summarize the content and extract only the fact described in the text bellow. The summary shall NOT include a title, introduction and conclusion. Text: Microsoft is set to transform the landscape of enterprise updates with the upcoming launch of its subscription-based hotpatching service for Windows Server 2025. This innovative approach marks a significant shift in how updates will be managed for businesses operating Windows Server outside of Azure. Beginning July 1, 2025, hotpatching will transition from a complimentary preview to a paid subscription model, priced at .50 per CPU core per month. This change extends a capability that was previously exclusive to Azure users, now making it accessible for on-premises servers and hybrid environments through Azure Arc integration. What Is Hotpatching? Hotpatching is a cutting-edge technology that enables the installation of security and critical updates without necessitating a system reboot. Instead of interrupting services or rebooting servers, hotpatching directly updates the in-memory code of running processes. This advancement brings Windows server deployments in line with similar technologies that Linux administrators have enjoyed for years, such as kpatch and ksplice. By allowing updates without reboots, organizations can significantly reduce disruptions while enhancing their security posture. How Does Hotpatching Work? The hotpatching mechanism follows a structured update cycle: Baseline months: In January, April, July, and October, a full cumulative update will be released, requiring a reboot to establish a new baseline. Hotpatch months: In the two months following each baseline month, critical patches will be deployed via hotpatches without requiring any server reboots. This means that servers will only need to reboot approximately four times a year, rather than monthly. On rare occasions, Microsoft may issue a critical security update that requires a reboot even during a hotpatch month, but the aim remains clear: to provide up to eight rebootless hotpatches annually. Why Is Microsoft Moving to a Paid Model? While hotpatching was available at no additional cost during its preview phase, Microsoft is now positioning it as a premium feature for customers seeking maximum uptime, operational simplicity, and rapid security response. According to the Windows Server team at Microsoft, the value of hotpatching encompasses: Reduced Downtime: Maintain operations without the need for scheduling late-night or weekend reboot windows. Faster Updates: Smaller patches facilitate quicker deployments. Enhanced Security: Address vulnerabilities swiftly without delays associated with reboot coordination. Operational Efficiency: Streamlined change management and patch orchestration. Internal teams at Microsoft, including the Xbox division, have already experienced notable efficiency improvements with hotpatching, completing tasks that previously took weeks in just days. Subscription Details Feature Details Launch Date July 1, 2025 Price .50 USD per CPU core per month Editions Supported Windows Server 2025 Standard and Datacenter Deployment Requirement Must be connected to Azure Arc Included with Azure Editions Datacenter: Azure Edition (no extra charge) Patch Frequency 8 hotpatches/year + 4 reboot-required baseline patches Organizations currently utilizing the free preview must either opt out before June 30, 2025, or they will be automatically transitioned into the paid subscription starting in July. While hotpatching offers powerful capabilities, it does not entirely eliminate the need for traditional updates. Certain updates will still necessitate a reboot, including: Major non-security updates. .NET Framework patches. Driver and firmware updates. Emergency out-of-band security patches. As such, administrators should still anticipate occasional downtime, albeit significantly reduced. By incorporating hotpatching into their update strategies, organizations can bolster system availability and streamline their maintenance processes." max_tokens="3500" temperature="0.3" top_p="1.0" best_of="1" presence_penalty="0.1" frequency_penalty="frequency_penalty"].50 per CPU core per month. Hotpatching allows security and critical updates to be installed without rebooting the system, reducing downtime and enhancing security. The update cycle includes four baseline months requiring reboots and eight hotpatches annually without reboots. The service is available for Windows Server 2025 Standard and Datacenter editions and requires connection to Azure Arc. Organizations using the free preview must opt out by June 30, 2025, or will be transitioned to the paid model. Certain updates, such as major non-security updates and .NET Framework patches, will still require reboots.
Winsage
April 17, 2025
Microsoft has reported that two recent updates for Windows 11 24H2, specifically the April cumulative update KB5055523 and the March preview update KB5053656, are causing blue screen crashes with the error code 0x18B (SECUREKERNELERROR) after installation and reboot. There is currently no permanent solution, but Microsoft is working on a workaround using a Known Issue Rollback (KIR) that will automatically apply to personal or unmanaged devices through Windows Update. IT departments will need to manually download a Group Policy .msi file to implement the rollback. Affected machines will require a restart to complete the process.
Search