administrators

Winsage
July 24, 2026
This week, Meta experienced a global outage affecting Facebook users, followed by Microsoft facing performance issues with its M365 services, including Teams and SharePoint. Microsoft also reported difficulties with Azure, impacting Windows 11 updates and the Microsoft Store. The issues began around 11:15 AM PST on July 23, 2026, with a notification to users about the Azure outage affecting Windows Update and related services. Microsoft initiated recovery efforts and by 1:45 PM PST, announced that the issues were resolved and services were restored. Currently, there are no ongoing issues reported on the Microsoft Service Health Status page, but the incident is documented on the Windows Release Health page.
Tech Optimizer
July 23, 2026
Poor database performance can lead to missed SLAs, delayed releases, customer dissatisfaction, and lost revenue. Microsoft has enhanced PostgreSQL on Azure, transforming it into a fully managed platform that meets enterprise demands. Azure Database for PostgreSQL and the new Azure HorizonDB offer significant performance improvements, with HorizonDB being three times faster than self-managed PostgreSQL. The PostgreSQL extension for Visual Studio Code integrates performance management into development workflows, providing tools for managing PostgreSQL throughout its lifecycle. Key features include a server metrics dashboard that displays performance indicators, Azure Advisor recommendations for actionable insights, improved query plan visualization, and AI-assisted query analysis. The extension also enhances schema design and query formulation experiences, ensuring secure and governed interactions with PostgreSQL. Azure HorizonDB is in public preview, designed for AI-native workloads. These advancements aim to reduce friction, enhance clarity, and enable faster actions for enterprise teams managing PostgreSQL at scale.
Winsage
July 23, 2026
Microsoft has introduced enhancements to its Windows operating system security, including an update to Entra ID authentication with default passkeys and AI-enhanced security updates. A key advancement is the KMS Hardware-Secured initiative, which uses Trusted Platform Module (TPM)-based attestation to ensure KMS hosts operate on trusted hardware for Windows volume activation. This aims to combat risks from counterfeit KMS servers. Under the new model, KMS hosts will confirm their hardware identity using TPM before activating Windows devices. Starting in August 2026, Windows Server 2025 will provide readiness messaging for KMS host compliance with new security requirements. TPM attestation will be mandatory for KMS Hardware-Secured activation with the upcoming Windows Server 2028 LTSC release. Organizations are advised to prepare for this transition.
Winsage
July 22, 2026
October 2026 will see the end of support for several Microsoft products, including Office LTSC 2021, which requires organizations to transition to LTSC 2024 or Microsoft 365 for continued support. Windows Server 2022 will exit mainstream support on October 13, 2026, while Windows 11 24H2 Home and Pro editions will also reach their end of life on the same date. The enterprise and education versions of Windows 11 23H2 will be supported until November 10, 2026. Publisher 2021 will be discontinued without a successor. Additionally, Entra ID Sign-In risk policies will be phased out on October 1, 2026, necessitating a transition to Conditional Access to maintain user and sign-in risk protection. SQL Server 2017 is scheduled for retirement in October 2027.
Winsage
July 20, 2026
On July 14, 2026, Microsoft released cumulative update KB5101650 for Windows 11 versions 25H2 and 24H2, addressing OS Builds 26200.8875 and 26100.8875. This update includes essential security fixes, updates to Secure Boot certificates, and enhanced Remote Desktop Protocol (RDP) defenses against phishing attacks. It consolidates July 2026's security content, addressing known vulnerabilities and introducing functional improvements. The update is critical for minimizing exposure to identified threats and is prioritized for systems managing remote access or nearing certificate expiration. The update enhances Remote Desktop security by supporting SHA-2 certificate thumbprints while retaining SHA-1 for legacy compatibility. It includes new Group Policy options to mitigate phishing risks associated with malicious .rdp files. The curl upgrade to version 8.21.0 incorporates security patches for command-line tools in Windows environments. Secure Boot certificates are automatically updated through Windows updates, ensuring boot security across various hardware. KB5101650 installs primarily through the Windows Update interface, requiring a restart to activate changes. Enterprise environments can use the Microsoft Update Catalog for manual distribution. A temporary restriction affects certain Dell devices with Intel Innovation Platform Framework drivers, which Microsoft plans to address in a future update. The cumulative update resolves a total of 622 Microsoft CVEs, including 416 affecting Windows components. Users are advised to verify and install the update promptly to secure the full suite of improvements.
Winsage
July 19, 2026
Microsoft held an OEM Secure Boot Office Hours event with manufacturers like Acer, Asus, Dell, and HP to discuss issues related to the Windows 11 Secure Boot 2023 certificate rollout. Many IT administrators left with unresolved concerns, particularly regarding Secure Boot certificate errors. Participants reported persistent problems, including failures of suggested solutions from official documentation to apply to their hardware configurations. Ed Tittel shared his experience with compliance issues related to CA-2023 certificates, noting that ASUS motherboards sometimes required Secure Boot to be disabled temporarily, while MSI models exhibited erratic behavior. ASRock systems needed manual key resets, and documentation was lacking. Devices from Dell, HP, and Lenovo performed better but still faced staggered rollouts and required multiple reboots for BIOS updates. Specific issues raised included HP's BitLocker recovery loop persisting even with the latest BIOS, challenges with legacy device support from HP, devices showing Secure Boot Status as Unknown, and failures in updating the KEK on HP EliteBooks. Some questions from IT administrators regarding Dell and HP went unanswered during the session. The experiences highlighted a trend of Secure Boot issues across multiple OEMs, not limited to a single vendor. IT administrators are advised to pilot updates on representative hardware, back up BitLocker recovery keys, and consult OEM-specific advisories. The unresolved issues reflect common challenges faced by users, indicating that problems with Secure Boot certificate deployments are widespread across various manufacturers.
Search