Confirmed fixed on the machine that reported it.
v3.0.0 disabled the Windows Update services instead of just stopping them, which holds on most machines. On some it didn't — everything switched back on about ten minutes into a session, exactly as before. This release adds the tooling to find out why on a given machine, and a way through when the answer is Windows Update Medic.
Find out what's undoing it
scripts/Trace-QuietReverts.ps1 — read-only forensics. -Verify told you that something reverted; this tells you who.
It reads the Windows event logs that record a service being re-enabled — including Service Control Manager event 7040, the definitive record — plus the WaaSMedic and Task Scheduler logs, and lays them out as a timeline against what the kit did. It ends with a verdict pointing at one of four causes.
Run it elevated. The WaaSMedic tasks are invisible to a normal user and will look absent when they aren't.
Force it when the answer is Medic
On some builds WaaSMedicSvc's registry key is owned by TrustedInstaller and refuses to be disabled even as SYSTEM. Windows Update Medic then keeps repairing the update stack mid-race.
Pre-Race-Quiet.ps1 -UnlockMedic takes ownership of that one key, disables the service, verifies the write actually took, and hands ownership straight back in the same run. The original security descriptor is captured before anything changes and saved in two places. Post-Race-Restore verifies the permissions and owner are back, and refuses to delete the snapshot while any key remains unrestored.
There's also an optional scripts-medic-unlock/ pair with that behaviour on by default, for handing to someone who's already confirmed it's their problem.
Only use it if you've confirmed you need it. Run Trace-QuietReverts first. If it points at Group Policy or an MDM profile instead, the unlock won't help — a managed machine re-applies those settings regardless.
Upgrading from v2.x
Two things need your attention:
Post-Race-Restore.ps1is required, not optional. Quieting disables services rather than stopping them, so nothing self-heals on reboot. Skip the restore and the PC has no Windows Update and no fresh Defender definitions until you run it.- Don't mix files across versions. Six scripts share
scripts/X3D-Profiles.ps1— replace the whole folder. A partial upgrade produces wrong core numbers silently.
Coming from v2.1.0 or earlier, this also brings full support for every X3D AMD has shipped — 6-core through 16-core, the dual-cached 9950X3D2, the mobile HX3D parts, and non-X3D CPUs for the general fixes. See RELEASE-NOTES.md for that detail.
Guide: https://no6969el.github.io/iracing-x3d-tuning/
Requires Windows PowerShell 5.1 (built into Windows 10/11). PowerShell 7 is not needed.