26H2 → 26220 → 25H2 upgrade failures and Insider enrollment reverting
Ok, so I moved from the Beta Channel to the Experimental Channel to pick up 26H2 early, following the guidance in the Insider email and the support article. After receiving 26H2, I switched back to Beta, which the same guidance said was fine. After that, Windows tried to install build 26220, and that upgrade failed twice. I tried leaving the Insider Program to return to the base build, planning to re‑enter Beta afterward. The staging phase completed normally, but on reboot the system skipped the usual update screens and went straight to the desktop without applying anything. When I tried re‑entering Insider Beta, the system reverted the change on reboot and left me unenrolled again. I’ve paused the attempt to install 25H2 because it keeps trying to stage and uses a large amount of disk space. The upgrade failures all behave the same way. The “Preparing updates” part at restart completes, the offline portion completes, but the online configuration phase never runs. The system just rolls back to the desktop with no visible error. The error code I’ve seen is 0x8007000D, and the failure happens during the SECOND_BOOT / MIGRATE_DATA phase. I also tried getting help through support. One rep said she would remote in to troubleshoot, but that session never happened. The next rep did remote in, but only cleared temporary files and ran a basic step. During that conversation I was told the case was waiting for escalation, then that there was no escalation team, and then that it had been forwarded to the correct team. The case was closed before I had time to reply or ask anything. There seems to be a servicing stack mismatch as well. DISM reports version 10.0.26100.8772, while the image version shows 10.0.26300.8772. The same mismatch appears across other command‑line tools I used while trying to clear space and repair the servicing environment. I’ve been working on this for days now and I’m really hoping someone can help. Thank you in advance.
Server 2016 Windows Update disabled?
I have Windows 2016 and 2019 Servers. All in in the same OU and getting the same Group Policy. This is confirmed via gpresult. I am using GP to disable Automatic Updates. This looks to be working in 2019: But with Server 2016, it says this: Should I expect these servers to update?
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!
Windows update in settings not showing up (something went wrong. Try open settings later)
i've had this problem a while now but didnt think much of it until i needed newer versions of windows to run apps. tried many ways like resetting settings to refresh. tried pc health check, troubleshoots which gave results that the problem was no identifiable. im not sure what i should do. i am trying to update to the lastest win 10 version as my pc does not support win 11.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.
Windows Update took too long to finish
Hello. As of now I'm updating my PC and it's still not finish yet, it's stuck on the loading screen. I don't know how many times I experienced this but I can't install the latest updates on my PC these past few weeks because of this, it's always stuck on loading screen after restarting. Please help, what should I do? The "orange" on the Windows Update symbol is now "red".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.
