deprecation

Winsage
May 11, 2025
Windows 11 includes various background services that can be disabled to enhance performance or privacy. Users can access the Services window by searching for "Services" in the search bar. Key services that may be unnecessary for many users include: - Windows Mobile Hotspot Service: Often unnecessary as most laptops lack a mobile data connection. - Fax: Rarely needed for personal computers. - Downloaded Maps Manager: Manages downloaded maps, likely to become less relevant with the deprecation of Windows Maps. - Certificate Propagation: Essential for smart card functionality; can be disabled if not using smart cards. - Windows Insider Service: Manages enrollment in the Windows Insider program; advisable to disable if not participating. - Parental Controls: Useful for families; can be disabled if the device is for personal use. - Windows Image Acquisition: Facilitates image acquisition from scanners and cameras; can be disabled if no scanner is used. - TCP/IP NetBIOS Helper: Aids communication with local network devices; can be disabled for most home users. - Xbox Live Game Save: Syncs save data with Xbox Live; unnecessary for users who primarily use other gaming platforms. - Connected User Experiences and Telemetry: Collects diagnostic data; disabling it can enhance privacy. Disabling these services may not lead to significant performance improvements but can create a more personalized computing experience. Users can re-enable any service if needed later.
Winsage
April 19, 2025
Microsoft has announced the deprecation of Virtualization-based Security (VBS) enclaves, a feature introduced in July 2024, in Windows 11 23H2 and earlier versions, as well as in Windows Server 2022 and its predecessors. Support for VBS enclaves will continue in Windows Server 2025 and future versions. VBS enclaves were designed to create secure memory spaces using Microsoft's Hyper-V hypervisor, enhancing security for specific application components. The decision to phase out VBS enclaves may be influenced by the rapid development cycle of Windows 11. Users are expected to transition to newer releases as support for Windows 11 23H2 ends in November. Enterprise customers relying on VBS enclaves may face disruptions if the feature is completely removed.
Winsage
April 17, 2025
CVE-2025-24054 is a vulnerability that allows attackers to capture NTLMv2-SSP hashes from a victim's machine during authentication requests to an attacker-controlled SMB server. Active exploitation of this vulnerability has been observed since March 19, 2025, targeting government and private sectors in Poland and Romania. The attacks involve phishing emails that lead victims to download an archive file containing exploits designed to leak NTLMv2-SSP hashes. Microsoft has released patches for this vulnerability, but users on older, unsupported versions may need to consider micropatching.
Winsage
April 9, 2025
Microsoft will continue to support driver update synchronization for Windows Server Update Services (WSUS) servers, postponing the planned deprecation initially set for April 18 due to customer feedback. Paul Reed, Azure Compliance Senior Program Manager, noted the importance of this feature for organizations, particularly in regulated environments. A revised timeline for the future of WSUS driver synchronization will be developed, and Microsoft is open to ongoing customer feedback.
Winsage
April 9, 2025
Microsoft is phasing out legacy features from Windows 10 and Windows 11, including the Control Panel. Recent updates have led to a loss of "seconds" precision in the Calendar Taskbar flyout for Windows 10 users. This change mirrors a similar feature removal in Windows 11, where users initially lacked the option to display seconds. Currently, Windows 10 users do not have a toggle to restore this feature, and the impending end of support for Windows 10 raises concerns about the prioritization of user feedback.
Winsage
April 8, 2025
Microsoft has announced an extension of support for Windows Server Update Services (WSUS), postponing the planned end of support originally set for April 2025, in response to user feedback. The decision comes shortly before the scheduled cutoff and addresses challenges associated with disconnected device scenarios. Initially, Microsoft planned to make drivers available only through the Microsoft Update Catalog, but user feedback prompted a change. While some IT administrators may welcome the decision, others argue that WSUS is outdated and lacks essential capabilities for modern security. Gene Moody, field CTO at Action1, noted that WSUS is ill-equipped to meet contemporary demands and highlighted its limitations in enforcing updates and providing real-time visibility. Moody suggested that the extension of support is influenced by specific scenarios where WSUS remains necessary, such as environments with legal obligations or air-gapped networks. He cautioned that this decision should not be seen as a shift away from Microsoft's goal of phasing out WSUS in favor of cloud-based solutions.
Winsage
April 8, 2025
Microsoft has decided to postpone the removal of Windows Server Update Services (WSUS) driver synchronization, which was initially scheduled for April 18, 2025, due to user feedback. WSUS will continue to synchronize driver updates from the Windows Update service and import them from the Microsoft Update Catalog. Microsoft is encouraging administrators to consider alternative technologies such as Windows Autopatch, Microsoft Intune, and Azure Update Manager.
Winsage
April 7, 2025
Microsoft has indefinitely postponed the removal of driver synchronization within Windows Server Update Services (WSUS) in response to customer feedback. The planned removal, originally set for April 18, 2025, has been put on hold as the company works on a revised timeline. This decision marks a shift from previous communications that indicated the deprecation of WSUS driver synchronization. Microsoft had initially announced the intention to phase out this feature in June 2024 and had encouraged IT administrators to adopt cloud-based solutions. Despite the earlier deprecation announcement, Microsoft will continue to support existing WSUS capabilities and publish updates.
Winsage
March 18, 2025
Microsoft is set to release Windows Server 2025 in November 2024, featuring several editions: Essentials, Standard, Datacenter, and Datacenter Azure. Windows Server Essentials is limited to servers with a single CPU and fewer than 10 cores and can only be obtained through hardware OEMs. The Standard edition allows Hyper-V licensing for up to two virtual machines, while the Datacenter edition has no such limits and offers more flexibility with disaster recovery features. The Datacenter Azure edition is optimized for the cloud and receives annual updates. The hardware requirements for Windows Server 2025 include a minimum 64-bit CPU at 1.4 GHz, support for various instructions, and the ability to accommodate up to 2,048 logical processors. The minimum memory requirement is 512 MB, with 2 GB recommended for optimal performance. Storage requirements suggest at least 64 GB for better performance, especially with Desktop Experience, and a Gigabit Ethernet adapter is necessary for networking. Several features have been deprecated in Windows Server 2025, including Computer Browser, Failover Clustering Cluster Sets, and NTLM, among others. Completely removed features include IIS 6 Management Console, NTLMv1, and Windows PowerShell 2.0 Engine. Organizations planning to migrate to Windows Server 2025 must ensure their hardware meets the minimum requirements and can perform an in-place upgrade if currently using Windows Server 2012 R2 or newer. Testing in a lab environment and backing up servers before migration are recommended steps.
Winsage
March 6, 2025
Microsoft has updated its support page to address the "0x80131500" error affecting users of its Store application. This error has been a known issue since 2019. The support article provides four solutions: resetting the Microsoft Store app, checking for updates, running the Store troubleshooter (Windows 10 only), and updating internet TLS settings. Specifically, users are advised to ensure that TLS 1.2 and 1.3 are enabled while TLS 1.0 and 1.1 are unchecked. The "0x80131500" error has also been associated with the Windows 10 20H2 update error. Additionally, TLS 1.0 and 1.1 were deprecated in 2023, leading to their disablement in Microsoft 365 products and related APIs.
Search