non-security updates

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.
Winsage
April 16, 2025
Microsoft has warned customers about potential system failures due to a blue screen error (secure kernel fatal error) following the installation of Windows updates since March, specifically the KB5055523 April cumulative update and the KB5053656 March preview update, affecting Windows 11, version 24H2. Users may experience crashes and a blue screen exception with the code 0x18B. Microsoft is working on a solution and has implemented a Known Issue Rollback (KIR) to reverse the problematic updates, which will automatically reach affected devices within 24 hours. Affected users are advised to restart their devices. For enterprise-managed devices, administrators must install the KIR Group Policy specific to their Windows version to resolve the issue, requiring a device restart. Further assistance is available on the Microsoft support website. Additionally, Microsoft has released emergency updates for local audit logon policies in Active Directory Group Policy and alerted administrators about potential inaccessibility of Windows Server 2025 domain controllers post-restart.
Winsage
March 27, 2025
The transition to cloud-native endpoint management is changing Windows device management, particularly regarding Windows Update. IT administrators are increasingly relying on Windows Update services for security patches and features. Microsoft has introduced Windows Update for Business to give IT administrators better control over update policies through Group Policy or Mobile Device Management (MDM). Effective management requires understanding which policies to implement for specific desktops. The best approach for managing monthly updates is through servicing rings, which group Windows devices and assign specific update cadences and policies. This method allows controlled rollouts of updates, enabling administrators to prioritize stability and minimize disruption by testing updates on pilot groups before wider deployment. Windows Update for Business manages three update channels: the General Availability Channel for immediate feature updates, the Long-Term Servicing Channel (LTSC) for stability-focused devices, and the Windows Insider Program for testing updates. Administrators can control these channels using specific Group Policy Object (GPO) settings. Two primary update release types are managed: quality updates, which are released monthly and can be deferred for up to 30 days, and feature updates, which are annual and can be deferred for up to 365 days. Administrators can pause the deployment of updates temporarily for up to 35 days. Driver updates are also managed through Windows Update, with options to include or exclude them in monthly quality updates. Optional updates, available monthly, can be controlled using specific GPO and MDM settings.
Winsage
March 27, 2025
Microsoft has acknowledged a significant issue affecting Remote Desktop functionality on Windows Server 2025 systems, which arose after the installation of security updates released since February 2025. Users may experience freezes in Remote Desktop sessions shortly after connecting, with unresponsive mouse and keyboard inputs requiring a disconnect and reconnect to regain functionality. This issue also affects Windows 11 24H2 systems, but Microsoft addressed it for Windows 11 users with an optional update (KB5052093) released on February 25. A fix for Windows Server 2025 devices is planned for an upcoming update. Additionally, Microsoft has implemented Known Issue Rollback (KIR) to reverse problematic non-security updates related to Remote Desktop and Remote Desktop Services (RDS) connection issues from Windows 11 24H2 updates since January 2025. Users may experience Remote Desktop Protocol (RDP) disconnections lasting up to 65 seconds when connecting from Windows 11 24H2 devices to RDS hosts on Windows Server 2016 systems. A permanent fix for RDP disconnection issues is planned for next month's cumulative updates. Microsoft is also investigating connection errors on Windows 11 24H2 systems related to restoring data from SMB network shares or Backup & Replication servers.
Winsage
March 26, 2025
Microsoft has resolved an issue affecting USB printers that began after Windows updates in January 2025, which caused printers to produce random text. This fix is included in the March 2025 non-security preview updates KB5053643 and KB5053657 for Windows 10 (version 22H2) and Windows 11 (versions 22H2 and 23H2). The resolution will also be part of the cumulative updates for April 2025 Patch Tuesday. The problem was particularly noticeable when printers were powered on or reconnected, leading to erroneous outputs related to the Internet Printing Protocol (IPP). Microsoft acknowledged that the issue arose after the January 2025 preview update (KB5050092). Additionally, Microsoft has addressed another issue affecting Remote Desktop and RDS connections and is collaborating with Veeam to investigate connection errors on Windows 11 24H2 systems.
Winsage
March 26, 2025
Microsoft has informed users about issues with Remote Desktop and Remote Desktop Services (RDS) connections after recent Windows updates since January 2025. Users may experience unexpected disconnections during Remote Desktop Protocol (RDP) sessions following the January preview update (KB5050094) and the March 2025 security update (KB5053598). Specifically, users connecting from Windows 11 24H2 PCs to RDS hosts on Windows Server 2016 or earlier may be disconnected after about 65 seconds. Microsoft has introduced a solution through its Known Issue Rollback (KIR) feature, requiring administrators to install and configure the Windows 11 24H2 and Windows Server 2025 KB5053598 250314_20401 KIR group policy. A restart of affected devices is necessary to apply the new settings. A permanent fix will be included in a future Windows update.
Winsage
March 19, 2025
Microsoft has introduced a gamepad keyboard for Windows 11 that allows users to type using an Xbox controller. This new feature enhances the on-screen keyboard and includes shortcuts for Xbox controllers, such as using the X button for backspace and the Y button for the spacebar. The gamepad keyboard is part of Microsoft's initiative to improve the handheld experience for gamers and is currently available in the Release Preview version of Windows 11, with wider access expected soon. Additionally, Microsoft has updated the Game Bar for better usability on smaller screens and improved controller navigation in the Xbox app for PC.
Search