Intune Autopatch Reports - Expected Behavior
I utilize the Intune Autopatch Reports for Quality Updates to monitor the deployment of updates across our environment. We currently have a group of devices which have a 30-day deferral period due to the compliance/testing policy we have to follow. My Understanding is that the "Quality Update Status" Report will determine if the device is Up-to-Date based on if the device has the update that has been released to it but I am finding that all devices are marked as Not Up-to-Date even with the 2026.05 QU installed as the 2026.06 QU is not available for the devices. I am wondering if this is expected behavior or if this changed because before the changes to the reports in May (2026.05) it was showing correctly Thanks!
KB5089573 forced install + Lenovo network stack degradation (HTTPS latency, build 26200.8524)
KB5089573 installed automatically on a Lenovo system despite updates being paused and no preview updates enabled. After installation, the system jumped to build 26200.8524 and the network stack degraded severely. Heavy HTTPS sites (LinkedIn, Google Finance, YouTube) take 20–60 seconds to load across all browsers. Speedtest is normal, other devices on the same network are unaffected, and both Edge and Chrome show identical latency. DISM shows no package for KB5089573 and the update cannot be uninstalled. Looking for correlation data from other Lenovo users.
The New Activation Portal Is Partly Broken But It Is a MAJOR Inconvenience For Me & Others.
I Run Windows 7 Ultimate x64 And I need to Activate Windows, I am used to the new aka.ms/aoh replacing the phone line. But I Have Activated Windows XP & Vista Without Any Problems Multiple Times, I Tested It Too, Tried 7, Starter, Home, Pro, Ultimate, Even x32 & x64. Though, No matter what, everything BUT Windows 7 Works. This Is Clearly a Server Sided Issue And I've Had This problem for the past months maybe even about a year. (The Product Key I Am Using Is Not Public on The Internet So It's Not Blocked/Used Publicly By Everyone, it is the same product key that came with the CD) And I Can Say For Certain This is a Server Sided Issue. Please Help. And Thank You For Your Time.Windows Update fails with “Something went wrong – Undoing changes” unless installed via ISO
Hi everyone, I'm facing a strange issue with Windows Update on my laptop and I wanted to know if anyone else experienced something similar. Problem: When I install updates through Windows Update, the update downloads normally and during restart it goes up to 100%, but then I get the message: Something went wrong. Undoing changes. After that, Windows rolls back the update. Observation: Interestingly, updates that start directly from the “You're there” stage sometimes install correctly. Policy change I made: Previously Windows would automatically download and install updates and frequently ask for restarts. Because of that behavior, I changed the policy to manual download and install so updates would not start installing automatically. Thermal precaution I tried: Since my laptop has a faulty CPU fan, I also limited the maximum CPU state to 99% in Power Options to prevent aggressive turbo boosting and reduce potential thermal throttling during the update process. Another important observation: If I install the same update using a Windows ISO (in-place upgrade / repair install), the update installs successfully and does not fail at 100%. Possible hardware issue: My laptop currently has: A broken battery A faulty CPU fan So I'm wondering if the update process might be failing due to power or thermal issues during the installation phase. System info: OS: Windows 11 Pro Insider Preview Channel: Release Preview Current build: 26200.7840 Update that fails: KB5077241 (Build 26200.7922) Questions: Can hardware issues like a damaged battery or faulty CPU fan cause Windows Update installation failures? Why would updates succeed when installing from an ISO but fail through Windows Update? Which logs should I check to identify the exact cause? (CBS.log, WindowsUpdate.log, etc.) Any suggestions, troubleshooting steps, or similar experiences would be appreciated. Thanks!CrowdStrike Secure Boot Lifecycle Management Content Pack
CrowdStrike has recently released the Secure Boot Lifecycle Management Content Pack. This new feature helps Falcon for IT module users manage Windows Secure Boot certificate updates ahead of these certificates’ expiration beginning in late June 2026. The dashboard provides an at‑a‑glance view of Secure Boot–enabled devices, showing which systems are already compliant with the updated 2023 Secure Boot certificate, which are in progress, and which are blocked or require opt‑in to a managed rollout. It also highlights certificate update failures that may require investigation. In addition, overall readiness is summarized through a compliance gauge, while a 30‑day trend shows how pass and fail counts change as remediation progresses. Filters by operating system, server edition, hostname, and update status help administrators quickly identify devices that need action to help ensure systems remain secure after the certificates expire. The feature also provides management options to opt devices into Microsoft's managed rollout for gradual, tested deployment, and to block updates on hardware with known compatibility issues to prevent boot failures. Note that this feature is available as part of CrowdStrike's Falcon for IT module. CrowdStrike Endpoint Detection and Response (EDR) customers who are not licensed for this module can enable a free trial from the CrowdStrike Store. To learn more about this feature, please see the content pack tutorial video.
Proposal: Dedicated Windows “Repair Companion” Device for Automatic Deep System Recovery
I’d like to propose a new hardware‑assisted recovery solution for Windows that would dramatically improve system reliability and reduce catastrophic failures caused by deep OS corruption. Today, Windows can repair many issues on its own, but certain types of corruption — such as servicing stack failures, broken WinSxS manifests, failed migrations, or damaged bootloaders — require offline repair or manual intervention. These situations often force users into time‑consuming troubleshooting or full reinstallations. My proposal is a dedicated, consumer‑friendly “Windows Repair Companion” device that connects to a home network and provides a trusted, isolated environment for deep system repair. This would be similar in concept to enterprise out‑of‑band management, but simplified and designed for everyday users. Key Features: • A small hardware device (similar in size to a Surface Dock or streaming box) that plugs into a router or PC. • Contains a hardened, read‑only repair OS and clean Windows recovery images. • Supports automatic network boot (PXE/UEFI) when a PC detects severe corruption or cannot boot normally. • Performs offline repairs: DISM, SFC, CHKDSK, servicing stack rebuilds, WinSxS restoration, bootloader repair, and update rollback. • Provides a true “push‑button restore” experience without requiring user technical knowledge. • Could leverage existing Surface recovery technology, secure boot chains, and cloud restore infrastructure. • Offers a new potential revenue stream for Microsoft while significantly improving Windows reliability. Benefits: • Makes Windows effectively unbrickable for most users. • Eliminates many catastrophic update failures and servicing issues. • Reduces support costs and frustration for consumers and small businesses. • Provides a clean, consistent recovery path across all OEM hardware. • Bridges the gap between consumer Windows and enterprise‑grade resilience. This device would give users peace of mind and provide Microsoft with a modern, hardware‑assisted recovery model that aligns with the direction of Surface and Windows Core OS technologies. Thank you for considering this idea — I believe it could meaningfully improve the Windows experience for millions of users.
