update process

Winsage
May 5, 2025
Microsoft has begun the final rollout phase for the Windows 11 24H2 update, which is now being automatically deployed to consumers. Users on Windows 11 Home or Pro versions 23H2, 22H2, and 21H2, not managed by IT departments, will receive the update automatically unless a safeguard hold is in place due to potential issues. Notifications will be sent via Windows Update when the update is downloading and ready for installation. Users can postpone the update but cannot decline it entirely.
Winsage
May 5, 2025
Many users of Windows 11 will receive an automatic upgrade to version 24H2, confirmed by Microsoft. Devices running the Home and Pro editions of Windows 11 (versions 23H2, 22H2, and 21H2) will receive this update without IT management intervention. The rollout began recently and will extend to users of Windows 10 and 11, unless hindered by compatibility issues. Users can manually check for the update through Settings > Windows Update. As of April, Windows 11's market share was 43.72%, compared to 52.94% for Windows 10, with the end of support for Windows 10 set for October 14, 2025. Microsoft is encouraging users to transition to Windows 11 through ads and popups.
Winsage
May 4, 2025
Windows 11 has received mixed feedback from users, particularly regarding its limited customization options, such as the inability to reposition the taskbar. Seelen UI is a free application that offers extensive customization, allowing users to overhaul their user interface. It can be downloaded from the Microsoft Store or GitHub, with the former recommended for easier updates. Upon installation, Seelen UI replaces the taskbar with the Seelen Dock and introduces a Fancy Toolbar for system stats. The Seelen Dock can be customized in size and position, offering more flexibility than Windows 11's default taskbar. Seelen UI also features a Windows Manager that organizes open windows in a cascading manner, enhancing productivity and allowing for further layout customization. Overall, Seelen UI encourages users to create a personalized desktop environment that boosts productivity.
Winsage
May 1, 2025
Windows 10 will reach its end of life in 2025, prompting users to transition to Windows 11, which offers applications to recreate the Windows 10 experience. Transitioning to Windows 11 is possible through an update process if hardware requirements are met, with a temporary backup allowing a revert to Windows 10 within ten days. Applications like Start11 and Startallback enable customization of the Windows 11 interface to resemble Windows 10 or 7. Users can also install themes from the Microsoft Store or online, using Ultra UX Theme Patcher for third-party themes. Windhawk mods further enhance customization options. RevertSV provides an ISO image that mimics Windows 10, mainly for testing in virtual machines.
Winsage
April 30, 2025
Windows 11 version 24H2 has been facing rollout challenges due to compatibility issues, leading Microsoft to implement a new block identified by protection number 56318982. The removal of such blocks can take time, similar to the previous ID 52754008 case. Current problems with Windows Server Update Services (WSUS) are preventing devices on Windows 11 versions 23H2 and 22H2 from accessing the 24H2 update. Users attempting to download version 24H2 may encounter error code 0x80240069, attributed to the April 2025 security update (KB5055528). This error obstructs the download process, and there is no temporary workaround available from Microsoft at this time. The issue is also affecting the System Center Configuration Manager (SCCM). Error code 0x80240069 is not documented in Microsoft's resources.
Winsage
April 29, 2025
Microsoft plans to transition its hotpatching feature for on-premises Windows Server 2025 into a paid subscription service starting in July, 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 has unveiled plans to transition its hotpatching feature for on-premises Windows Server 2025 into a paid subscription service starting in July. This innovative capability allows administrators to implement software updates without the need for system reboots, a significant advantage that streamlines the update process. Hotpatching: A Game Changer for Administrators Hotpatching is not a novel concept; it has been a staple in various environments, including the Linux kernel, VMware products, and the Xen hypervisor. The primary appeal lies in its ability to facilitate security updates without the disruption of reboots, enabling IT teams to maintain operational continuity without the hassle of scheduling downtime. This feature will be a game changer; you may finally get to see your family on the weekends. Currently, Microsoft offers hotpatching for its Windows Server: Azure Edition and version 2022 within its Azure cloud infrastructure. The company has highlighted that its Xbox team has been a significant user of this feature. In August 2024, a preview of hotpatching for Windows Server 2025 running in Azure was announced, followed by a subsequent preview for on-premises implementations managed through the Arc hybrid-and-multicloud management tool. With this latest update, hotpatching is now available for both the Standard and Datacenter editions of Windows Server 2025, allowing on-premises users to benefit from this functionality. Hari Pulapaka, Microsoft’s general manager of Windows Server, emphasized the transformative potential of hotpatching, noting, “This feature will be a game changer; simpler change control, shorter patch windows, easier orchestration.” He humorously added that it might even allow professionals to enjoy more time with their families on weekends. As of last Thursday, Microsoft announced that the current preview will conclude on June 30, transitioning into a subscription model priced at .50 per core per month. Traditional non-hotpatch updates will remain available at no cost. In a detailed explanation, Janine Patrick, Windows Server Product Marketing Manager, and Artem Pronichkin, Senior Program Manager, outlined the service's structure, which aims to deliver eight hotpatches annually. This schedule follows a three-month cycle: the first month serves as a baseline month (monthly cumulative update), followed by two months dedicated to hotpatches. During baseline months—January, April, July, and October—reboots will be necessary. They also noted that, on rare occasions, a non-hotpatch update may be required during a hotpatch month for security reasons, which would also necessitate a reboot. However, the goal remains to provide up to eight hotpatches each year. The benefits of hotpatching are clear, as it can significantly reduce the 'window of vulnerability' that often occurs when administrators delay updates and restarts following a Windows security update. Additionally, it alleviates the traditional burdens associated with 'Patch Tuesday' updates. Importantly, adoption of hotpatching remains optional; Microsoft will continue to provide software updates according to its existing schedule. However, the company anticipates that many Windows Server 2025 users will find value in the ability to minimize downtime through this subscription service. While Windows Server 2025 machines will need to be managed by Arc to utilize hotpatching, there will be no additional costs associated with using Arc for this new offering. Users currently testing the hotpatching preview will automatically transition to the subscription model starting July 1, unless they choose to disenroll before June 30. Notably, Azure Editions of Windows Server will continue to receive hotpatching at no charge. As this new subscription service approaches, the question remains: Will users embrace the opportunity to pay for the promise of non-disruptive patches? The conversation is open for your thoughts." max_tokens="3500" temperature="0.3" top_p="1.0" best_of="1" presence_penalty="0.1" frequency_penalty="frequency_penalty"].50 per core per month. Hotpatching allows administrators to implement software updates without system reboots, enhancing operational continuity. Currently, hotpatching is available for Windows Server: Azure Edition and version 2022 within Azure. A preview for Windows Server 2025 running in Azure was announced in August 2024, followed by a preview for on-premises implementations managed through the Arc hybrid-and-multicloud management tool. The feature will be available for both the Standard and Datacenter editions of Windows Server 2025, with a goal of delivering eight hotpatches annually. Baseline months will require reboots, while hotpatch months will not, unless a non-hotpatch update is necessary. Adoption of hotpatching is optional, and traditional updates will continue to be available at no cost. Users testing the hotpatching preview will automatically transition to the subscription model starting July 1, unless they disenroll before June 30. Azure Editions of Windows Server will continue to receive hotpatching at no charge.
Winsage
April 25, 2025
A recent Microsoft security update has created a new 'inetpub' folder in the root of the system drive, linked to a fix for a Windows Process Activation elevation of privilege vulnerability (CVE-2025-21204). This folder has appeared on systems without Internet Information Services (IIS) installed. Microsoft advises users not to delete the folder, as it enhances system protection. However, cybersecurity expert Kevin Beaumont has shown that the 'inetpub' folder can be manipulated by non-administrative users to create a junction that redirects to a Windows file, potentially obstructing future Windows updates and resulting in a 0x800F081F error code. Microsoft has classified this issue as "Medium" severity and has closed the case, indicating it may be addressed in future updates.
Winsage
April 25, 2025
The upcoming Windows 11 25H2 update is expected to be a modest enhancement rather than a major overhaul, continuing to use the Germanium codebase established with 24H2. A preview build, specifically build 27842 from the Canary Channel, has been identified, and references to GE25H2 were found in the AppraiserRes.dll file, which assesses PC compatibility for the new version. The update is anticipated to arrive in the latter half of the year, similar to previous incremental updates. Concerns exist regarding the stability of 25H2 compared to 24H2, which faced installation issues and compatibility problems. Windows 10 will reach the end of regular support on October 14, 2025, prompting users to transition to Windows 11. Smaller updates like enablement packages tend to present fewer stability risks, and Microsoft has not officially confirmed any details about 25H2 or its update process for versions 23H2 and 24H2. Speculation about Windows 12 continues, but its timeline remains uncertain.
Winsage
April 22, 2025
A security vulnerability identified as CVE-2025-21204 has been discovered in the Windows Update Stack, allowing local attackers to execute unauthorized code and escalate privileges to SYSTEM-level access. This vulnerability, with a CVSS score of 7.8 (High), affects Windows 10 versions 1507, 1607, and 1809, among likely other supported Windows 10/11 and Windows Server versions. The flaw arises from a design issue where Windows Update processes do not properly follow directory junctions, enabling attackers with limited user privileges to redirect trusted paths to locations containing malicious code. Microsoft has introduced a mitigation strategy in its April 2025 cumulative update, which includes creating a new folder at the root of system drives and implementing detection rules for suspicious junction creations. Organizations are advised to apply the April 2025 security updates, restrict ACLs on specific directories, prevent symbolic link creation, and monitor file creation activities in certain directories.
Winsage
April 15, 2025
The April 2025 Windows Recovery Environment update, identified as KB5057589, has caused confusion among Windows 10 users due to an error message (0x80070643 – ERRORINSTALLFAILURE) encountered during installation. Microsoft clarified that this error is a nuisance and does not affect the update or device functionality. The update enhances recovery features for devices facing booting issues and is delivered through Windows Update. Users may see the error if the update is installed while another update is pending a reboot, but the update typically installs successfully after a restart. Microsoft is working on a resolution to address user concerns.
Search