windows update
84 TopicsWindows 10 and reserved storage
First published on TECHNET on Jan 07, 2019 Reserving disk space to keep Windows 10 up to dateWindows Insiders: To enable this new feature now, please see the last section "Testing out Storage Reserve" and complete the questStarting with the next major update we’re making a few changes to how Windows 10 manages disk space.1.5MViews33likes107CommentsWindows office hours are closed: May 20, 2021
Thanks to everyone who joined us for office hours! Here is a list of who was in the virtual office today: Windows as a service strategies, tactics, best practices: Dave Backman, Namrata Bachwani, Roy Barton Windows update monitoring and reporting: Charles Inglis Windows app development (+ update monitoring and strategies): George Nelson Expediting updates in Microsoft Endpoint Manager: David Guyer Windows 10 deployment: Steve Thomas Cloud-based update management, Windows Update for Business: Aria Carley, Kay Toma Microsoft Endpoint Manager: Jason Sandys Microsoft Endpoint Manager (public sector, CMG, tenant attach, etc.): Danny Guillory Configuration Manager: Rob York, Bruno Yoshioka FastTrack: Kevin Mineweaser Security: Rick Munck Our next, regularly scheduled office hours event will take place on Thursday, June 17th, 9:00-10:00 a.m. Pacific Time. Add it to your calendar. For an up-to-date list of future events, see the Windows IT Pro Blog.950Views4likes0CommentsOffice hours are closed: February 18, 2021
Office hours are now closed. We hope we were able to answer your questions and provide tips and resources to help you more easily manage Windows 10 updates and your Windows device estate. The experts and engineers who supported today's session were: Windows as a service strategies, tactics, best practices: Dave Backman Windows 10 servicing tech: Namrata Bachwani Windows setup: Steve DiAcetis Windows 10 deployment: Steve Thomas Cloud-based update management, Windows Update for Business: Aria Carley and David Mebane Microsoft Endpoint Manager: Joe Lurie and Jason Sandys Microsoft Endpoint Manager (public sector, CMG, etc.): Danny Guillory Configuration Manager: Rob York Security: Rick Munck and Roy Barton Product feedback: Kevin Mineweaser FastTrack: Sean McLaren Office hours at Microsoft Ignite in March To ensure there is plenty of time for Q&A at Microsoft Ignite, March 2-4, we'll be holding four special editions of office hours during the conference. Select any and all of the desired times below to join us! March 2 – 1:00-2:00 p.m. Pacific Time March 3 – 8:00-9:00 a.m. Pacific Time March 3 – 5:00-6:00 p.m. Pacific Time March 4 – 8:00-9:00 a.m. Pacific Time Save the date for future events Our next, regularly scheduled office hours event will take place on Thursday, March 18th, 9:00-10:00 a.m. Pacific Time. Add it to your calendar. For an up-to-date list of future events, see the Windows IT Pro Blog. See you next time!1.5KViews4likes0CommentsMicrosoft will NOT be pushing out the new Edge via Windows Update to everyone
So previously there was this post from this source saying Microsoft will be pushing out the new Edge via Windows Update to the majority of Windows 10 users, but the documentation on Microsoft's website has changed now, here are the newly added information: Update 01/09/2020 To help our customers become more secure and up-to-date, Microsoft will distribute Microsoft Edge (Chromium-based) to Home and Pro Edition devices running Windows 10 version 1803 via Windows Update. This process will start after January 15th, 2020 and more information will be available on that date. The Blocker Toolkit is intended for organizations that would like to block automatic delivery of Microsoft Edge (Chromium-based) on devices running Windows 10 version 1803 and newer that are running the Home or Pro Edition of Windows. All other versions and Editions of Windows are excluded from being updated automatically. Devices running Windows 10 Home or Pro Edition that are joined to an Active Directory or Azure Active Directory domain, are MDM managed, or are WSUS or WUfB managed, will also be excluded from this automatic update." No enterprise versions of Windows will be automatically updated, meaning the Blocker Toolkit is just needed if you run Home and Pro on your enterprise network, and if they are not joined to a Domain. https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-blocker-toolkit5.1KViews2likes6Comments26H2 → 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.124Views1like4CommentsCrowdStrike 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.251Views1like1CommentUnable to deploy out of band update 26200.7628
Hello, I need to deploy OOB 26200.7628 on our computers. We use deployment rings. The 2026.1 OOB update appeared in Releases on January 24. I created an expedite policy with a group of users I want to target with this update (with a restart within 0 days). But nothing has happened since Monday, everyone is still on 26200.7623. Where am I going wrong? Thank you.Solved1.2KViews1like6Comments[On demand] AMA: Managing Windows updates
Tune in to Tech Community Live on demand. Get tips on how to easily manage updates for your Windows devices. And, don’t worry if you missed the live stream. Q&A is open through Friday (12/5) at 12:00 p.m. PST so keep those questions coming! Go to https://aka.ms/AMA/WindowsUpdate to post your questions.101Views1like0Comments
