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.