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.Pascal (10 series) GPUs on Windows 11 encounter artifacting boot loop when HDR is enabled in Windows
Bug: Users with Pascal (10 series) GPUs on the latest builds of Windows 11 are encountering an issue with an infinite boot loop that shows artifacting on screen when HDR is enabled in Windows 11. Workaround: Disable HDR in Windows 11 User reports: https://www.reddit.com/r/WindowsHelp/comments/1t5nt0u/hdr_blackscreen_artifacts_on_boot_after_recent/ https://www.reddit.com/r/pchelp/comments/1ngqsze/artifacting_and_crash_during_windows_boot_caused/ https://www.reddit.com/r/pcmasterrace/comments/1u5qfoo/is_my_gpu_doing_or_what/ Report this to NVIDIA: https://nvidia.custhelp.com/app/ask https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/587167/pascal-10-series-gpus-on-windows-11-encounter-arti/ Report this to Microsoft: https://www.reddit.com/r/Windows11/comments/1s0tt03/tip_of_the_week_if_you_want_to_quickly_share/
Microsoft Print to PDF not working/missing.
The Microsoft Print to PDF was not working on my PC so I tried reenabling it via Windows Features in Optional Features and it won't turn back on. It gives error code: 0x800f0922. I also tried other various methods online and none work. All end with various error codes which all result in the service not working/turning on. I even filed feedback about 2 weeks ago with no response yet. I contacted support, where I was recommended to perform a repair via ISO but was then canceled by the agent as I am on an Insider build. I am on build 26300.8687. This is a summary of my diagnostic from Gemini which I had used to try to solve my issue. Here is a summary of the diagnostic, tracking every command I executed in PowerShell and the specific roadblocks the Windows subsystem threw back. The Add-Printer Layer attempted to use modern PowerShell commands to register the printer onto both the interactive prompt port and the standard local file port. Commands Ran: PowerShell Add-Printer -Name "Microsoft Print to PDF" -DriverName "Microsoft Print to PDF" -PortName "PORTPROMPT:" Add-Printer -Name "Microsoft Print to PDF" -DriverName "Microsoft Print to PDF" -PortName "FILE:" * **Errors Faced:** * `ObjectNotFound: (MSFT_Printer:ROOT/StandardCimv2/MSFT_Printer)` * `HRESULT 0x80070002,Add-Printer` --- ## 2. The Legacy PrintUI Layer To bypass the modern PowerShell cmdlet, I tried using the legacy Windows user interface print engine via standard command prompt syntax and escaped quotes. * **Commands Ran:** ```powershell cmd /c "rundll32 printui.dll,PrintUIEntry /if /b `"Microsoft Print to PDF`" /r `"PORTPROMPT:`" /m `"Microsoft Print to PDF`"" rundll32 printui.dll,PrintUIEntry /if /b "Microsoft Print to PDF" /f "C:\Windows\System32\spool\DRIVERS\x64\3\prnms009.inf" /r "PORTPROMPT:" /m "Microsoft Print to PDF" Errors Faced: A graphical dialog box error: Operation could not be completed (error 0x00000002). The system cannot find the file specified. The Deployment Script Layer (WMI/CScript) I tried deploying the printer using Windows’ built-in visual basic administrative scripts to side-step the user interface layer completely. Command Ran: PowerShell cscript $env:windir\System32\Printing_Admin_Scripts\en-US\prnmngr.vbs -a -p "Microsoft Print to PDF" -m "Microsoft Print to PDF" -r "PORTPROMPT:" * **Errors Faced:** * `Unable to add printer Microsoft Print to PDF Error 0x80041002 Not found` * `Operation PutInstance` * `Provider Win32 Provider` * `Description The system cannot find the file specified. Win32 error code 2` Ultimately, every single command failed with an identical variation of **"File Not Found" (Error 2 / 0x80070002 / 0x80041002)**.
Critical Shell/Explorer.exe Boot Loop and Flickering on Recent Windows 11 Insider Build
Hello Windows Insider Team, I am writing to report a critical UI/system stability issue encountered immediately after updating to and restarting the recent Windows 11 Insider build on my machine. Issue Description: Upon finalizing the update and rebooting, the desktop shell entered an infinite crash loop. The Windows background and active windows were flickering/blinking rapidly, and the Start Menu and Taskbar were completely missing/unresponsive. Key Diagnostics: Task Manager Stability: Interestingly, the Task Manager remained completely stable and unaffected by the flickering, confirming the core OS and graphic drivers were functional. Attempted Fixes: Restarting explorer.exe via Task Manager did not resolve the issue. Attempting to delete the IrisService registry key HKCU > SOFTWARE > Microsoft > Windows > CurrentVersion > IrisService only stabilized the Start Menu for a brief moment before the flickering loop resumed. Resolution: The system was only stabilized after bypassing the UI via Task Manager, booting into the Advanced Startup menu, and performing an "Uninstall latest feature update" rollback to the previous working Insider build. I wanted to bring this to your attention as the crash loop completely breaks usability for users hitting this specific flight. Please let me know if you need any specific diagnostic logs from my previous build state to help isolate the bug. Best regards, Suryanarana N
Accidentally Restored Files from Recycle Bin: Impossible to Distinguish from Existing Files
I accidentally clicked "Restore all items" in the Recycle Bin instead of permanently deleting the files. The restored files were merged back into my original photo folder, mixing with the files I intentionally kept. The photos have very similar filenames, and the restored files kept their original filenames, paths, and timestamps (Date Created/Modified), making them impossible to distinguish from the original files. I also performed other actions afterward, so Ctrl+Z / Undo is no longer available. I already tried multiple AI-assisted troubleshooting methods, including PowerShell scripts, sorting by timestamps, checking Recent Items, metadata filtering, and duplicate detection, but none worked because the restored files appear identical at the filesystem level. Typical solutions fail because: Filename sorting is ineffective. Date Created/Modified does not reflect restore time. The files are not duplicates; they are unique photos I had manually decided to delete earlier. Is there any Windows feature, NTFS journal, Event Viewer log, hidden metadata, shell history, or forensic method that can identify which files were recently restored from the Recycle Bin or detect a "Date Restored" / file movement history? I want to separate and re-delete the restored files without manually reviewing hundreds of photos again. Thank you.
USB Speakers Not Recognizing/Referred to as "Steam Streaming" Devices Following Potential Update
My USB speakers are suddenly not being recognized, and instead are being referred to as "Steam Streaming Speakers/Microphone" in the sound settings. I've tried pretty much everything I can think of, including: Disabling the speakers in settings Unplugging/plugging in Speakers (lights/speaker "pop" occurs, but no sound comes from them) Checking BIOS to make sure Audio Controller was enabled Disabling/uninstalling drivers in Device Manager then restarting Uninstalling device drivers in Device Manager then restarting I've found no fix so far and the most likely option seems to just be it's some weird thing that happened when either Steam or Windows updated. The drivers remain missing whenever I restart my computer, and plugging them/unplugging them gets no recognition whatsoever from the PC. Just wondering if anyone else has had this happen. Dunno if this has anything to do with a Windows Insider update tbqh (as I am in the Insider program and did just received an update for it two nights ago), but it's the only thing I can think of because I updated last night before going to bed and this issue only began today.
