Notice that my version of Windows 11 Pro Insiders Edition going away keeps appearing
I started getting the notice that my version of Windows will expire on August 11 three or four weeks ago. I would go to the Windows update under Settings/System and it would say NO updates are available. About a week ago It finally stated that update 25H2 was available. I would do the update numerous times since and each time I get an error code of 0xc1900101. looking that error code up on the internet said my EFI partition may need to be enlarged. When trying there sequence of steps, my system would not allow for the increasing of the partition. I Chatted with an individual today Aug 6, and she tried to run a couple of diagnostics and neither produced any meaningful results. She then gave a link to this site where she assured me the issue would be resolved. Oh and also she tried to download a new OS but it stopped before the entire MSI file downloaded. Any help/suggestions?
WOA 29639.100 explorer.exe freeze when open some folders
When attempting to open certain folders, File Explorer's CPU usage spikes rapidly, and some or all file items become invisible. Stack traces viewed via Process Monitor reveal that the activity consistently involves the `SetLinkFlags` function shown in the image. Third-party file management tools such as File and 7-Zip operate normally, and issues related to non-system Shell components have already been ruled out by ShellExView. 7zip can show all files normally.
Windows 11 Insider Preview (26H2 - 26300.8935) expires by 08/11, what to do? No updates available
Edizione Windows 11 Home Insider Preview Versione 26H2 Data installazione: 30/01/2026 Data di scadenza della valutazione 11/08/2026 20:09 Build sistema operativo 26300.8935 Feature Pack Pacchetto di esperienze per funzionalità Windows 1000.26100.416.0Windows 11 Insider Setup fails with 0x800B0109 before UEFI disk layout error
Hello, I am unable to upgrade my Windows 11 Insider Preview installation using either Windows Update or the official Microsoft Insider ISO. Current build: Windows 11 Insider Preview 26200.8894 KB5121767 installed successfully UEFI boot Secure Boot enabled TPM 2.0 enabled The setup always ends with: "Windows can't be installed because this PC has an unsupported disk layout for UEFI firmware." However, the Panther logs indicate that this is not the first error. Setup fails while verifying the following Microsoft-signed files: Mitigation.dll Facilitator.dll Both fail with: 0x800B0109 PowerShell Get-AuthenticodeSignature also returns: Status: UnknownError "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider." I have already verified: Official Microsoft Insider ISO SFC /scannow completed successfully DISM /RestoreHealth completed successfully Component Store is healthy Secure Boot enabled TPM 2.0 enabled Based on the logs, it appears that Setup fails during Authenticode verification before displaying the UEFI disk layout message. Has anyone seen this on recent Insider builds, or is this a known Setup issue? Thank you.
Urgent: Stuck KB5094126 (2026-06 Security Update) Loop on ASUS M413A
Hello, I have a very urgent issue. I am running an ASUS M413A Model M413IA-EB211T laptop running in the Windows 11 Insider Preview program. Right now, my machine is caught in a persistent and highly aggressive background update loop regarding the June 2026 Security Update KB5094126 for OS Build 26200.8655. The core background engines wuauserv and usosvc continually flip themselves back to Running and Manual/Automatic via background kernel self-healing routines. They are completely ignoring manual user flags to stay disabled via standard sc config commands. Because my system utilizes 8 GB of total RAM with shared integrated graphics, this ongoing background processing loop completely bottlenecks my remaining usable memory. This is throwing my processor usage to 100 percent and causing extreme, loud cooling fan strain whenever the AC charger is plugged in. Furthermore, the loop is continually eating 5 to 12 GBs of data at every single automatic download attempt, creating massive network usage and consuming massive storage bandwidth. My Exact System Specs: Device Name: LAPTOP-S4R984K2 Processor: AMD Ryzen 7 4700U with Radeon Graphics 2.00 GHz, 8 Cores Installed RAM: 8.00 GB 7.42 GB usable due to integrated hardware reservation Graphics Card: Integrated AMD Radeon Graphics 496 MB dedicated video cache System Type: 64-bit operating system, x64-based processor Storage Environment: 226 GB used out of 477 GB available total capacity What Actionable Steps I Am Seeking from the Community: Question 1. July Update Availability Check: Is there a way to safely skip this broken June patch and download the July updated version directly for my specific environment: Windows 11 Insider Preview Build 26200.8655? Question 2. Safe Standalone Roadmap: If I must install this, what is the exact method to download the correct standalone package for KB5094126 and initialize it manually without using the broken Windows Update pipeline? Question 3. Enforcement Command: What exact script can I deploy inside an elevated Administrator Command Prompt cmd or anywhere else to forcefully inject a registry block or anything else that stays active for as long as I put it? It must survive the aggressive Insider kernel health loops and hold the block long-term without risking database corruption or triggering automatic system overrides? Question 4. Cache and Datastore Maintenance Question: Is there any safe method to clear out the active transaction log database handles inside C:\Windows\SoftwareDistribution\DataStore\Logs? Could these lingering handles be the underlying reason why this build is failing to process the install, and how can they be purged without risking database corruption or a forced recovery loop? CRITICAL CONSTRAINT — Strict Risks I Must Avoid: I am completely refusing to do an In-Place Upgrade, a total system reset, or utilize the built-in Fix problems using Windows Update recovery utility. I need the forum experts to provide a path that completely guards against the following risks: Risk 1. System Freeze and Repair Loops: Falling into a mid-way installation freeze or an endless Automatic Repair boot loop where the machine fails to load back to the desktop. Risk 2. Display and Brightness Driver Corruption: Resetting, updating, or modifying my legacy display driver configuration. Any driver modification will immediately re-trigger unreadable thin system fonts, highly oversaturated display graphics, or high brightness spikes. Risk 3. Loss of Custom Profiles: Overriding my fine-tuned power slider behaviors, custom screen brightness thresholds, or my explicitly disabled auto-brightness/adaptive content feature tags. I must avoid resetting any of these features, as simply changing the brightness level itself causes a severe brightness spike. Complete Ledger of Troubleshooting Steps Taken So Far All Failed or Reversed: Step 1. Cache Purges: Cleared out the SoftwareDistribution Download folder, but the text entry remains stuck on the Settings app screen. Step 2. File-Level Permission Locks: Used icacls to deny the local SYSTEM account permission to execute wuaueng.dll. This successfully froze the loop for exactly 3 days until the automated 3-day Insider system health check forcefully restored factory permissions and restarted the services. Step 3. Firewall Barriers: Set up outbound Windows Defender Firewall block rules targeting the specific update services, which were actively bypassed by alternative network pipelines inside svchost.exe. Step 4. Service Configurations: Regularly deployed combination scripts to stop and disable wuauserv, usosvc, and bits via command line, which are immediately overwritten by the Insider kernel health loops. Step 5. System Health Restore and Scan Results: Ran standard administrative system repairs sfc /scannow and DISM /RestoreHealth. The tools reported that they successfully repaired something in the background, but the scan logs were completely unclear as to what was fixed, and it did not resolve the update loop. How can I safely acquire the standalone update package and force-install it without risking my current display profiles, causing a system freeze, or forcing an in-place operating system upgrade? Please let me know as soon as possible, I have been dealing with this for at least a month or longer.
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.New Outlook Unable to Close Since build 26220.8754 Update
Since build 26220.8754, I (and others) have been unable to close New Outlook using the X. I went into Windows Settings > Apps > Installed Apps > Outlook > click the 3 dots to the far right, select Advanced Options. Then select Reset. It worked for 1 time, but then the issue just showed right back up. I am not the only one with this issue, it has been reported here https://learn.microsoft.com/en-us/answers/questions/5933524/new-outlook-doesnt-close-with-x-any-longer?source=docs
