Changelog

What changed.

The one command fetches the newest script that passed the Windows check, every run, so every entry here reaches you the next time you run it, on the same key, for nothing.

OmniDx Edition 1.32.0 · October 2026

Game Boost is gone, and nothing of OmniDx touches a game while it runs

  • A Fortnite player was removed from a match by Easy Anti-Cheat ("Forbidden tool") with Game Boost on the PC. Game Boost changed the game in front from outside: its priority, Windows' power throttling and its graphics priority, through a handle to the game's own process. That is the kind of thing an anti-cheat can take for a tool against the game, so Game Boost is removed completely: its switches, its timer, its Efficiency mode for other apps and its quiet Wi-Fi. Updating turns off the switches an earlier Edition left on and puts back the power plan it had swapped in
  • The boost that stays needs nothing running: Games First has Windows itself start every game at high priority, never power-throttled and on the fast graphics card, from Windows' own settings. Nothing of OmniDx opens the game
  • While a game or its anti-cheat is running (Easy Anti-Cheat, BattlEye, Vanguard, FACEIT, EA's and others), the Hub opens no other program at all: the Running page lists programs by name only and closes nothing, the busy check and the driver-delay measurement wait until you close the game, and the mouse test reads the mouse only while its own window is in front
  • The Measure page no longer starts a recording: a recording reads the game while it runs. Runs you saved with the free bench still show there
v1.117.3 · October 2026

The tune's text says what the Edition is now

  • The finish screen and the Info tab no longer list Game Boost (OmniDx Edition 1.32.0 removed it): the Hub's presets, what is running, drivers, overclocking guides and the connection page, and nothing of it touches a game while it runs
v1.117.2 · October 2026

Apps install on a brand-new PC too

  • On a fresh Windows, winget (Windows' App Installer, which the clean installs use) comes with Windows but is only switched on for your account once the Microsoft Store has updated it, which can take hours. Apps, installed clean then stopped and sent you to the Store. It now switches winget on itself, the way Microsoft documents it, and if this Windows has no App Installer at all, adds it with Microsoft's own WinGet module
v1.117.1 · October 2026

No window at the sign-in after installing apps

  • After installing apps clean, the tune looks once more at the next sign-in for anything an app put back at startup the first time it opened, then that one-time task removes itself. Its PowerShell showed an empty window for a moment, three minutes after that sign-in, over whatever was open. It now starts with no window at all, the way the after-restart count does
v1.117.0 · October 2026

Nothing of the tune left running at sign-in

  • The keep task is gone. It ran three minutes after every sign-in to put back what a Windows update turned on, so a hidden PowerShell started each time, games or not. Now nothing of the tune stays to run at sign-in or in the background: the only task a run leaves is the after-restart count, which runs once and removes itself. A run removes the keep task an earlier version left, and no longer asks about it
  • After a big Windows update, status says what came back and running the command again puts it back, same key, free. With OmniDx Edition, the OmniDx Hub checks when you open it and puts it back in one click. C:\OmniDx\undo\keep.ps1 stays, for running by hand; with -Check it only looks
  • Fixed: status, which runs without administrator rights, could list a setting as drifted when Windows simply would not let it read the value (some keys read only for administrators). Those are now left out instead of called missing
OmniDx Edition 1.31.1 · October 2026

One process fewer at the sign-in after setup

  • The welcome's check at the sign-in after setup asked Windows' management service (WMI) when the PC started, and that leaves a WMI host process running for minutes after the question. It now reads how long Windows has been up, which needs no other process
OmniDx Edition 1.31.0 · October 2026

After a Windows update: the Hub checks when you open it

  • New on Home: when you open the Hub it asks the tune, once and reading only, whether a Windows update turned any of its settings back on. If one did, a strip says how many and which, with Put them back: one click, as administrator, and it checks again. Nothing of OmniDx runs at sign-in or in the background to watch for updates (the tune's sign-in task is gone since Tune 1.117.0)
  • The check runs only when the tune has left records on the PC, with no window and below normal priority
  • Games First no longer runs at sign-in. Its task ran a minute after every sign-in to catch games installed since; it now has no trigger and runs only when asked: when you open the Hub and it finds a game installed since the last run, or from the Games page. Correction: 1.30.0 said nothing of the Edition was left at sign-in, but this task still was. Now nothing is
  • Fixed: freeing memory and putting new games first opened a console window for a moment, also during a game when Game Boost empties the standby list, where a new window can take the focus from the game. OmniDx's tasks now start with no window
  • Fixed in the Edition check: the welcome's test waited for the welcome window it had just opened, which nobody closes
OmniDx Edition 1.30.0 · October 2026

Nothing of the Edition left at sign-in

  • The Hub's welcome after setup's restart used a sign-in task that stayed: at every later sign-in it started a hidden PowerShell that found the welcome done and closed. It is now one entry Windows deletes as it runs it, and the Hub makes the check itself (no window, no PowerShell). Before the restart it waits for the next sign-in only. (Corrected: this card said that once the welcome had shown nothing of the Edition started with Windows, but Games First's task still ran at sign-in; it stopped in 1.31.0)
  • Setup removes the old task and its script on PCs that had them
OmniDx Edition 1.29.0 · October 2026

Windows Security stays kept, whatever the path says

  • Starts with Windows keeps Windows Security's entry and your antivirus's with no switch. An entry whose program cannot be found is marked as a leftover and suggested off, and until now that rule came first: one of those entries with its program not found where it points would have lost its protection. They now stay kept and are never suggested off; the Edition check plants one to prove it
OmniDx Bench 1.2.0 · free · OmniDx Edition 1.28.0 · October 2026

Did Windows' desktop add a frame of delay?

  • The bench's verdict, and the Hub's Measure page, now say how your game's frames reached the screen, from PresentMon's own reading for each frame: straight from the game (exclusive fullscreen, or a borderless window Windows lets flip on its own) or drawn again by Windows' desktop, which adds about one refresh of delay
  • When the desktop drew them, it says what lets the game show its frames itself: exclusive fullscreen, or borderless with Optimizations for windowed games on, and nothing (an overlay, another window) drawn over the game
OmniDx Edition 1.27.0 · October 2026

Your Wi-Fi's signal and band, before the match

  • On Wi-Fi, Check before a match now shows the signal and the band in its connection line, as Windows reports them
  • Under 60% (about -70 dBm, where a match starts losing packets) it says the signal is weak and what helps: closer to the router, nothing metal or a wall in between, or a cable. On 2.4 GHz it says so: the band microwaves, Bluetooth and neighbouring networks crowd, so 5 or 6 GHz is better when the router has it
OmniDx Edition 1.26.0 · October 2026

Lag in your home, or past your router

  • Check before a match pings your router at the same time as the internet. When packets are lost or the line is unsteady, it says where: lost or unsteady to the router as well, the trouble is in your home (the Wi-Fi, the cable or the router itself); clean to the router, it is past it, at your internet provider or in a download filling the line
  • Fixed: on a network that drops pings, as some routers, firewalls and providers do, the check said No answer from the internet while the internet worked. When the first three pings get no reply it now times opening connections instead, as the Connection page already did, and says so
  • When the internet really is down and the router still answers, it says so, with what to restart
  • Corrected: 1.25.0 said the busy-line check names the program moving the most data. On Windows that count is given only to administrators: the counters any program can read missed nearly all of a download's traffic in the Edition check, so nothing was named. It now lists the known background downloaders with a connection open to the internet, which needs no administrator rights, and says so when none is open
OmniDx Edition 1.25.0 · October 2026

A busy internet line, caught before the match

  • Busy right now and Check before a match also read the internet line over the same two seconds: this PC's own traffic, in and out, through the adapter its internet goes through. A launcher downloading an update, cloud storage syncing, a torrent seeding or a backup uploading fills the line, and every packet of a match then waits behind it as lag spikes, whatever the processor is doing
  • When the line is busy it lists the background downloaders with a connection open to the internet (Steam, Epic, Battle.net, OneDrive, torrent clients and the rest), as the likely ones. Read without administrator rights, from Windows' own counters and connection table. (Corrected in 1.26.0: this line first said it named the program moving the most data; see there)
  • New in its list, with what to do: Ubisoft Connect, the Riot Client and the Xbox app downloading, torrent clients, and Dropbox, Google Drive, iCloud and MEGA syncing
OmniDx Edition 1.24.0 · October 2026

The graphics card in Busy right now, and a game's own fixes a right-click away

  • Busy right now (and so Check before a match) also reads each program's share of the graphics card, from the counters Task Manager's GPU column reads, as Task Manager shows it: its busiest engine. A browser playing a video, an animated wallpaper or a recorder now shows up before a match even when it barely uses the processor
  • New in its list, with what to do: NVIDIA's overlay or Instant Replay recording in the background, Medal recording clips, Overwolf's overlays, and Wallpaper Engine
  • A right-click on a game in the Games page: play it, its settings, verify its files in Steam (the usual first fix for a game that crashes in its own code), open its folder, and why it crashed when Windows logged it
  • OmniDx Browser: an address typed into a new tab in the split second its engine finished starting was replaced by the new tab page. It now waits for the tab and opens, as it does a moment earlier or later
OmniDx Edition 1.23.0 · October 2026

What starts at sign-in without telling Task Manager

  • Starts with Windows now also lists other companies' scheduled tasks that start a program at sign-in or start-up: the updaters and helpers Task Manager's Startup tab never shows. Each has a switch (it asks for administrator rights), and one that switched itself back on after an update is marked
  • It follows the tune's own rules: Microsoft's tasks, OmniDx's, tasks that run a script and programs signed by Microsoft are left out, and anti-cheat, thermal and fan control, touchpads, VPNs, remote desktop and the laptop's own controls are kept with no switch
  • Check before a match also says what the Hub measured before: a mouse reporting below 500 Hz, and a spike from the wake-up test, with the way to the driver behind it
OmniDx Edition 1.22.0 · October 2026

Crashes where you look for them

  • OmniDx Hub's Games page marks each game Windows logged crashing or freezing in the last 30 days with a Crashed tag; a click on it opens the Drivers page, which says where it crashed and what usually fixes it
  • The Home page shows a strip when Windows logged blue screens, power-offs without a shutdown, processor or memory errors, or graphics driver resets this week, with the way to what causes them
  • Home, Games and Drivers share one read of Windows' logs, kept ten minutes, so opening them stays quick
v1.116.0 · October 2026

Network numbers on networks that drop pings

  • Some routers, firewalls and providers drop pings. There the free look said only that the router or the internet did not answer. Now it times opening a connection instead (the handshake is one round trip): the router's DNS port, else its web page, and 1.1.1.1's HTTPS port, and says it did
  • Packet loss to the internet now says where it starts: when the router answered every time it is past the router, at the line or the provider; when the router lost some too, it starts in the home, on the Wi-Fi, the cable or the router
v1.115.0 · October 2026

Your drives' health, and shaders delivered compiled on AMD Radeon

  • New: the tune reads each drive's health, in the free look too. Windows' own verdict for the disk, and the drive's own counters: how much of its rated life it has used, its temperature against its rated limit, and reads it could not correct. A drive that is failing, worn out or running hot gets a plain warning, because no tweak helps a failing drive
  • New advice on Windows 11 24H2 and later with an AMD Radeon RX 5000 to 9000 (or a Radeon 680M to 890M laptop chip) and the Xbox app: Microsoft's Advanced Shader Delivery. Games from the Xbox app that support it download their shaders already compiled, so the first minutes do not stutter and loading is far shorter (Forza Horizon 6 first)
  • It switches itself on with AMD Software 26.6.1 or newer and Gaming Services 37.113 or newer; the tune reads the Gaming Services version on your PC and says when it needs an update from the Microsoft Store. Games from Steam and other launchers compile their own shaders, as before
OmniDx Edition 1.21.0 · October 2026

Check before a match

  • New on OmniDx Hub's Home page: Check before a match. One press, a few seconds, and a line for each thing that can cost a ranked game, the ones to fix first
  • It reads what runs in the background over two seconds and whether Windows Update is installing or waiting for a restart; the charger and the power plan; each screen's refresh rate against its monitor's best; free memory; Game Mode; the connection over five pings (lost packets, jitter, Wi-Fi or a cable); and room on Windows' drive
  • Each line that needs something has its fix one click away: the Running page, the Display tab that raises the refresh rate, Free up memory, the Connection page, or the Windows setting itself. It changes nothing by itself
v1.114.0 · October 2026

What crashed, and why, in the tune's own report

  • New: the tune reads what Windows logged over the last 30 days and says it in plain words, in the free look too. It reads only, and no tweak is pretended to fix any of it
  • Errors your processor, memory or a PCI Express slot corrected by themselves: the classic sign of an overclock, undervolt or memory profile (XMP/EXPO) that is not stable, often before anything crashes, with what to try first
  • Blue screens by their code (0x124 a hardware error, 0x133 a driver holding the processor, and others), power-offs without a shutdown, and graphics driver resets
  • Each game that crashed, how often, and where: in NVIDIA's, AMD's or Intel's graphics driver, in an overlay such as Steam's or Discord's, in its anti-cheat, or in its own code, with the fix for each. Programs that are not games are left out
OmniDx Edition 1.20.0 · October 2026

Why a game crashed, and how your drives are doing

  • New on the Drivers page: Crashes and hardware errors over the last 30 days, the most serious first, each in plain words with what usually causes it. It reads only what Windows already records, and changes nothing
  • Each game that crashed or froze, how often, and where: in NVIDIA's, AMD's or Intel's graphics driver (a clean driver install), in an overlay such as Steam's, Discord's or RivaTuner's (turn it off for that game), in its anti-cheat, or in its own code (verify its files)
  • Graphics driver resets (the black screen for a moment), blue screens named by their code (0x124 is a hardware error, 0x133 a driver holding the processor, and others), and power-offs without a shutdown
  • The errors your processor, memory or PCIe slots corrected by themselves: the sign of an overclock, undervolt or memory profile (XMP/EXPO) that is not stable, often before anything crashes. With what to try first for each
  • A Reliability Monitor button opens Windows' own timeline of the same events
  • New on the Drivers page: Drives. Each disk (NVMe SSD, SSD or hard disk) with Windows' own health verdict, how full each drive is and which games are on it. An SSD past about 85% full writes slower and makes a game stutter while it streams in or updates, so the page says when to free space; it also names games on a hard disk, and a Windows drive under 20 GB free
  • One button (administrator) reads each drive's own counters: how much of its rated life it has used, its temperature against its rated limit, and reads it could not correct, with a warning when a drive is failing, worn out or running hot
OmniDx Edition 1.19.0 · October 2026

What starts with Windows, in OmniDx Hub

  • New on the Running page: Starts with Windows lists every program Task Manager's Startup tab lists (the Run entries, the Startup folders and Store apps like Spotify), what each one is, and a switch for each. The switch writes what Task Manager writes, so Task Manager and Settings show the same; nothing is uninstalled
  • Apps such as launchers and chat apps can switch themselves back on after an update. One you switched off in the Hub that is on again comes first, marked, so you can see it and switch it off again
  • Each entry says what it is, and the ones gamers meet most come with a note: launchers, chat and browsers starting themselves are suggested off (one button switches them all off), while sound, touchpad, anti-cheat and MSI Afterburner entries say when to leave them on. An entry whose program was uninstalled is found and suggested off
  • Windows Security's entries and antivirus are never switched: they show as Kept, with no switch
v1.113.0 · October 2026

Games on a hard disk, and Windows' own Xbox mode

  • New: the game profiles name every game installed on a hard disk rather than an SSD. A game there loads slowly and stutters while it streams its world in, whatever is tuned; the line says how to move it (Steam: the game's Properties, Installed Files, Move install folder)
  • New advice on Windows 11 24H2 and 25H2: Xbox mode, Windows' own full screen experience (Settings, Gaming, Full screen experience, home app Xbox, then Win+F11), which holds Windows' background work back while you play. Microsoft is rolling it out gradually, so the line says the page may not show yet, and it says when the Xbox app it needs is not installed
v1.112.0 · OmniDx Edition 1.18.0 · October 2026

Every game's settings, checked again, and in OmniDx Hub

  • Fixed: the Counter-Strike 2 notes suggested the -allow_third_party_software launch option. It turns CS2's Trusted Mode off, which can cost Trust Factor and put you in lobbies with less trusted players. The notes now say to leave it out, and name CS2's real video settings (Boost Player Contrast, NVIDIA Reflex Enabled + Boost) instead of a multicore setting CS2 does not have
  • Fixed: Roblox's notes now point to its own Maximum Frame Rate setting (Esc, Settings), which raises the 60 FPS cap up to 240, instead of Reduce Motion, which is an accessibility setting and does nothing for frames
  • Fixed: Rust's notes no longer list -malloc=system and -force-feature-level-11-0 from old guides; Fortnite's name the rendering mode as the game does now (Performance) and give a clear frame-rate limit; Dead by Daylight's drop a claim about its engine that could not be backed up
  • OmniDx Hub, Drivers page: Shader caches shows how much the graphics drivers keep (DirectX's own, NVIDIA's, AMD's, Intel's) and clears it when you ask, with a question first. It is the known fix when a game stutters, shows broken graphics or crashes at launch after a driver update; the first minutes of each game compile again. It never clears by itself
  • OmniDx Hub, Running page: Busy right now reads what uses the processor or the disk over two seconds, names the service behind each Windows service host (Windows Update, Delivery Optimization), and says in plain words what each one is and what to do: let an update finish, pause a download or OneDrive, close a busy tab. Microsoft Defender is named and left alone
  • OmniDx Hub, Games page: every game OmniDx has notes for shows a Settings tag, and a right-click opens what to set in its own menu, with a Copy button. The Hub's copy is written from the tune's own list by a tool, and the check fails if the two ever differ
OmniDx Bench 1.1.0 · free · OmniDx Edition 1.18.0 · October 2026

The free bench now says what holds your frames back, and measures input delay

  • What set the pace in your minute of play: the graphics card, the CPU (the game's own main thread) or a frame cap, from PresentMon's own split of every frame, and what that means for your settings
  • The PC's part of your input delay: the time from your key press or mouse move to the screen, as PresentMon measures it (median and the slow end). With both runs measured it gets its own row in the side by side and on the result card
  • Read once a second while you play, from Windows' own counters: the CPU held below its rated speed by its own heat or power limit, memory running short, the driver time, and on an NVIDIA card its temperature and any slowing for heat. Nothing is installed for it: no driver, no service
  • The other programs that used the CPU during the game, and which of your stutters came in the same second as heat, power or memory trouble
  • OmniDx Edition 1.18.0: a new Measure page in OmniDx Hub records a game with the bench in one press and lays out every saved run per game, stock against with OmniDx, with the input delay and the latest verdict
  • Fixed: the result card drew a divider under its last row
v1.111.0 · October 2026

Games Windows quietly slowed after a crash, and an old guide's memory setting

  • New: when a program crashes a few times in an hour, Windows puts its crash shim (the Fault Tolerant Heap) on it, and from then on every start pads and delays its memory work. A game that crashed with a driver once too often kept paying for that, and nothing said so. The tune now takes that shim off your games only, every other program keeps it, and Windows puts it back by itself if a game keeps crashing. Undo puts it back as it was
  • The free look lists any of your games Windows has put that shim on
  • New repair: LargeSystemCache=1, a file-server setting some old tweak guides set, makes Windows keep its file cache ahead of programs' own memory, so a game's memory goes first when it runs short. It goes back to Windows' own 0, and undo puts back what was there
  • Undo now puts back a removed binary or multi-part registry value exactly as it was, not as a list of numbers
  • Help in the app is by email now: the Info tab and two help lines no longer point to the Discord
v1.110.0 · October 2026

Lower input delay and more frames: game files, the graphics card's lanes, and laptops' GPU switch

  • Counter-Strike 2 on an NVIDIA card: NVIDIA Reflex is set to On + Boost in the game's own settings file (On on a laptop, where Boost costs battery and heat). Reflex keeps the CPU from queueing frames ahead of the graphics card, which is where most of a game's input delay builds up
  • A game's frame cap left at 60 on a faster screen (Fortnite, Marvel Rivals, PUBG, THE FINALS) is raised to the screen's own rate. A cap you chose above 60, like one just under the refresh rate with G-SYNC or FreeSync, or no cap at all, is left exactly as it is
  • PUBG: Battlegrounds and THE FINALS join the games whose own settings files get V-Sync off and the heavy, low-value effects turned down, backed up first and undone with the rest
  • Fixed: Rainbow Six Siege's V-Sync setting was never written. A one-setting list turned into three loose words on the way in, so nothing matched. The build machine now plants a Siege file and checks it
  • New check: a desktop graphics card running on fewer PCI Express lanes than it has (a lower slot, a riser cable, or lanes shared with an M.2 drive) is named in the report, for every card maker. At x4 or fewer, or on PCI Express 3.0, that costs real frames
  • New advice for laptops with a graphics card: if the laptop's own control app has a MUX switch (Ultimate, dGPU, Discrete or Direct mode), turning it on lets the card drive the screen directly, for more frames and less delay while plugged in
  • Fixed: switching off the Sticky, Toggle and Filter Keys shortcuts also switched those features off for anyone who uses them on purpose. Now only the shortcut goes, and Filter Keys being on is said plainly, because it ignores or slows quick key presses
v1.109.0 · OmniDx Edition 1.17.0 · October 2026

Clean installs, fixed after installing every app on a fresh Windows

  • The build machine installed all 25 apps through the clean install and recorded what each did. The TeamSpeak 3 installer in winget's catalogue installs Overwolf along with it when it runs silently. The list now installs TeamSpeak 6, TeamSpeak's current client, instead
  • New safeguard for every app: anything else an installer adds to Settings > Apps (an offer bundled in) is named in the log, its programs are closed and what it put at startup is switched off. Runtimes an app needs, such as Visual C++ or .NET, are left alone
  • Installers that hand over to a second installer and return straight away (iCUE's, Razer's) are now waited for, up to five minutes (Razer's own window, up to twenty), so the clean-up sees everything they added
  • Battle.net installs now: its installer needs a folder, and it is given one
  • Opera GX and G HUB no longer stay open after installing, Opera GX's assistant updater task goes off (the browser's own updater stays), and a background service an installer started but that does not start with Windows (EA's) is stopped until the app is opened
  • When winget cannot install something, the log says why in plain words, for example that the maker's download link is broken right now
v1.108.0 · OmniDx Edition 1.16.0 · October 2026

Apps already on your PC: marked, and cleaned without installing them again

  • The clean-install list, in the tune app's OmniDx OS tab and on the Hub's Tune page, marks each app that is already on your PC (on this PC), from its entry in Settings > Apps
  • Ticking one of those cleans it without running its installer again: what it put to start with Windows goes off the same way, and its version stays as it is (the app keeps itself up to date)
  • Installing goes faster when you tick apps you already have, and nothing is downloaded for them
v1.107.0 · October 2026

Updaters stay on demand after the program updates itself

  • Some updaters put their version in their service's name (Google's: GoogleUpdaterService156.0.8067.0), so every Chrome update installs a fresh pair of services set to start with Windows, which the keep task never recognised: it only knew the old names. It now treats a newer copy of a service the tune set the same way as the one it replaces, and writes it into the same record, so undo puts it back too. Status names it as well
  • Two clean installs before the next sign-in: the second adds its apps to the first one's once-more check instead of replacing it
  • Every app on the clean-install list is now installed on a fresh Windows by the build machine itself, and the OmniDx Edition page shows what each one added to start with Windows, what went off and what still starts, and why
v1.106.0 · OmniDx Edition 1.15.0 · October 2026

Gamer apps installed clean: from their makers, with nothing of them starting with Windows

  • New on the tune app's OmniDx OS tab, and on the Hub's Tune page: tick the apps you want (Chrome, Firefox, Brave, Opera GX, Discord, Spotify, TeamSpeak, Steam, Epic, Battle.net, EA app, Ubisoft Connect, GOG Galaxy, Logitech Onboard Memory Manager and G HUB, Razer Synapse 4, Corsair iCUE, SteelSeries GG, OBS Studio, MSI Afterburner, HWiNFO, CPU-Z, GPU-Z, 7-Zip, VLC) and press one button
  • Each app comes from its maker's own installer through winget, Windows' own package manager, which checks the installer before it runs. Nothing is repackaged or changed inside the app
  • Then everything the install added to start with Windows is switched off: startup entries (the way Task Manager's Startup apps does it, so you can turn one back on there), background services the app can start again by itself, and scheduled tasks. Discord's and Spotify's own start-at-login settings go off too, so they do not put themselves back, and Chrome and Brave stop running in the background after you close them
  • Browsers keep their updaters, because a browser has to stay patched. G HUB, Synapse and iCUE need their own services running to open or to find your devices, so those stay; for nothing at all running, Logitech's Onboard Memory Manager saves your settings to the mouse
  • An app that adds its start-with-Windows entry the first time you open it is looked at once more at your next sign-in, by a task that then removes itself. An app already on your PC is cleaned the same way. Undo puts back every bit of it
  • From PowerShell: $env:OMNIDX_MODE='apps'; irm omnidx.net/go.ps1 | iex lists the apps and asks which
v1.105.0 · OmniDx Edition 1.14.0 · October 2026

Your monitor's full refresh rate in one click, and your mouse's polling rate measured

  • A monitor that can do 144 or 240 Hz but was left at 60 is one of the most common things we find. The tune's app now shows a button when that is the case: it switches each screen to the highest rate its monitor offers at its resolution and asks you to keep it. If you do nothing for 15 seconds (or the screen goes black), it goes back by itself, the same way Windows' own display settings work
  • The check is per screen now, at the resolution you use. Earlier versions took the highest rate from the graphics card's whole list, which could name a rate your monitor only offers at a lower resolution
  • The Hub's Overclock page has the same one-click fix on its Free first tab, for every screen
  • New in the Hub: measure your mouse's polling rate. Move the mouse in circles for four seconds and it tells you how often the mouse reports to the PC (125 Hz waits up to 8 ms, 1000 Hz 1 ms), and what to change if it is low
  • Fixed: the check for an old guide's forced platform clock (HPET) only recognised an English Windows. It now reads Windows in every language
v1.104.0 · OmniDx Edition 1.13.0 · October 2026

No PIN, a faster start, and the network, power plan and graphics settings checked again

  • Instant sign-in now holds under every power plan: waking no longer asks for the PIN when the Edition's Insane plan or Game Boost's plan is in use, and laptops with modern sleep get Windows' own "If you've been away: Never" too
  • Your start, measured: the report shows how long the motherboard took before Windows began and how long Windows took to the desktop, with anything Windows logged as slowing a start in the last 30 days. The Hub's Tune page shows the same, and whether instant sign-in is on
  • A boot menu that waited 30 seconds for a choice (an old Windows left behind after an upgrade) now waits 3, with the choice still there. Undo puts the old wait back
  • The BIOS checklist's fast-boot item names this PC's own figure, and on AM5 boards with DDR5 it adds Memory Context Restore, which stops the memory training from running again at every start
  • Network: the initial retransmit timeout goes back to Windows' own 1 second. Earlier versions set 2 seconds, a value from Windows 7-era guides that doubles the wait before a lost connection request is resent on Windows 10 and 11. Selective suspend and Realtek's auto disable gigabit go off, receive-side scaling goes on where a driver shipped it off, and Wi-Fi transmit power goes to its highest
  • The OmniDx plan sets the efficiency cores of Intel's hybrid CPUs the same way as the performance cores (no parking, full speed plugged in) and keeps devices out of power-saving idle. On battery both back off as before. A Windows 10 PC with one of those CPUs is told that Windows 11 keeps games on the performance cores, and the Edition's move to Windows 10 says so before it starts
  • NVIDIA: preferred refresh rate set to Highest available for every game, so a game in fullscreen runs at your monitor's top rate. Resizable BAR is read from NVIDIA's own tool and the report says whether it is on. The shader cache advice changes to Driver Default, because current drivers keep more than the 10 GB old guides suggest
  • AMD and Intel Arc: a full settings list for AMD Software and Intel Graphics Software in the report, and which driver to get and how to install it
  • Windows Update on your say-so also holds this Windows version, so no version upgrade arrives by surprise. This version's monthly fixes still install when you press Check for updates, and Defender keeps updating itself. Undo lets the next version come
OmniDx Edition 1.12.0 · October 2026

Find the driver behind stutter, crackle and late clicks

  • The Hub's Drivers page has a new Driver delay card. Press Measure, and for ten seconds it times every short job a driver makes the processor stop for (deferred procedure calls and interrupts, the same events LatencyMon reads). Then it shows which driver held the processor longest, for how long, and what to do about it
  • A driver that holds the processor for a millisecond holds up a frame, a sound buffer or a click for as long, which is where micro-stutter, audio crackle and late clicks often come from. The card grades the longest one: under half a millisecond is good, two milliseconds or more is a stutter
  • Each driver is named by its file and by what it is (graphics, Wi-Fi, Ethernet, USB, storage, audio, power management), with the fix for that kind: the maker's newest driver, a cable instead of Wi-Fi, the BIOS and chipset driver
  • Nothing is installed or changed, and nothing stays running: it uses Windows' own kernel trace for those ten seconds and then stops. If another tool such as LatencyMon is already using that trace, the card says so and leaves it alone. Save the list now includes the measurement
  • When the Home page's wake-up test finds spikes, its link now reads Find the driver and opens the Drivers page with the measurement already running, so you go straight from "something is delaying this PC" to which driver it is
v1.103.0 · September 2026

Nothing of OmniDx runs during a match, even right after you sign in

  • The keep task (the one that puts the tune back after a Windows update) ran three minutes after every sign-in, so signing in and going straight into a match meant it could run mid-game. Now, if a game is running at that point, it waits and does its check once the game has closed
  • How it knows a game is running: it looks for any program Windows starts at high priority for the tune or Games First, the same list your games are on. Waiting costs nothing: a one-minute sleep between looks, for up to three hours
v1.102.0 · OmniDx Edition 1.11.0 · September 2026

The boost needs nothing running, and games keep their shaders

  • Games keep the shaders they compiled. Windows' automatic disk cleanup was emptying the DirectX shader cache, so games compiled their shaders again afterwards, which is the stutter you get in the first minutes of a match. The tune now takes the shader cache out of that automatic cleanup. Disk Cleanup opened by hand can still clear it, and undo puts it back
  • No paging file at all, a leftover from old tweak guides, now goes back to Windows' own setting (System managed) after the next restart. Without one, a game that runs short of memory crashes instead of slowing down. Before, the tune only warned about it
  • OmniDx Browser now notices a game filling the screen by itself and puts its tabs to sleep, including the open one if the game covers it. That no longer needs Game Boost or anything else of OmniDx running, and the open tab wakes up when the game has gone. A browser on a second screen keeps its open tab awake. The Windows check now puts a stand-in game in front and checks both
  • The Hub now says plainly that the boost is built in: every game starts at high priority, never throttled and on the fast GPU. Windows applies that itself as the game starts, with nothing of OmniDx running. Game Boost is now shown as optional extras on top (the finer timer, freeing standby memory, background apps in Efficiency mode). It is the only part that runs a process, one small one, while it is on
  • The Hub's Games page now marks each game Windows starts boosted by itself with a Boosted badge. It is read from the same settings Windows reads when the game starts, so the badge shows what actually applies, not what we hope does
v1.101.0 · September 2026

Discord in one process fewer, with Extreme

  • With Extreme, Discord's graphics part now runs inside its main process, set in Discord's own settings so it holds through Discord's updates. Measured on our test PC: six Discord processes down to five
  • What we tried and left out: folding Discord's network part in as well changed nothing in the same test, so it is not set. Only what measured better goes in
  • The cost, as with Spotify: if your graphics driver resets, Discord closes instead of only its graphics part restarting. Any switches you set in Discord yourself stay, and a run without Extreme takes this one out again
v1.100.0 · September 2026

Spotify in fewer processes, with Extreme

  • With Extreme, Spotify's own shortcuts (Start menu, taskbar, desktop) now start it with its graphics and network parts inside its main process. Measured on our test PC: six Spotify processes down to four, about 60 MB less memory, and the app looks and works the same
  • The cost, said plainly: if your graphics driver resets, Spotify closes instead of only its graphics part restarting. Open it again and it carries on
  • This is the desktop app from spotify.com; the Microsoft Store version takes no such switches and is left as it is. Each shortcut is backed up first, undo puts it back, and a later run without Extreme takes the switches out again
v1.99.0 · OmniDx Edition 1.10.0 · September 2026

OmniDx Browser in fewer processes, Discord's settings that actually apply, and no false warnings

  • OmniDx Browser runs the engine's graphics, network and sound parts inside its main process instead of one process each, and keeps no spare page process waiting. Pages keep their own processes and their sandbox. It is on unless you untick "Fewer processes" in the browser's menu, and if the engine will not start with it, the browser starts without it
  • A tab asleep for half an hour (five minutes while Game Boost is on) now lets its process close too. It keeps its title and address and loads again when you open it. Before, a sleeping tab was frozen but still counted
  • If the browser's engine stops (a crash, or a graphics driver reset), the tabs come back where they were on a fresh engine instead of going blank, and a page whose own process crashed reloads, once. The Windows check now ends the engine on purpose and checks the page comes back
  • Discord's settings were written with a byte-order mark at the front of the file, which Discord's JSON reader rejects, so the tune's Discord settings (no start with Windows, hardware acceleration) most likely never applied. They are written without it now, and so is Spotify's settings file
  • Three warnings that showed on every clean Windows run are gone: Delivery Optimization, the taskbar's Widgets button and Game Bar's presence writer are guarded by Windows itself, so the tune now says so in a plain line instead of listing them under Warnings as if something went wrong
  • System Guard's broker (SgrmBroker) is off the Extreme list. Windows guards it, so it never changed, and it is part of Windows Defender System Guard, which nothing of OmniDx touches
v1.98.2 · OmniDx Edition 1.9.1 · September 2026

Windows 10 with no USB stick, proven start to finish on our test PC

  • OmniDx Edition's option 4 took a Windows 11 test PC to Windows 10 by itself: Windows setup ran through, Windows 10 skipped its first-start screens and signed in, the Edition set itself up, the files on the old desktop and in Documents came back, and the tune ran in Extreme and restarted. Three minutes after that restart: 44 processes, two of them our filming helper, and 1.2 GB of memory in use. The same PC on Windows 11 came to 60 with the tune in Extreme and every More Cuts box
  • What it took: Windows setup refuses its no-questions mode together with an answer file and stood waiting on its own message, so setup now runs in that mode alone and the answer file goes into setup's own working folder, which setup carries into Windows 10 and reads before the first-start screens. Setup now starts about fourteen minutes sooner, with no image to rebuild
  • What stays, said plainly: the old account's folders stay in C:\Windows.old, and folders of their own at the top of C: (C:\Games, say) stay where they are; Windows 11 itself and everything in Program Files go, so apps and games installed there are installed again. The window before the move and the note on the new desktop now say exactly that (the note said games were in Windows.old; they are not)
  • While setup runs, the window stays open and repeats any message setup puts up; if setup ends without restarting, it says why in setup's own words
  • The tune's reference line for a clean Windows 11 with Extreme and every More Cuts box: 60, from the 1.98.1 restart film (65 counted, five of them the film's own)
v1.98.1 · September 2026

Start's search is left alone again: closing it did not hold

  • The restart film with 1.98.0 found Windows starting Start's search again within four seconds of the keep task closing it, so it saved nothing, and the after-restart count, taken in those seconds, came out lower than the PC really was. It is taken out: a PC that ran 1.98.0 gets the flag removed at its next run, and the count no longer closes anything but Resume's helper (which stays closed)
  • The honest number from that film, with Extreme and every MORE CUTS box on a clean Windows 11: 66 counted, five of them the film's own, so 61 for the PC. The storage box and the Wi-Fi sync task did what they said: StorSvc and one task host fewer
  • The keep task's checks of scheduled tasks now go through Task Scheduler itself instead of through WMI, the last of its WMI questions: the film still found two WMI hosts at rest
v1.98.0 · September 2026

Measured: 62 on a clean Windows 11. Then up to ten more gone

  • The restart film on a clean Windows 11 with 1.93.0, Extreme and every MORE CUTS box counted 67 processes three minutes after the sign-in, five of them the film's own helpers: 62 for the PC itself. Everything left was Windows, its security, and the four things below
  • Start's search: Windows loads it at every sign-in and keeps it, SearchHost with six browser-engine processes behind it, seven processes whether or not anyone searches (turning off web results, highlights and cloud search in 1.90.2 did not stop it). With Extreme, the keep task now closes it at each sign-in; it loads again the first time you search, a moment slower that once
  • The keep task no longer asks Windows through WMI (service start modes from the registry, the boot time from the System log, its own console by start time): a WMI question leaves a provider host running for minutes, and the film found two at rest
  • On a PC with no Wi-Fi adapter, Extreme switches off Windows' Wi-Fi sync task, which ran all day in a task host of its own
  • MORE CUTS has a box for Windows' storage service (one service host at rest): it says what you give up, Microsoft Store and Game Pass installs and Settings > Storage, and that Steam, Epic and the other launchers do not use it
  • The after-restart list names what each COM surrogate (dllhost) runs, so the next one can be found
v1.97.0 · September 2026

Three more boxes: the laptop sound suites

  • MORE CUTS has boxes for Nahimic (many MSI, Lenovo Legion, Dell and ASRock PCs), Waves MaxxAudio (many Dell laptops) and DTS sound (many HP, Acer, Lenovo and ASUS laptops). Each runs a service, often with a helper, all day for its speaker effects: one to three processes. Ticked, it starts only when something asks for it
  • Each box says what you give up: the speakers may sound flatter without the maker's tuning and its app stops applying settings; sound itself keeps working. Nahimic has also been behind stutter and crashes in some games. On a desktop Extreme already puts these on demand; on a laptop the tune keeps them unless you tick the box. They wait for the restart, so nothing changes under a song or a call
v1.96.0 and OmniDx Edition 1.9.0 · September 2026

From Windows 11 to Windows 10, with no USB stick

  • OmniDx Edition's one line has an option 4 on a Windows 11 PC, and the tune's OmniDx OS tab a Windows 10 here, no USB button: the PC moves to Windows 10, which runs a few processes fewer at rest than Windows 11 even after the tune (on our test PC, 57 to 60 against 63), and is set up as OmniDx Edition with the tune in Extreme. Nothing to plug in
  • It is Microsoft's own Windows 10 (22H2), the same file Microsoft's Media Creation Tool downloads, found in Microsoft's own list (fetched from microsoft.com over HTTPS) and checked against the fingerprint written there, and its setup must carry Microsoft's signature; a setup folder is built from it on the PC with Windows' own tools, and Windows' own setup installs it in its Keep nothing mode. If setup cannot finish, it puts Windows 11 back by itself
  • Your Desktop, Documents, Downloads, Pictures, Music, Videos and Saved Games come back into the new account at its first sign-in, with a note on the desktop saying what came back; nothing is overwritten. The apps and games installed on C: are installed again. This PC's drivers and Wi-Fi network go with it, and Windows 10 activates from the same licence
  • It says everything first and changes nothing until you type WINDOWS 10: Windows 10's security updates end on 13 October 2026 (Extended Security Updates for home PCs), some anti-cheats and new games want Windows 11, and there is no one-click way back (Microsoft's Windows 11 installer upgrades it again, keeping files). It stops, with nothing changed, on a work or school PC, on battery, or without room
v1.95.0 · September 2026

The after-restart list says which box takes away what is left

  • The list of everything still running after the restart (and the report's own list) now ends with the MORE CUTS boxes that would take something on it away on your PC, and how many processes each: for example NVIDIA's control panel helper (2 processes) or Office's background service (1 process). A service host that also runs other services is not counted, because cutting one of them saves nothing there. Each box in the app still says first what it does and what you give up
  • The after-restart count is now taken three minutes after the sign-in instead of two: by then Windows has finished its own start-up work (the licence check and the update scan, which each run for a minute or two after a restart and then end), so the number is the PC at rest. The restart films have always counted at three minutes
  • The app's target line now follows your ticks: Extreme's own target when Extreme is ticked, less the processes each ticked MORE CUTS box takes away on your PC, so you see how close the boxes you choose bring it
v1.94.0 · September 2026

Two fewer processes on an NVIDIA PC, if you choose

  • MORE CUTS has a new box, NVIDIA's control panel helper: NVDisplay.Container, two processes that run all day on every PC with an NVIDIA card, for the NVIDIA Control Panel, its tray icon and the colour settings it applies at sign-in. Ticked, it starts only when something asks. The driver, G-SYNC and the 3D settings of your games keep working
  • The box says what you give up: the NVIDIA Control Panel does not open and digital vibrance is not applied at sign-in until you untick it and run again. Leave it if you use digital vibrance. It is off unless you tick it, recorded, and undone like everything else
v1.93.0 · September 2026

Two more processes gone by themselves, one more you can choose

  • Resume's helper (CrossDeviceResume) is closed at sign-in. Windows starts it once at every sign-in even with Resume switched off by the tune, and a clean Windows 11 filmed through a restart showed it never comes back once closed. The after-restart count and the keep task close it before they count; only while Resume is off by the tune's own setting
  • Extreme switches radio management off on a PC with no Wi-Fi, Bluetooth or mobile radio at all (a desktop on a cable): it ran in a service host of its own with nothing to switch. A laptop, or any PC with a radio, keeps it
  • MORE CUTS has a new box, opening other PCs' shared folders: Windows' client for shared folders, mapped drives and a NAS, which runs all day in a host of its own. Ticked, it starts only when something asks; the internet, Steam, games and Discord never use it
v1.92.0 · September 2026

Up to eight fewer processes: every Windows service shares its host

  • Since 1.85.0 the tune has let Windows' services share their hosts again, about twenty processes fewer after a restart, but it kept eight in a host of their own: sound, sound devices, the network address, name lookups, Wi-Fi, Bluetooth, WMI and Windows Update. That was up to eight processes at rest, six on a home laptop's after-restart list. They now share their group's host like every other service, which is how Windows itself runs them on every PC with less than 3.5 GB of memory. A PC an earlier run set that way gets Windows' own setting back at the next run; it takes effect after the restart
  • The after-restart count no longer counts itself: it takes the list of processes first, then asks Windows which window it runs in, and leaves out the WMI host that question starts. Before, that host (sometimes two) was counted as if it ran at rest
OmniDx Edition 1.8.1 · September 2026

Nothing of OmniDx runs while you play unless you ask

  • Game Boost is now off unless you switch it on. While it is on, it is one small process (about 20 MB, below your game's priority, never inside the game), and that process now ends the moment Boost is switched off, or 20 seconds after a game started from the Hub closes. Before, once used, it stayed running until you signed out
  • Started for Game Boost, it no longer reads your files for the old search index (a disk walk right as a game started) and no longer takes Alt + Space. Switching Boost off when it was not running no longer starts it
  • Games First, which puts every game at high priority and keeps it out of Efficiency mode, needs nothing running: it is Windows' own per-program settings. Its sign-in check now compares what is installed and ends at once when nothing changed, instead of looking through the games' folders every time
  • The Hub's live numbers pause while a game fills the screen or the Hub is minimised
OmniDx Edition 1.8.0 · September 2026

Games first, from the first frame; nothing a game needs left in Efficiency mode

  • Every game on the PC now starts at high priority, with high disk and memory priority, the moment it opens, by Windows' own per-program setting: nothing of the Edition has to be running, and a game started from Steam, Epic, the Xbox app or its own shortcut gets it the same. Each game is also on Windows' own never power-throttled list, so Efficiency mode never applies to it, in front or alt-tabbed, and it uses the fast graphics card. High, never Realtime: a realtime game starves the mouse, the sound and Windows itself
  • The games come from Windows' own list of games it has seen run, Steam, Epic, Riot, Roblox and the Xbox app, and for an Unreal game its real program rather than the small launcher in front of it. Installers, crash reporters, launchers and anti-cheat are never included, and a priority somebody else already set is left alone. A game installed later is added a minute after the next sign-in, or at once from the Hub's Games page (Put new games first)
  • While Game Boost is on, the programs a game leans on are never left in Efficiency mode, whoever put them there: Steam's client, Discord's and Spotify's voice and playback, TeamSpeak, OBS, the NVIDIA and AMD overlays, RTSS, ExitLag, Voicemeeter and the mouse and keyboard suites. They are also on Windows' never-throttled list. Browsers, launchers' store pages and chat windows still go into Efficiency mode during a game, as before
  • The Edition's undo takes all of it away; the Windows check plants a game, starts it and checks it runs at high priority from its first moment, then checks the undo
v1.91.0 · September 2026

More cuts, you choose: each one explained, with what it saves on your PC

  • A new part of the Tune tab, MORE CUTS, has a box for each thing some people use and others never do: Office's background service, the laptop maker's Dolby sound service, Realtek's audio console helper on a laptop, AMD's External Events Utility, network device discovery, Windows' diagnostic services, and printing even with a printer installed. None is ticked unless you tick it
  • Under each box: what it does, the risk, and what you get, in plain words, and a line read from your own PC that says how many processes it would take away there, that it is not on your PC, or that it shares a service host and so saves no process. On a home laptop with Office, Dolby, Realtek and an AMD chip that is up to ten processes
  • Untick one later and run again, and it goes back to how it was before you cut it. Undo puts back any of them, and the keep task holds them after a Windows update. The Info tab (section 8) and the report say the same things, written from the same list. Windows Security, the firewall and your antivirus are never among them
  • From the one command: $env:OMNIDX_CUT='Office,Printing' before it, with the names Office, Dolby, Realtek, AmdEvents, Discovery, Diagnostics and Printing
Key page · September 2026

Paid? The key page never says otherwise

  • A card payment can take a few seconds to a minute to settle after Square sends you back. The key page used to answer that moment with a refusal; now it says "Confirming your payment with Square", asks again by itself, and shows your key the moment Square confirms. If Square takes longer than about two minutes, the receipt form takes over with your order already filled in, and one press gets the key
  • The order number from Square's email (the code after # in its subject, "Receipt from OmniDx #…"; Gmail shows it as Order number) plus the email you paid with now finds your payment at Square directly, even if you closed the tab before the key appeared. The key page shows where to look, and pasting the email's "View web receipt" link works too
  • A paid order that Square keeps open (a checkout with a delivery step) now counts as paid, and a check that fails on our side is put as ours, never as a problem with your payment; the owner is told at once so it gets fixed
OmniDx Edition 1.7.1 · September 2026

Updating from an earlier Edition works again

  • Setting 1.7.0 up over an earlier Edition stopped at its first step on a real laptop: the earlier OmniDx Search was still running and held its own file, and with one app left in Start a list of shortcuts was read as letters ("Specified cast is not valid"). Setup now closes the OmniDx apps before it builds them, and the Start entry is made correctly. The Windows check now starts an earlier search before setup and fails on either error
OmniDx Edition 1.7.0 · September 2026

Search is Windows' own again

  • Press the Windows key and type, as on any Windows: Start's own search finds your apps, games and settings. It is set to this PC only (no web results, Bing, internet suggestions or ads). OmniDx Search is gone from Start, the taskbar and Windows + S, and nothing of it runs in the background any more
  • Nothing of the Edition runs at rest now. Game Boost's helper starts when you switch Game Boost on in the Hub or open a game from it, and follows your games until you sign out. The Hub's welcome still opens once after the restart, from a small check at sign-in that exits at once afterwards
  • Setting it up again over an earlier Edition takes the old search task, the Windows + S takeover and the policy that switched Windows' search off away by itself
v1.90.3 · September 2026

A Windows Security settings button

  • The app's Tune tab has a button that opens Windows' own Windows Security page, the same one Start opens. The tune still never changes anything there; whatever you change on that page is your own choice, made in Windows' own screen
v1.90.2 · September 2026

Five fewer processes: Start's search stops preloading the web

  • Windows 11 24H2 and later draw the Start search flyout with WebView2 and preload it for cloud and highlights content, so the search brings up five extra browser-engine processes at rest even with Bing already off (measured on a home laptop). The tune now turns off the cloud search, the device history and search highlights, so that content is not there to preload and those five do not start. Typing in Start still finds your apps, settings and files
v1.90.1 · September 2026

The after-restart list names what is inside Windows' own group

  • The biggest line in the after-restart list is "svchost", thirty-odd processes that each host some of Windows' services. The list now names every service running inside them, so the next cut can be chosen by name instead of guessed
  • The app's Info tab says search works the old way: press the Windows key and type (OmniDx Edition 1.7.0 gave search back to Windows)
v1.90.0 · September 2026

Lenovo Vantage off at rest, and a truer after-restart list

  • A home Lenovo laptop's after-restart list showed Lenovo Vantage, the plugin host behind it and Lenovo's telemetry client as twelve processes and nearly three hundred threads. Extreme now sets them to start when asked on a Lenovo whose performance modes and Fn keys have services of their own (and on any Lenovo desktop). The battery limit and the performance modes stay as set, because the laptop keeps them; the report gives the one line that starts Vantage's services when you want to open it. Recorded and undone like the rest
  • The after-restart list puts another company's antivirus in a group of its own. McAfee's firewall host had been counted as Windows, because an antivirus runs protected and shows no folder. The list now says what to do: the tune never removes an antivirus, but a trial you do not pay for can be uninstalled in Settings, and Windows Security switches itself back on
  • Browser-engine processes (WebView2) in the list now name the app they belong to, and console windows name the program that opened them, so the last few processes can be traced to their owner
v1.89.1 · September 2026

The after-restart count, one button away

  • A new button on the Tune tab, After-restart count, opens the real process count and the list of everything still running (both written two minutes after the first sign-in after the tune) in Notepad. Typing the file's path into the taskbar's search box only searched, and Extreme takes that box away; the Info tab now points at the button, and at Windows + R for a line typed by hand
  • The right-hand column of the app scrolls on a short screen instead of cutting its last buttons off
v1.89.0 · September 2026

Windows Update on your say-so

  • Extreme now sets Windows Update to wait for you: nothing downloads, installs or restarts by itself, and the update scans that wake the PC and start their workers in the middle of a game are off. Press Settings, Windows Update, Check for updates whenever you like (once a month is when Microsoft ships its fixes) and every update is there. It has its own box in the app, ticked with Extreme, so it can be left out of Extreme or added to the standard tune (-ManualUpdates, -KeepAutoUpdates)
  • With it, Windows Update never swaps a driver, so the graphics driver stays the one you installed; a new version of Windows waits a year; and Store apps update when you open the Store, unless Game Pass or the Xbox app is in use. The Windows Update service itself stays, Defender is not touched and keeps fetching its virus definitions by itself, and undo puts automatic updates back
  • Every run: Windows Update never restarts the PC by itself while you are signed in. Updates still install as before; the restart waits for one you choose
v1.88.1 · September 2026

Extreme quiets the browser updaters too

  • A real Windows 11 at-rest measurement showed Microsoft Edge's background updater still running after the tune. Edge is on every Windows PC and Chrome on most, and their update tasks are time-triggered and vendor-signed, so the other sweeps left them. Extreme now switches those background-update tasks off; the browser still updates when you open it and Windows Update still delivers Edge, so nothing stays unpatched for long. Recorded and undone like everything else
v1.88.0 · September 2026

Extreme goes after the rest: the target is 60 to 70

  • On a home laptop most of what runs past Windows' own share is other companies' software. Extreme now sets every service another company installed that starts with Windows to start when its app asks: the graphics suite's extras, the PC maker's agents and hub services, RGB and peripheral suites, launchers' and updaters' services. Nothing is stopped mid-run (the restart applies it), each is recorded, and undo puts each back. Left alone: anti-cheat, your antivirus, the graphics driver's core service, fan and thermal control, the touchpad and pen, Bluetooth, the disk controller's service, VPNs and remote-desktop tools, and on a laptop its speaker tuning and the maker's hotkey and battery services
  • Their scheduled tasks that start a tray program at every sign-in or boot are switched off too (a task that runs somebody's own script is left alone), and so are AutoPlay's pop-up, sharing folders from this PC when nothing is shared, and network discovery's publishing
  • Instant sign-in, which comes with Extreme: Windows signs your account in by itself at every start, and waking from sleep asks for nothing, so once it loads you are in. An account with a password types it once in the app (checked before anything changes, kept in Windows' own protected store, never sent anywhere); the PIN stays for Windows + L. Anyone who opens the PC is signed in, which the app says next to the box, and it can be unticked
  • The Info tab has a new section, Extreme: everything to know: the steps to 60 to 70, everything it switches off, what it leaves alone, what you might notice, instant sign-in's trade-off, and how to put it back
v1.87.3 · September 2026

The OmniDx OS tab, word for word

  • The tab's list of what you get says exactly what the Edition does: the taskbar's four pins, Search's web search and quick actions, the browser's blocked trackers and sleeping tabs
v1.87.2 · September 2026

The custom OmniDx OS has its own tab

  • The app's header has three tabs now: Tune, OmniDx OS and Info. OmniDx OS is the custom OS, OmniDx Edition, included with your key: what you get, and three buttons that go straight to the part you want, with your key already in. Put it on this PC (no reinstall, your files and apps stay), Make a USB stick (a clean install, step by step down to the Media Creation Tool and the boot menu), and Take it off this PC (press it twice). It says whether the Edition is on the PC and which version, and Put it on again updates it
  • The Tune tab's OmniDx OS button and the Info tab both open it; Info no longer carries the Edition's steps
v1.87.1 · September 2026

OmniDx Edition from the app

  • A Get OmniDx Edition button in the app opens the Edition in its own window with your key already in it: 2 puts it on the PC as it is, 1 makes a USB stick for a clean install. The Info tab has a new section 3 with every step of both, down to the Media Creation Tool and the boot menu keys, and how to take the Edition off again. After a run the log says the Edition is included, and so does the report's next steps, on a PC that does not have it yet
  • Fixed: Undo every run and What is still in place stayed greyed out after the window opened, until a run had finished. They work as soon as the PC is read, and every button comes back even if reading the PC fails
  • The report and folder buttons share a row (The report, C:\OmniDx) to make room
v1.87.0 · September 2026

An Info tab in the app

  • The window the one command opens has two tabs now: Tune, the app as it was, and Info, which says what to do, step by step. Before you start, the run, the restart, the restore point the tune makes (and how to make one yourself, how to go back to one, and how to reach System Restore when Windows will not start), undo from the app or from PowerShell, what every button and box does, your key, and where to get help. The PowerShell lines sit in boxes you can copy from. On a PC that has never run the tune, the status line points to it
  • The daily key audit now also goes the other way: every key the licence server holds is looked for in every commit ever made to this project, every release and its files, and the public logs of every automated check since the first key was made. A key found anywhere fails the check at once, naming where, never the key
OmniDx Edition 1.5.1 · September 2026

Install it and go: this PC's drivers on the stick, Windows 10 or 11

  • The stick maker asks whether the stick is for this PC and, if so, copies its own drivers onto it: network, Wi-Fi, Bluetooth, sound, storage, chipset, USB, camera, touchpad, fingerprint and sensors. The new Windows installs them at its first sign-in, so the internet works from the first start instead of after Windows Update finds them
  • The disk controller's driver also goes where Windows setup loads it by itself, so setup sees the disk on laptops whose controller Microsoft's media has no driver for (Intel RST or VMD), which used to mean downloading a driver and clicking Load driver
  • On Wi-Fi it offers to save the network too (off unless you say yes): the new Windows joins it by itself, and the file with its password is deleted from the stick at that first sign-in
  • Setup's new drivers step asks Windows Update for the drivers it picks for this PC and installs them while the setup window is open, so the PC is complete at its first real start. Graphics is left to the maker's app or Windows Update on purpose
  • Windows 11 or Windows 10, your pick: the stick maker asks first, every time, says whether this PC can take Windows 11 (TPM 2.0, Secure Boot) and suggests the answer, opens the right Microsoft page, and checks the stick installs the Windows you picked. The Edition page has the same choice with both download pages. On Windows 10 the apps also go on the desktop, and News and interests (a web view running all day), Meet Now and the Cortana and People buttons come off the taskbar. Microsoft's free security updates for Windows 10 ended in October 2025, which setup says at the end; the Known issues page has what that means
  • 1.5.1: Edge's desktop icon stays gone. Edge's updater put it back after a restart; its own policy now tells it not to
  • 1.5.2: when Windows Update wants a restart first, the tune that setup leaves for the next sign-in starts PowerShell by its full path and is retried if Windows cannot start it, the same fix as the tune's 1.85.4
v1.86.0 and Edition 1.6.0 · September 2026

Only games come first

  • Your other games get the game profile too, not only the 49 on the list: the tune finds them through Windows' own list of the games it has seen run, each Epic game's manifest, the Xbox app's game files and each Steam game's own folder (an Unreal game's real program, not its small starter). Each gets high CPU priority, the high-performance GPU and, on an NVIDIA card, the same driver profile as the listed games (maximum performance, low latency mode, high-performance texture filtering). Their helpers, crash reporters, anti-cheat, servers and installers never do
  • The launchers' web views (Steam, Epic, Ubisoft, GOG and Riot store pages and friends lists) run below normal, so a page loading never takes the processor from a game. The launchers themselves are left alone: a game started by a below-normal program would inherit it
  • Security: C:\OmniDx now has rights of its own. The keep task and the after-restart count run the scripts in it as administrator at sign-in, and a folder made at the root of C: lets every account on the PC change what is in it, so on a PC shared with a standard account that account could have edited a script and been run as administrator. Now only the system and administrators change the folder; everyone else reads it. Every run closes it, including a folder an earlier version made. The bench asks for administrator rights for a comparison too, since its runs are kept there
  • Status now says, for the keep task and the after-restart count, whether Windows could start them at their last sign-in, in words ("path not found" and the rest), since a task Windows fails to start leaves no log of its own. The service-host box in the app no longer has its bracket cut off
  • OmniDx Edition on Windows 10, first run on a real install: Windows 10 22H2 from Microsoft's own image, the Edition's setup from the stick, WebView2 installed where Windows 10 lacks it. The stick's answer file now also stops Windows 10's "allow your PC to be discoverable?" panel from opening over setup at the first sign-in
  • OmniDx Edition's Game Boost now also lifts the game itself while it has the screen: high priority, above normal on the GPU's own scheduler (so a browser or a video in the background waits its turn), and never power-throttled onto a slow core, on Competitive and Insane. A browser, video player or office app filling the screen is not taken for a game, a game whose anti-cheat refuses is left as it is, and everything is put back when Game Boost ends
v1.85.4 · September 2026

The after-restart count runs after an Extreme restart too

  • A restart film of Extreme on a clean Windows 11 found the after-restart count task had not run: Windows could not start it at the moment of the sign-in ("path not found"), while the keep task three minutes later ran. Both tasks now start their programs by full path from a folder that exists, a minute after the sign-in, and Windows starts them again up to three times if it cannot the first time
  • Both tasks now also run on a laptop on battery. Windows' default for a task is not to start on battery at all, and the after-restart count had that default
v1.85.3 · September 2026

Every run checked by the licence server, and the example key never works

  • Every run of the tune now asks the licence server, and only a key it issued for a paid order runs, on the one PC it locked to at its first run. Before, a PC already on its key carried on while the server could not be reached; now it waits for the connection and says so
  • The example key the site and the tutorial video showed is refused by the server and the script by name. The site, the video and the app's preview picture show TUNE-XXXX-XXXX-XXXX-XXXX instead
v1.85.2 · September 2026

The after-restart number, measured instead of estimated

  • The restart film ran 1.85.0 on a clean Windows 11: 78 processes three minutes after the sign-in, with the film's own helper among them, against 95 with 1.84.0. Grouping the service hosts takes about twenty off, not the forty 1.85.0 said: services only share a host with others of their own group
  • So the numbers the tune shows are now the measured ones: about 75 after the standard tune and a restart on a clean Windows 11, about 70 with Extreme, about 55 with OmniDx Edition, and the target the run prints for your PC starts from there. The app's box says about 20 fewer
  • No service failed or stopped with the hosts grouped: Windows' own event log from the film's restart has no service errors
v1.85.1 · September 2026

Windows 10, checked

  • The Windows check now also runs on the Windows 10 generation (Windows Server 2022, build 20348), not only on Windows 11's, and every step passes there: the full run with a key, the service-host grouping and the services that keep their own host, the keep task putting back what an update turned on, the status report, a second run, Extreme, undoing the last run, the whole undo with the service hosts split again as Windows had them, and the games' and apps' settings files back byte for byte
  • The script asks for TLS 1.2 itself for the key check and its settings file, as the one command already did: a Windows 10 PowerShell window opened by hand could still offer only TLS 1.0
v1.85.0 · September 2026

About 60 after a restart on every run, with the services that matter kept safe

  • Every run now lets Windows' services share their processes again, as Windows did until 2017 and still does on PCs with less memory: fewer processes after a restart (about twenty, as measured in 1.85.2; this entry first said forty), where only Extreme did it before. A clean Windows 11 comes to about 60 instead of about 100
  • The trade, and how it is kept small: in a shared process one crashing service stops the others with it until Windows starts them again. So sound, the network address and name lookups, Wi-Fi, Bluetooth, WMI (what lighting and monitoring tools crash most) and Windows Update keep a process of their own, set the way Microsoft's own troubleshooting isolates a service, recorded and undone like everything else
  • Crashes are not hidden: the status command lists every service that stopped unexpectedly in the last seven days, and the keep task writes any since its last check into its log. If one keeps happening, -NoGroup (or the app's new "Group service hosts" box, unticked) puts every service back in its own process
  • A Known issues page lists everything known to go wrong with the tune and OmniDx Edition, who it affects and the fix, in the Help menu and the footer. "Everything it touches" lists the services that keep their own process
  • The after-restart target the run shows is recalculated for the grouping (corrected in 1.85.2 to the measured number)
  • Taken out: the feature override 1.84.0 wrote for Resume's helper. Asked directly, Windows showed it never read it; a run removes it from PCs that have it, and OmniDx Edition 1.4.1 no longer writes it. The helper itself runs on some starts and not others, which the known issues page says
v1.84.0 · September 2026

Your drivers, read and checked: graphics, network, audio, Bluetooth, storage

  • Every run and the free report now read the driver behind each graphics card, network adapter, sound device, Bluetooth radio and storage controller: who made it, its version and how old it is
  • A device Windows reports a problem with (a missing driver, a driver that failed to start, a device that stopped responding) is named, with Windows' own reason and where its driver comes from. A device you turned off yourself is left out
  • What it points out: a graphics card on Microsoft's basic display driver (no game runs right on it), a graphics driver older than six months, a network driver older than two years, an audio driver older than three, and an AMD PC without AMD's chipset driver (it is what tells Windows which cores to use)
  • How each graphics card and network adapter interrupts: message-signalled (MSI), answered on its own, or a line-based interrupt it can share with other devices and wait on. A card left on a line is named, with what switches it over
  • The link itself: a cable connection linked at 100 Mbps instead of gigabit (nearly always the cable or the router port), and, when Wi-Fi is the only connection, a 2.4 GHz network or a signal under 60%, each with what fixes it
  • Where your sound goes: when Windows plays it through Bluetooth headphones, the report says so, because Bluetooth audio reaches your ears 100 to 250 ms after the game makes it (footsteps and shots come late), and in hands-free mode it drops to phone quality too. A wired headset or one with its own USB dongle has none of that
  • It only reads. The tune still never installs, removes or changes a driver; the report says where to get each one: the maker's page, or Windows Update's optional updates
  • The report has a Drivers section, the free look writes one too, and the Windows check proves both on every version
  • Fixed: on Windows 11, turning on the optimisations for windowed games replaced the whole of that graphics setting, which switched off Auto HDR for anyone who had it on. They are now added to what is there; the Windows check turns Auto HDR on before the run and fails if it is lost
  • OmniDx Edition 1.4.0: Hub › Drivers shows the same, live, with a button that asks Windows Update which driver updates are waiting for this PC (it installs nothing), and buttons to Optional updates, Device Manager and the graphics card maker's page. Type "drivers" in OmniDx Search to open it
  • OmniDx Edition sets up cleanly on a PC with no internet yet: Search and the Hub build as always and only the browser waits. Windows' own search is replaced only when OmniDx Search is really there, and OmniDx Browser becomes the default only once Windows has WebView2; until then links open in Edge instead of nowhere. The Windows check builds offline on every change to prove it
  • Runs right on more PCs. Started from "Windows PowerShell (x86)", which Start's search also offers, the one command now switches to the 64-bit PowerShell by itself (the 32-bit one sees only half of Windows' settings); a Windows account name with an apostrophe (O'Brien) no longer breaks the switch to administrator. OmniDx Edition's windows fit the screen they open on: the Hub, the Browser and the Search panel were taller than a 1080p laptop at 150 % scaling or a 1366 x 768 screen, with their bottom edge out of reach
  • The network adapter's power saving now goes off on Windows in any language. Energy-Efficient Ethernet, Green Ethernet, interrupt moderation, flow control, packet coalescing and Realtek's and Intel's own savers were found by their English names, which Windows translates ("Ethernet de eficiencia energetica"), so a Spanish or Portuguese Windows kept them all on; they are now also found by the keyword the driver stores them under, the same in every language, set only to a value the driver lists, and put back by undo. The same for touch screens: they were recognised by their English name, so a Spanish or Portuguese touch laptop read as having none and Extreme would have cut its touch keyboard and pen service; they are now recognised by what they report to Windows as hardware
  • Works the same on Windows in any language: the Wi-Fi advice (2.4 GHz band, weak signal) and the Hub's Connection page read Windows' Wi-Fi report by its values instead of its English labels, so a Spanish, Portuguese, French or German Windows gets them too. OmniDx Edition 1.4.1: on a fresh install with no internet at the first sign-in (no Wi-Fi driver yet, the cable not in), the tune waits up to two minutes for a connection and otherwise waits for a later sign-in instead of being lost; and a Hub command that prints a page of errors can no longer freeze the Hub
  • The next film still showed Resume's helper running with the policy in place: the same package entry also gates it on a Windows feature flag, which the tune and the Edition now switch off too (read at the next start). And the Windows check found Windows turns the Internet Explorer engine's cache task back on whenever Edge opens that cache: the sign-in keep task now cuts it again quietly and stops its task host, and Status no longer reports it as if an update had undone the tune
  • Resume's helper (CrossDeviceResume), which kept running after every switch tried so far, is switched off where the shell actually checks: its entry in Windows' own package names the policy Connectivity/DisableCrossDeviceResume, now set by the tune and the Edition. The Edition film also showed two task hosts kept up by three scheduled tasks: the old Internet Explorer engine's cache upkeep goes in every tune, and the Edition also drops the system-sounds agent (its sounds are off) and, on a PC without Wi-Fi, the Wi-Fi cloud sync. The film measured 61 processes at rest, the filming helper's four and a short-lived update among them
  • Fewer processes with the standard tune too: what OmniDx Edition already cut now goes in every run. Click to Do (its AppActions process was still running at rest on the restart film), Recall's component, Windows' AI runtime, the health-and-experiences helper, the compatibility inventory and Resume. The film of a stock Windows 11 went from 150 processes to 100 after the restart before this; Extreme and the Edition go lower
  • On a PC where Smart App Control (or a work or school policy) holds PowerShell in Constrained Language Mode, the one command and the tune now say so in plain words and stop before reading or changing anything, instead of failing halfway. The Windows check runs both in that mode on every version
  • Two helpers that ship inside the drivers themselves get switches in Hub › Running: Realtek's audio helper (two processes; sound and the jacks work without it, only the Realtek Audio Console waits), switched off by OmniDx Edition on a desktop and by the tune's Extreme on a desktop without the Edition, and NVIDIA's Control Panel helper, left on because the Control Panel and digital vibrance need it. Laptops keep both
  • Smart App Control: a clean Windows 11 install starts it evaluating, and if it later switched itself on it would block OmniDx Search, Hub and Browser (they are built on your PC, so carry no publisher signature). OmniDx Edition's setup switches it off while it is still evaluating; Defender, SmartScreen and the firewall stay on. Where PowerShell is already restricted by it, setup and the stick maker say so and change nothing
  • After a wake-up test with spikes, the Hub's wake-up card links straight to Drivers, where the usual cause (an old network or audio driver) shows
v1.83.0 · September 2026

Two old settings that cost latency, taken back, and dual-CCD X3D chips left to AMD's driver

  • The multi-plane overlay stays on. Extreme used to turn it off (an old fix for flicker); off, anything drawn over a borderless game (Discord's overlay, the volume pop-up, a notification) sends the game through Windows' compositor, a frame later to the screen. On, the game keeps its own path while the overlay is up
  • Windows' power throttling stays on. It only ever slows programs in the background, never the game in front, and on an Intel hybrid CPU it is what sends them to the efficiency cores, so the performance cores are the game's. Turned off, background programs competed with the game for them (and OmniDx Edition's Game Boost could not put background apps in Efficiency mode)
  • A PC where an earlier version made either change gets it put back at the next run, the way undo would, and it comes out of that run's record so the keep task stops putting it back. The Windows check plants both in an old record and proves it
  • Ryzen 9 7900X3D, 7950X3D, 9900X3D and 9950X3D keep Windows' Balanced plan, as AMD asks: AMD's driver moves a game onto the half of the CPU with the big cache by parking the other half, and the OmniDx plan, which never parks a core, left the game spread over both. OmniDx Edition's presets and Game Boost keep Balanced on these chips too
  • OmniDx Edition's Hub › Running has switches for ten more: HP OMEN Gaming Hub, Alienware Command Center, Lenovo Vantage and Legion, Acer NitroSense and PredatorSense (all four kept on laptops, where they run the fans), Glorious CORE, Turtle Beach and ROCCAT, Cooler Master, Thermaltake, Elgato and EVGA Precision X1
  • Seven helpers that come with some boards' and laptops' drivers, which OmniDx Edition already cut, now go in the tune too: Nahimic's audio effects off (known to crash games by injecting into them; kept on a laptop, whose speakers it tunes), AMD's user experience program and Killer's analytics off, and Intel's DAL host, ME local management, ME WMI provider and Graphics Command Center helper started only when something asks for them
  • The NVIDIA app's FrameView service, which runs all the time for its overlay's numbers, counts with the app's extras in the report's breakdown and Hub › Running
  • The run now measures the wake-up delay before and after: four seconds of asking to wake in 1 ms on a high-resolution timer, the average and the worst. A driver that holds the CPU delays input and frames by the same amount; the report puts both numbers in its before-and-after table. OmniDx Edition's Hub has the same test on its Home page, ten seconds, with a grade and what to do about spikes
  • New: $env:OMNIDX_MODE='read'; irm omnidx.net/go.ps1 | iex saves the exact script the command would run on your PC to the desktop, with its SHA-256, and changes nothing
v1.82.1 · September 2026

Why your PC runs more than a clean install, and what can go

  • Other software's updaters (Google's, Edge's, Brave's, Adobe's, Dropbox's, Intel's driver assistant, Java's) no longer run all day from a service of their own: they start when their program asks, and the programs still update themselves when opened. Found by the folder the service runs from, recorded, and put back by undo
  • The report now splits what is still running by who ships it, with the processes and threads of each: Windows, its security, the drivers' helpers, anti-cheat, the hardware and helper apps (lighting, mouse, cooler, the graphics app's extras), updaters, your apps and anything else. A clean install runs Windows' share alone; this is the difference on a home PC, and which parts of it can go
  • The after-restart count writes the same breakdown for the start that counts, to running-after-restart.txt
  • With OmniDx Edition, Hub › Running shows it live, with a switch for each hardware app and one for the updaters: off, its services start only when it is opened and it no longer starts with Windows; on puts back exactly what was there
v1.81.0 · September 2026

USB power saving really off, SSDs awake, and a quieter first minute after sign-in

  • A fix: the OmniDx plan's "USB selective suspend off" carried a wrong setting id, and Windows skipped it without a word, so USB power saving stayed on. The "USB 3 link power" line pointed at a different setting (the hub's suspend timeout), and the switchable-graphics line sat under the wrong group. All three now hold, and the Windows check reads each one back from the plan
  • SSDs no longer nap while plugged in: NVMe's own idle power states (APST) and SATA link power management are off on mains, so the first read after a pause (a map loading, a texture streamed in) does not wait for the drive to wake. On battery, Windows' values stay
  • Defender's scheduled scans now run at low CPU priority as well as capped at 25%, so a scan that starts mid-game waits behind it. Real-time protection is untouched
  • Network adapters: packet coalescing (batching incoming packets to save power) off, Wi-Fi's MIMO power save off, and on a desktop the Wi-Fi card's roaming at its lowest, so it stops scanning for another access point mid-match. Each is matched among the values that adapter's driver offers, and undo puts back what was there
  • The keep task, which checks after each sign-in that an update has not turned things back on, used to ask Windows about every service and task one by one, and kept PowerShell and WMI busy for most of the first minute a person looks at Task Manager. It now lists them once and finishes in seconds
  • The after-restart count and the keep task's card no longer count their own two processes
v1.80.0 · September 2026

Laptops: full speed plugged in, a real battery plan unplugged

  • The OmniDx plan is built from Ultimate Performance, whose on-battery values are as hungry as its plugged-in ones, so until now a laptop off the charger kept every core awake and every bus powered. Now, on battery only: the CPU idles down to 5% and boosts efficiently (a game still gets all of it), core parking, USB and PCIe power saving come back, Wi-Fi saves a little without the ping spikes of the maximum, the screen goes off after 5 minutes, sleep at 30, and a laptop asleep for 3 hours hibernates instead of running flat. Plugged in nothing changes. A desktop on a UPS gets the same during a power cut
v1.79.0 · September 2026

Your frame rate, measured: OmniDx Bench, one button away

  • New, free for anyone: irm omnidx.net/bench.ps1 | iex records a minute of a game with PresentMon (Intel's open-source frame-time tool, checked against its pinned fingerprint before every use) and gives average FPS, the 1% and 0.1% lows and stutters a minute. Run it stock and again after the tune and a restart: it puts the two side by side, calls anything under 3% "about the same", and draws a 1080 x 1920 card to post. How to test fairly
  • The app has a "Measure a game's FPS" button at the top that opens it in its own window; the free report suggests measuring before the tune, and the report's next steps suggest measuring after the restart
v1.78.2 · September 2026

OneDrive on a brand-new Windows no longer slips past the debloat

  • A new Windows installs OneDrive for each account in the background at its first sign-in. Run straight after a clean install, the tune looked while that installer was still going, found no OneDrive, and left it; OneDrive then finished installing and started with Windows at every sign-in after. Found filming a clean install. Now the debloat waits for OneDrive's first-sign-in installer (up to two minutes) and looks again: with nobody signed in to it, it is uninstalled as it always was, and undo reinstalls it
v1.78.1 · September 2026

What is still running after the restart, by name

  • The one-time count at your next sign-in now also writes every process still running then, grouped and with its memory, to C:\OmniDx\processes-after-restart.txt, next to the lists from before and after the run. Status mode names the biggest groups and where the full list is, and the support bundle includes it
v1.78.0 · September 2026

Your games set up in the NVIDIA driver itself

  • On an NVIDIA card, every listed game the tune finds on the PC now gets the driver settings NVIDIA Control Panel > Manage 3D settings > Program Settings would give it by hand: power management at prefer maximum performance (the card keeps its clocks mid-match), low latency mode on (one frame queued instead of up to three) and texture filtering at high performance. A game NVIDIA already has a profile for gets them on that profile; one it has none for gets its own, "OmniDx - " and the game's name
  • It goes through NVIDIA's own driver interface (NVAPI), the one the Control Panel uses, function by function as NVIDIA publishes it. A driver that expects another layout refuses the call rather than misreading it, and the tune says so and moves on
  • V-Sync, the frame cap and G-Sync are left to each game and to you: Reflex and G-Sync want them set together, not by a script. The report says which to set globally by hand
  • Every value it replaces is recorded. Undo puts a setting you had chosen back, takes the rest off the profile so NVIDIA's own value applies again, and removes the profiles it made
  • The NVIDIA step now reads the driver's version and age; a driver more than four months old is flagged with where to get the current Game Ready driver
Terms · 24 September 2026

All sales are final

  • The fourteen-day refund is withdrawn. The key is delivered on the page the moment you pay and is yours for as long as you own the PC, so there is no refund window; the free report mode is the way to look first, and it shows every change the tune would make without making one. A key that will not take on a PC is fixed, moved or reissued by support. The terms, pricing and key pages and the key email say so
  • Two lines that had fallen behind are fixed: the terms now say the tune writes graphics settings into a game's own settings file when you say yes (never the game's program files or its anti-cheat), and the FAQ now says a key moves to a new PC from the key page once every 30 days, not only by email
v1.77.1 · September 2026

No empty PowerShell window after you sign in

  • The two small tasks the tune leaves (the one that keeps it cut after updates, three minutes after sign-in, and the one-time after-restart count) asked for a hidden window, but Windows shows the window for a moment before hiding it, and on a busy sign-in that moment was seconds long: an empty blue window on the desktop that took the focus from whatever you had open. Found while filming a clean install. On Windows 11 they now start with no window at all; Windows 10 keeps the hidden window
  • The after-restart count's command is now a script file next to the undo script, so each task's line is only a path
  • The Windows check starts the keep task through Task Scheduler, as a sign-in does, and fails unless it runs to the end, logs, and opens no window
v1.77.0 · September 2026

Discord or Spotify left on at startup stays on, and a video of the whole thing

  • Unticking Discord or Spotify in the startup list left its Windows entry alone, but the step that tunes those apps still switched off the app's own "open at startup" setting, so it dropped off the list at its next start anyway. Now an app you keep keeps that setting too; the log says so ("it still starts with Windows, as you chose"). Found while filming the tutorial
  • The Windows check plants Discord's and Spotify's settings files, keeps Discord in the run, and proves Discord's setting was left on, Spotify's auto-start switched off, and both files back byte for byte after the undo
  • New on the front page and the download page: "Watch it work", a 74-second video of the whole thing on the site's example PC. It shows opening PowerShell, the one line, the administrator prompt, the fingerprint check, the app reading the PC, the key, the run with its live log, a game's settings file, the report's BIOS checklist and undo. The run is shown eight times faster, and the video says so. Every step is also written out under the player
  • 1.76.1 on the build machine: 398 changes recorded, 394 put back by undo, no red text
v1.76.1 · September 2026

The window's new checkbox fits, and its keep list names streaming

  • The picture the check draws of the window showed the new game-files checkbox cut off; its label is shorter now. The window's "Keeps" line names streaming when OBS, Streamlabs or XSplit is installed, as the console does
  • 1.76.0 on the build machine: 397 changes recorded (the twelve planted game settings among them), 393 put back by undo, and every planted game file byte for byte as it was
v1.76.0 · September 2026

Competitive settings written into the games' own files, and the PC maker's software in Extreme

  • For Fortnite, Marvel Rivals, Apex Legends, Counter-Strike 2, Rocket League, Rainbow Six Siege and Minecraft, the tune writes V-Sync off, motion blur off and the shadow and post-processing settings players use into each game's own settings file. It asks first, backs up each file, skips a game that is running, and undo puts every value back
  • Only a line already in the file changes, and only when its value has the shape the game uses: a setting a game renames is left alone, never added. The file keeps its own encoding. VALORANT, Overwatch 2 and League of Legends keep their settings in the account, so their files are left alone and the report still lists their settings
  • The free look lists what it would write, game by game, before anything changes; the app has its own checkbox for it
  • Extreme now removes the PC maker's support agents and promotion apps (Dell, HP, Lenovo, ASUS, Acer) and switches off their telemetry services. The hubs that run the fans, the battery limit and the hotkeys go only on a desktop; on a laptop they stay, with their services
  • The Windows check plants four games' files (one in UTF-16), proves the twelve edits, the four backups, a wrong-shaped value and a missing setting left alone, and after the undo compares every file byte for byte
v1.75.0 · September 2026

GPU health, thermal zones, the network as numbers, and a streamer profile

  • On an NVIDIA card the free look reads the driver's own tool: temperature at idle, the power limit against the card's maximum, fan, and the throttle reasons that are active (thermal, power cap, power brake). It warns when the card is throttling or hot at idle and says when the power limit sits under the card's maximum. AMD and Intel ship no equivalent tool, and the look says nothing rather than guess
  • The ACPI thermal zones where the board exposes them, with the passive limit that means the CPU is being held back by heat right now
  • The network as numbers: five pings to the router and five to the internet's edge, median, jitter and loss. A slow or jittery link to the router is named as Wi-Fi or a bad cable; loss is named as the line, which no tweak fixes
  • Streamer profile: with OBS Studio, Streamlabs Desktop or XSplit installed (or -Streamer), the camera frame server and Windows Graphics Capture stay, in Extreme too, and the report carries the encoder and capture notes
  • The report gains "Undervolt, not overclock, and a frame cap": the voltage curve on NVIDIA, the voltage steps on AMD, Curve Optimizer on Ryzen, the BIOS microcode on 13th and 14th gen Intel, and a frame cap three below the refresh rate with adaptive sync. Words only; the tune never touches voltage
  • Fixed, found by this version's own check: under Windows PowerShell 5.1 the free look's "Keeps" line came back as "nothing extra" even when the PC had a reason to keep something, because of how that line was assembled (the same construct run on its own behaves, so the exact cause is not pinned down). It is now built one reason at a time, and the check proves it by running the free look with -Streamer. Two other lists that filter down to one item are wrapped the same way as a precaution
v1.74.0 · September 2026

Two idle samples, and no update-service restart for an empty cache

  • 1.73.0's step timings put the count before and after the cut at 3.7 s and 3.1 s each, most of it waiting for three one-second idle-CPU samples. Two samples say as much about an idle desktop
  • The cleanup stopped and restarted the two update services to clear a download cache that, on a re-run, is empty: 3.7 s for nothing. It now looks first and only touches the services when there is something to clear
v1.73.0 · September 2026

The time outside the phases is timed too

  • The phases have been timed since 1.4x; the record of 1.72.0 showed a re-run's phases adding up to 13 of its 29 seconds. The steps around them (the read, the key, the count before and after, the safety net, the keep task, the report) are now timed by name, printed on one line under "Where the time went", and kept in the run record for both runs
v1.72.0 · September 2026

"1 feature", and the second run's phases in the record

  • The session line said "1 features"; it counts properly now. 1.71.0 measured on the build machine: one feature, one session, 6 s, same 386 changes and 382 undone
  • The Windows check records the second run's phase split next to its seconds (30 to 33 s for one change), so that half minute can be read the way the first run's is
v1.71.0 · September 2026

The optional features go in one DISM session too

  • Each feature was switched off in its own DISM session, about seven seconds apiece on the build machine, and a Windows 10 PC has four to switch off (the PowerShell 2.0 engine twice over, XPS, Work Folders). They now go in one session, the way the Windows pieces have since 1.44.0, with one at a time as the fallback
  • What is still enabled after the pieces went is checked in one read of the optional-feature class instead of one DISM query per feature
v1.70.0 · September 2026

FACEIT on Windows 10 is told about October 2026 in the console

  • The report already carried FACEIT's timetable (Windows 11 for every player from October 2026); the free look now says it in the console too, on a Windows 10 PC with FACEIT installed, since the console is where most people read
  • The Windows check records how long the second run takes next to how little it changes, and the trust page shows both; the published log keeps the "slow part" line before the DISM removal
v1.69.0 · September 2026

The slow step says so before it starts

  • Removing the Windows pieces in one DISM session is the one step that takes a while (sixteen to forty-four seconds on the build machine, most of the run) and it prints nothing until it ends. It now says so first, so a quiet half minute does not look like a hang
  • The trust page states the median across every recorded run (processes before and after, seconds, the free look) beside the latest run's own numbers, which swing with the build machine
v1.68.0 · September 2026

The trust page shows every verified run, not one

  • The check now keeps a history of its runs (script version, date, the count before and after, changes, seconds, the free look's timing, error lines) and the trust page shows it as a table, newest first. One run's numbers swing with the build machine; thirty runs show the trend, and the swings, honestly
  • Services: the in-process cmdlet sets the start type first and sc.exe is the fallback, instead of one sc.exe process per service. 1.67.0's no-wait stops measured: the services phase 4.4 s, from 6.5 to 8.6 s over the five runs before
v1.67.0 · September 2026

Services are told to stop and the run moves on

  • The services phase waited for each of some forty services to finish stopping, six to ten seconds on the build machine. The stop is now requested and the run carries on; the count at the end already allows for services still unwinding and says so. The keep task, which runs unattended at sign-in, still waits
  • The site's moving background draws thirty frames a second instead of sixty (the drift is too slow for the eye to tell) and the glowing motes come from one pre-rendered sprite: measured in the browser, half the script cost per second
v1.66.0 · September 2026

1.65.0's background read comes out: measured, it made the look slower

  • Two runs of 1.65.0 on the build machine said the same thing: the pieces lap fell from eight to ten seconds to six or seven, but the machine read's own laps doubled while the feature query ran beside them (the device lap 4.7 s and 5.6 s against 1.1 to 1.8 s before), and the whole free look came out at 23 to 24 s against 17.5 s for 1.64.0. The two reads share the same service and get in each other's way
  • The pieces read is sequential again, as in 1.64.0. The servicing stack's cold start is the one cost left in the look, and it is recorded as such rather than hidden
v1.65.0 · September 2026

The Windows-pieces read runs while the machine is read

  • With no DISM call left in the free look, its pieces lap was still eight to ten seconds cold: the optional-feature class starting the servicing stack. That read and the component store's package list now run in a runspace inside the process while the machine is read, and the plan collects the answers when it needs them. If the runspace fails or takes over a minute, the plan reads them itself as before
  • Looked at and left alone: the feature states are not in the component store's registry under the packages' Updates keys (the walk cost a quarter of a second per key on the build machine and found none of the six names), so the class stays
v1.64.0 · September 2026

Every Windows piece decided from the component store, and three fewer module loads in the read

  • 1.63.0 still asked DISM about two names on the build machine, and those two carried its whole cold start (13.1 s of the look). Math Input Panel's package name came out of the check's discovery step; WordPad, Fax and Scan and the client name of the old Media Player are the names their feature-on-demand packages ship under. The old Media Player matters: its package is named differently on Windows 11 than on the build machine, and the previous hint would have skipped it on a buyer's PC. Anything the store mentions under an unknown name still goes to DISM
  • The printer list, the device listing and the Secure Boot flag are read from their classes and the boot-time flag instead of loading three modules; the cmdlets remain the fallback. The cold read's slowest lap was the printer listing at 2.3 s. Measured on the build machine: the cold read 9.6 s to 3.9 s, the warm read 3.7 s to 2.4 s, the free look 15.7 s to 11.7 s
v1.63.0 · September 2026

The free look reads the component store instead of asking DISM fifteen times

  • The look's own split (recorded since 1.62.0) put fifteen of its nineteen cold seconds on the Windows pieces: each name asked of DISM costs half a second warm and a second cold. The component store's record in the registry lists every package in under a second and says which are installed; the optional-feature class answers every feature name at once
  • Steps Recorder, the old Media Player and Internet Explorer are decided from that record by package names the check verified; a piece the store never mentions is not on the PC and is not asked about; anything else is still asked of DISM by name, so the answer is never a guess
  • The Windows check now holds the look's count against DISM's own answer on every run and fails on a mismatch. Measured on the build machine: the run's debloat look 7.6 s to 3.9 s; the free look's pieces lap 15.2 s to 13.1 s cold, with the two names still asked of DISM carrying its whole cold start
v1.62.0 · September 2026

The registry helper opens a key once

  • Every registry change used to probe the key, then ask for the value and catch the error when it was not there yet. One open of the key now answers both questions. Measured on the build machine: the read fell from 5.2 s to 4.4 s (the device lap from 1.9 s to 1.3 s), and the game-profile phase, which writes three values for each of 146 game exes, gave back about half a second outside its folder walk. Same 386 changes, same 382 undone
  • The Xbox-app and Minecraft check reads the package repository in the registry instead of loading the Store-app module twice; the TPM check reads its class instead of loading a module for one field. The cmdlets remain the fallback when a key or class is missing
  • The Windows check records the free look's split (startup, services, tasks, apps, Windows pieces) and the look's own read line in the run record, so a slower look says where
v1.61.0 · September 2026

The read no longer loads the Storage module at all

  • 1.60.0's read line (6.6 s, down from 7.7) showed the Storage module's load had moved from the disk read to the system-drive lookup rather than gone. That lookup uses the partition class now, with the cmdlets as the fallback, so nothing in the read loads that module
v1.60.0 · September 2026

Two more seconds off the read

  • The disks are read straight from the storage class instead of through a cmdlet that loads a whole module for three fields, and the display-mode listing (bounded at ten seconds because some drivers take that long) runs in a runspace inside the script instead of a second PowerShell process, which cost a second by itself on the build machine. 1.59.0's read line: cim 2.3, modes 1.0; the next one says what these two saved
v1.59.0 · September 2026

The read asks the device bus once

  • 1.58.0's new read line showed the five device queries (Bluetooth twice, touch, a fingerprint reader, a controller) costing 2.2 seconds of a 7.7 second read on the build machine, each walking the whole bus. They are one listing filtered in memory now, and the physical adapters are listed once instead of twice. Every mode reads the machine, so every mode starts sooner
v1.58.0 · September 2026

The read and the free look are timed on their own lines

  • The machine read now says how long it took and where (the four slowest parts), in every mode. The Windows check records the free look's time and the read's time in the published run record, shows them on the trust page, and fails when the free look gets more than twenty seconds slower than the last published run, the way 1.44.0's slow listing would have been caught the day it shipped
v1.57.0 · September 2026

The after-restart card writes itself

  • The keep task, which runs three minutes after every sign-in, now also writes C:\OmniDx\card-after-restart.png: the same card as the run's, with the count of that start, the number that counts. Nobody has to run status mode to get it; status mode names it when it is there. The Windows check requires it
v1.56.0 · September 2026

The game-folder walk has a limit

  • The game profiles phase walks every Steam library, Epic folder and the usual places four levels deep to find each game's exe. A terabyte of libraries is a lot of folders, so the walk now stops after twenty-five seconds and says how many folders wait for the next run; every listed game gets its CPU-priority profile by name regardless, and the line reports how long the walk took
v1.55.0 · September 2026

The eagle is there when the window opens

  • 1.54.0 left the eagle to Windows' own background download, which the check's headless draw of the window never waited for, so the published window still showed the old mark. The window now fetches it before it opens, three seconds at most and usually well under one, and keeps the drawn mark offline
v1.54.0 · September 2026

The eagle in the window and on the report

  • The app window's title row shows the eagle, fetched from the site by Windows itself while the window opens; the drawn mark stays until it lands, and for good on a PC that is offline. The report's title carries it the same way
v1.53.0 · September 2026

The eagle on the card

  • The card carries the eagle from the site instead of the old bars-and-bolt mark: one small download when the card is drawn, five seconds at most, and the old mark is drawn instead when the PC is offline
v1.52.0 · September 2026

Two more things the free look notices

  • A desktop with a graphics card whose monitor is plugged into the motherboard: the integrated chip reports a display mode and the card reports none, and the run says to move the cable. No tweak comes close to that one
  • A nearly full system drive (under 20 GB or under 10% free): games stutter and shader caches fail on it, and the run says where the space goes
  • The card's honesty line wrapped past the edge on the first build; it is two lines now
v1.51.0 · September 2026

The card

  • Every run now writes C:\OmniDx\card-<date>.png: the process count before and after on one 1080 by 1080 picture, the CPU and GPU, the date, and the words that keep it honest (an example run on one PC; yours will differ). The report shows it; status mode writes another once the after-restart count exists, with that number. The Windows check requires the card and publishes the build machine's
v1.50.0 · September 2026

The 2026 anti-cheat rules, and the dual-CCD X3D

  • FACEIT and VALORANT's Vanguard On-Demand now require Secure Boot, TPM 2.0, IOMMU and memory integrity on. The machine read reports IOMMU next to the other three; where Riot's client or FACEIT's anti-cheat is installed, the run names whichever of the four is off, the optional memory-integrity switch is refused outright, and BIOS item 12 says where IOMMU lives on AMD and Intel boards
  • On a 7900X3D, 7950X3D, 9900X3D or 9950X3D, Extreme no longer removes Game Bar: AMD's optimizer spots games through Game Mode and steers them onto the cache half of the CPU. The run also warns when that optimizer service is missing or stopped
  • The OmniDx power plan sets the processor's energy performance preference to performance, the value a modern CPU reads to choose its clocks; Balanced leaves it at a quarter of the way toward saving power
v1.49.0 · September 2026

Two runs in one minute keep two records

  • A run's record, log and report were named to the minute, so a second run started inside the same minute (a refusal, then a retry) would have written over the first run's record and taken its undo with it. They are named to the second now. The Windows check had been waiting a minute between its runs to avoid exactly that; it no longer needs to, and is two minutes shorter
v1.48.0 · September 2026

The slow part, found and removed

  • 1.47.0's timing line said it plainly: the look took 84 to 92 seconds of the debloat phase, every run. The one listing of optional features that 1.44.0 introduced (and 1.46.0 kept) is what costs it, 75 to 90 seconds on the build machine against a few seconds for the three names. Every piece is asked for by name again, as in 1.43.0, when the look took fifteen seconds and the phase 38
v1.47.0 · September 2026

The debloat phase, timed apart

  • The debloat phase has taken anywhere from 36 to 115 seconds on the build machine, and its one timing line (the DISM batch, about 20 seconds) did not account for it. It now ends with one line saying how long the look, the pieces and the features each took, so the next run says where the rest goes
v1.46.0 · September 2026

The free look, measured again

  • 1.44.0 asked DISM for one listing of every capability instead of the seven names. Warm, that was faster; cold, on the build machine, the listing took 77 seconds against 15 for the names, and the paid run's debloat phase went from 38 seconds to 90. Capabilities are asked for by name again; features, a short list, stay as one listing
v1.45.0 · September 2026

The report's "What was done" is a list again

  • In 1.42.0 to 1.44.0 the HTML report drew every line of "What was done" into one heading. It is one heading per phase with its lines under it again, and the Windows check now counts those headings in the report it publishes, so this cannot slip through twice
v1.44.0 · September 2026

A faster free look

  • The free look asked DISM about each legacy piece one at a time, and that was fifteen of its seventeen seconds on the build machine; it asks for one listing of capabilities and one of features now. The paid run reads the same plan, so it starts sooner too
v1.43.0 · September 2026

The free look counts what the run would really change

  • The free report said "services it would stop or set to manual: 51" on the build machine, and the paid run then changed 38: the look counted every listed service that existed, the run only changes one whose start mode differs from what it sets. The look applies the run's rule now, so its number is the run's number
  • Undo's closing line no longer calls a legacy piece that is waiting for Settings › Apps › Optional features a failure; it counts those separately and names where they are added back
v1.42.0 · September 2026

Read from the build machine's own report

  • A service somebody already disabled stays disabled. The tune sets a few services to manual rather than off (search indexing, Superfetch, the diagnostic policy); on a PC where one of those was already disabled, manual would have been a step back on, and the build machine's report showed search indexing returning with eight processes exactly that way
  • The undo section of the report only names a System Restore point when one was made; when Windows refused (the warnings say so), it says the undo script is the way back
  • The report's big "processes before" number, its before-and-after table and the Done line now read one snapshot, so they agree to the process
  • A heading with nothing done under it (the key check, a skipped phase) stays out of the report's "What was done"
  • Small things the second run's log showed: the cache cmdlet's own "Deleting..." lines and the feature cmdlet's "Restart is suppressed" warning no longer leak into the log; a run with nothing to clear says so instead of "about 0 MB back"; a run that stopped no services no longer blames unwinding services for the count; a display reporting 1 Hz reads as "refresh unknown"; an empty "Keeps:" line reads "nothing extra"; Status says "1 change", and its "Last run in place" line skips a run that was undone
v1.41.0 · September 2026

Read from the build machine's own log

  • The Defender scan cap only ever lowers now. The build machine's log showed the tune raising a cap that was already set lower than its own 25%; a PC that holds its scans under that keeps its own figure, and the log says so
  • The Before line and the After and Gone lines sat under whichever heading came before them; they have their own now (Before the cut, Done)
v1.40.0 · September 2026

The report's small print, readable

  • The muted labels in the report (under the big numbers, the table headings, the notes) were a shade under the contrast threshold an accessibility scan applies; they are lighter now, above it on every surface of the page
v1.39.0 · September 2026

The report, read as a buyer reads it

  • The "Telemetry, background activity, the shell" section of the report now says what it did, instead of standing empty because that phase records everything silently
  • The BIOS checklist in the report drops the bullets in front of its numbered items
  • The Windows check now publishes the report of its own run on the site, so the real thing can be opened before paying, and every capture of the script's output is scanned for PowerShell's own error text: the count is on record (zero), and a rise fails the check
v1.38.0 · September 2026

Quieter where a PC lacks a piece

  • A power-plan setting this PC's driver does not have is skipped and counted on one line, instead of powercfg's error appearing in red
  • Game Bar's presence writer is switched off only where Game Bar is installed; a registry key Windows will not let the tune create is named once, and the value left alone
  • A run that finds everything already done still writes its (empty) record, so undo and status always have a complete list of runs
  • "1 app removed", not "1 apps": the counts on screen agree with their nouns
v1.37.0 · September 2026

Said on screen, not only in the report

  • Anything another tool left switched off is said in the console while the PC is read, not only in the report, and the README in C:\OmniDx names the section
v1.36.0 · September 2026

What other tools left switched off

  • The report, the free report mode too, gains "Left by other tools": Defender switched off by policy, automatic updates off, the Windows Update service disabled, SmartScreen off, User Account Control off, the CPU security mitigations off. The tune changes none of them; it names each with the way back, so a hole another script made is not blamed on this one and not kept unknowingly
v1.35.0 · September 2026

Every start since the tune, on record

  • The keep task notes the boot time of each start on its log line, and status lists the starts since the tune, oldest first, next to the figure from before it: a record over weeks, in Windows' own numbers, not one screenshot
  • The after-restart task waits up to three minutes more for Windows to log that start's boot time, so the line has it far more often
  • The report's first next step says where the boot time will show up
v1.34.0 · September 2026

Boot time, before and after, in Windows' own figures

  • The report carries the boot time of the last full start before the tune, the after-restart line adds the first start after it, and status shows both side by side from then on. No stopwatch of ours: it is the figure Windows writes in its own boot-performance log a few minutes after the desktop appears
  • The key page sends the keys to your checkout address again with one press: the address on file and nowhere else, ten minutes apart, and the page says where they went
  • The owner page proves the mail before the first sale with one test email (Resend's exact refusal shows when the domain is not verified yet), sends every unsent order in one press, shows totals since the first sale above the recent orders, and emails the week's figures on demand and every Monday
  • Undo no longer waits five minutes on each optional piece of Windows when Windows Update is out of reach: after the first one times out it lists the rest for Settings > Apps > Optional features and gets on with it
v1.33.0 · September 2026

An old guide's clock, a stuck app at shutdown, and no guessing

  • A forced platform clock is removed: the "bcdedit /set useplatformclock true" line from a 2015 tweak thread makes every timer read cost more on a modern CPU and unsettles frame pacing. The tune deletes the value where it finds it, Windows picks the clock source again after a restart, and undo sets it back
  • Extreme: an app that will not close at shutdown is ended after its two seconds instead of holding the "this app is preventing shutdown" screen
  • The licence server shuts out guessing: twenty key-page tries, forty key checks or ten moves from one connection in ten minutes, and it answers "too many tries" until the window passes, while everyone else is served. Ten wrong owner tokens close the owner page the same way; the right token is never counted
  • The key tool makes and checks keys only. Nothing derives a buyer's key from an order any more: keys exist where the server minted them after Square confirmed the payment
v1.32.0 · September 2026

Drop Extreme, keep the tune

  • Undo the last run only: $env:OMNIDX_MODE='undolast' puts back the newest run (the Extreme one, say) and leaves the earlier runs and the keep task in place. Full undo still walks back every run. The keep task now goes only when no run is left recorded
  • The "after" count waits for the services that were told to stop to finish stopping, up to twenty seconds, so the number on screen is closer to the one after a restart
  • The Windows check undoes the Extreme run on its own first, checks that the two earlier runs are untouched and status is clean, then undoes the rest. A run put back alone now leaves the standard tune exactly as it was: the power plan, the TCP settings and the keep task no longer record themselves again on every run
  • Status and the key check ask the licence server, when one is configured, what it holds on the key: issued and on how many PCs, or switched off by a refund. Without a server they answer as before
  • The report opens with five next steps: restart, the BIOS items that matter on this PC, the GPU control panel, the launchers, and where status and undo are
  • The BIOS checklist and the GPU notes know a laptop: the memory profile, fans, power limits, the integrated graphics and the memory timings are written for what a laptop actually exposes, and the GPU switch (Hybrid, Discrete, MUX) and the per-game High performance setting take their place; Whisper Mode, Battery Boost and Radeon Chill are named as the frame caps they are
v1.31.0 · September 2026

Service hosts grouped, twenty-seven more tasks, Defender on a leash

  • Extreme now groups the service hosts the way Windows ran for twenty years: on a PC with more than 3.5 GB of RAM every service gets its own svchost.exe, which is most of the process count. A threshold above the installed RAM puts them back into shared hosts, twenty to forty processes fewer after a restart. The cost is that a crashing service takes its group down with it, which a restart fixes. Extreme also turns the System Guard broker off where it still ships, and shutdown waits two seconds for a slow service or app instead of five and twenty
  • The standard tune disables twenty-seven more scheduled tasks nobody on a gaming PC asked for: the compatibility appraisers, memory and disk-usage diagnostics, data-usage bookkeeping, the flighting reporters, SQM, offline files, storage tiers, remote assistance, print provisioning, media-library sharing, the indexer's maintenance, roaming profile uploads, the shared-PC cleanup, the Store's remote install and the end-of-support nag
  • Defender stays, and its scheduled scans are capped at a quarter of the CPU instead of half; real-time protection is untouched, and the cap is skipped when another antivirus is in charge. Undo puts the old figure back
  • Typing and inking history stays on the PC, handwriting errors are not reported, the compatibility inventory is off, the clipboard is not synced through the cloud, and nobody can offer to take the screen over through Remote Assistance. On 11, the account nags on Start go, and "End task" appears on the taskbar's right-click menu for the game that stops answering
  • Squad is now $39.99 for three keys, one PC each: yours and two for friends. The $69.99 five-PC key is gone. And the key goes to the email you gave at checkout the moment Square confirms the payment, as well as onto the page Square sends you to
  • Eighteen more game profiles, forty-nine in all: Battlefield 2042, EA Sports FC 26, NBA 2K26, Palworld, Path of Exile 2, Diablo IV, Monster Hunter Wilds, Elden Ring and Nightreign, Cyberpunk 2077, Baldur's Gate 3, Star Citizen, DayZ, Arma Reforger, Hell Let Loose, Genshin Impact, Ready or Not, Final Fantasy XIV, STALKER 2 and Sea of Thieves, each with its settings in the report; FiveM gets the GTA V profile. The power plan also turns throttle states off on a desktop and Wi-Fi power saving off (the cause of most Wi-Fi ping spikes); flow control goes off on the live adapter
  • The report gains a section on launchers, overlays and helper apps: the one or two settings that matter in Steam, Epic, Battle.net, the Riot client, the EA app, Ubisoft Connect, GOG Galaxy, Discord, the NVIDIA and AMD apps, the Xbox app, Overwolf, Wallpaper Engine and the RGB suites (iCUE, Synapse, G HUB, SteelSeries GG, Armoury Crate, MSI Center), for the ones found on your PC
  • The one command now fetches the exact copy of the script that passed the whole Windows check, published by the check next to its hash. A change that fails the check never reaches anyone. The check also runs when the test tooling changes, not only the script
v1.30.0 · September 2026

Extreme, and thirty more services

  • The standard tune cuts thirty more services nobody on a gaming PC uses: peer networking, routing, SNMP, mixed reality, shared PC, SMS, troubleshooting, UE-V, Work Folders, Wi-Fi Direct, scanners, spot verifier, cellular time, enterprise apps, File History, data usage, and the Hyper-V guest services on a physical PC. Game Bar's presence writer, the one Game Bar process that runs anyway, is off
  • Extreme, a second command on the key page marked caution: eighteen more services (notifications, clipboard history, nearby sharing, Windows Search, superfetch on SSDs, capture, media controls, pairing brokers, voice activation, DVR broadcast), the shell drawn plain, exclusive fullscreen for every game, multi-plane overlay off, memory compression off with 16 GB or more, the dynamic tick off on desktops, the Xbox pieces gone unless they are in use, and nine advanced BIOS items in the report. It asks first; undo puts all of it back; the keep task leaves the shell choices alone. In the app it is a tick box; from the console, -Extreme
  • The Windows check now runs a third pass with Extreme on the build machine, requires it to record its extras and leave status clean, then undoes all three runs
v1.29.0 · September 2026

Keys come from one place

  • The key page no longer makes keys itself; only the licence server issues them, and only after Square confirms the payment. No server, or one that cannot be reached, is a plain message, never a key
  • A first run needs the licence server to vouch for the key and stops without it; a key already bound to the PC keeps working when the server is unreachable, as before. Run by hand, the script reads the same config the one command does
  • The Windows check first proves a first run refuses with no server and changes nothing, then runs the tune against a stand-in server on the build machine itself
v1.28.0 · September 2026

Undo, in one session

  • Undo puts the legacy pieces of Windows back in one DISM session at the end instead of one session each, which was most of its time; if DISM will not take them together they go one at a time, and if the batch times out because Windows Update is out of reach it says where to add them later instead of timing out again three times
v1.27.0 · September 2026

Said, not assumed

  • The debloat says whether the legacy pieces went in one DISM session and how long that took, or that DISM refused the batch and they went one at a time; the build machine's runs vary between 38 and 73 seconds here and the log will now say which path it was
  • The trust page lists what the Windows check proves on every push, under the numbers it publishes
v1.26.1 · September 2026

One session for the legacy pieces

  • 1.25 read the service list once and, because the plain listing leaves out the per-user templates (clipboard history, push notifications, the sync services), skipped seven of them. Caught by comparing two build-machine logs; a missing name is now looked up directly, and the check fails when a run records noticeably fewer changes than the last published one
  • The legacy pieces of Windows are removed in one DISM session instead of one each; the debloat was the slowest phase at 68 seconds on the build machine, most of it session set-up. If the batch does not complete, each piece is taken one at a time as before
v1.25.0 · September 2026

Three phases, once each

  • The phase timings from the build machine named the slow ones: apps 25 s, games 23 s, services 17 s. Packages and provisioned packages are now read once instead of once per pattern, every service's start mode comes from one read, and the game search skips the Program Files folders no game ships under
v1.24.0 · September 2026

Where the time went

  • Every phase is timed. The end of a run says where the seconds went, and the summary file keeps the figure per phase, so the next thing to make faster is a fact
v1.23.0 · September 2026

Counted once

  • The old Media Player is both a capability and an optional feature on newer builds, and the free report counted it twice; removing the capability takes the feature with it, so it is one item now. The build machine's free look went from 110 seconds to 19 with the 1.22 change; that number is in its log
v1.22.0 · September 2026

A faster look

  • The legacy pieces of Windows are looked up by their exact package names instead of listing every capability and feature on the PC, which took a minute and a half of the free report's two minutes on the build machine; scheduled tasks are read once instead of one by one
v1.21.0 · September 2026

Your decisions stand on a second run

  • A startup app an earlier run switched off and you turned back on in Task Manager stays on when you run the tune again: the console says so and leaves it, and the app shows it unticked. Type "all" at the console picker, or tick it in the app, to cut it again
v1.20.0 · September 2026

Where the free look spends its time

  • The free report says how long each of its reads took (startup, services, tasks, apps, the legacy pieces of Windows), so a slow one can be seen and shortened rather than guessed at
  • The Windows check no longer loses a run's files when two runs finish close together: it refreshes to the branch tip and puts the newest run's files on top
v1.19.0 · September 2026

One zip for support

  • $env:OMNIDX_MODE='support' zips the run logs, the PC as it was read, the numbers and the change records to the desktop and opens Explorer on it. Keys are masked; no registry exports, none of your files. No administrator prompt
  • Restart now in the app asks for a second click, like undo
v1.18.0 · September 2026

Minecraft, not every Java

  • The Minecraft profile no longer matches javaw.exe, which would have raised the priority of every Java program on the PC and called any Java install "Minecraft"; it matches the Bedrock and launcher executables. Seen on the build machine, which has Java and no Minecraft
  • The run log on the run-it page no longer has its long lines cut at the build machine's console width
v1.17.0 · September 2026

One warning fewer

  • Removing the old Media Player as a capability takes its optional feature with it on newer builds, and the feature step then warned that the name was unknown. It looks again first now and says "already gone" instead. Seen on the build machine's own run
v1.16.0 · September 2026

Status without the prompt

  • Status and the key check only read, so they now run in any PowerShell, from any account, without asking for administrator rights; the one command no longer opens a second window for them
v1.15.0 · September 2026

Why is the number up again

  • Status names the processes running now that were not running right after the tune: whatever was opened since, or a launcher that came back. Settings are checked separately; this is the answer to the question Task Manager raises
v1.14.0 · September 2026

One notification, when it matters

  • When the keep task finds a feature update has turned five or more settings back on, it puts them back and shows one Windows notification saying so; a stray value or two is fixed quietly
  • The transparency page lists the games it writes profiles for, with their executables, generated from the script
v1.13.0 · September 2026

Quiet about the key

  • The one command no longer puts the key on the command line of the administrator window it opens (Windows keeps command lines in logs and the run's transcript); it crosses in a file only your account can read, which is deleted on arrival
  • The keep task's log line now ends with the process count at that sign-in, so keep-log.txt doubles as a record of the number over time
  • The keep task leaves the Windows 11 right-click menu choice alone, like the other personal preferences
v1.12.0 · September 2026

Faster read

  • Reading the PC times each of its slow parts and keeps the numbers in the machine record, so a slow read can be seen rather than guessed at; the Windows check prints them
  • The controller check looks only in the device classes a controller can be in, and listing every display mode (which some drivers take ages over) gets ten seconds before it is left out
v1.11.0 · September 2026

Every process, in the report

  • The report page folds in the full process lists from before and after, name by name with counts and memory, and says whether the PC is kept cut
v1.10.0 · September 2026

No means no

  • Saying no to keeping it cut, or running with -NoKeep or -Skip keep, also removes the keep task an earlier run left, and says so
  • The Windows check's second run now passes no key at all and says no to the keep task: it must find the key the first run bound, be accepted, record nearly nothing, and take the task down
v1.9.0 · September 2026

The run, word for word

  • The run-it page shows the log of the last run on the build machine: every phase header, everything done, the numbers, exactly as the console printed them. Committed by the check itself, so it cannot be edited by hand
  • The free report mentions the keep task and status mode
v1.8.0 · September 2026

Read me first

  • Game profiles: the game folders are walked once and every game is a lookup, instead of one walk per game; the games phase is minutes faster on a full Program Files
  • The PC remembers its key: a second run asks for nothing, in the console and in the app, whose button now says Run it again. Undo in the app asks for a second click
  • C:\OmniDx gets a README.txt: what every file there is, how to undo, how to see status, and that nothing in the folder talks to the internet
  • The report, text and page, ends with the status command; the one command prints "Script verified" with the hash it matched, so you can see the check happen
  • Hibernation is read from the registry instead of powercfg's text, so a desktop running Windows in another language gets the same treatment
  • The transparency page lists what the keep task leaves alone, generated from the script
  • The Windows check now runs the tune a second time with the same key and requires it to be accepted and to find nearly nothing left to do, then undoes both runs; the proof line shows the second run's count
v1.7.1 · September 2026

Thirty-one games, and the disk

  • Fifteen more game profiles: The Finals, Dota 2, Battlefield 6, Deadlock, Delta Force, ARC Raiders, Helldivers 2, Warframe, Destiny 2, Halo Infinite, Dead by Daylight, Hunt: Showdown 1896, War Thunder, World of Warcraft and Squad; each with its competitive in-game settings in the report
  • NTFS is allowed more cache memory on PCs with 16 GB or more, and TRIM is switched on for SSDs when a cloned or old install left it off. Both recorded with the previous value; undo puts them back
  • The proof line on the front page now also shows how many settings the Windows check turned back on by hand and the keep task put back
  • The publish check now refuses a recorded change type with no undo handler, a window control the code names but the XAML lacks, and a bootstrapper flag the script does not declare
v1.6.0 · September 2026

Kept cut

  • Windows updates turn pieces of the tune back on. Say yes at the end of a run and a small task, three minutes after each sign-in, compares every recorded service, task and value with the machine and puts back what drifted. It never touches startup apps or your own settings, logs to C:\OmniDx\keep-log.txt, and undo removes it. -NoKeep never makes it
  • Status: $env:OMNIDX_MODE='status' says which runs are in place, what an update put back, when the keep task last ran, the after-restart count and the key. Changes nothing; the app has a button for it
  • Undo walks back every recorded run, newest first, so a PC tuned twice ends up as it was before the first run; each record then moves to done\ and a second undo says there is nothing left
  • C:\OmniDx keeps the last ten runs of logs, reports and snapshots; undo records and their backups stay until undo uses them
  • Restart now counts down ten seconds; any key stays
  • The Windows check now proves the keep task: it turns a service, a task and a policy value back on by hand, runs keep.ps1, and requires all three put back and status clean; then undo must remove the task and leave nothing behind
v1.5.0 · September 2026

Run before published

  • Every change now runs the whole tune with a real key on a fresh Windows build machine, then undoes it, before the site publishes; the numbers from that run are on the front page and the trust page
  • The report names the processes that were running before and are not now
v1.4.0 · September 2026

Numbers, a page, a hash

  • Before and after, measured: processes, threads, handles, memory in use, three seconds of idle CPU and DPC time. The after-restart task writes the same six numbers
  • The report is also a page: numbers up top, kept-and-why, warnings, the BIOS checklist readable on a phone next to the BIOS screen, per-game settings, everything done. It opens in the browser at the end; the app has an Open the report button
  • A game running when you press Run gets a warning and a question first
  • The command checks the script against the hash published next to it before running it, and fetches again on a mismatch; a stale hash fails the publish check, so the two cannot drift
  • App: the target on its own line, labels that fit, Enter in the key box runs, the footer counts the run's time
v1.3.0 · September 2026

The app

  • The one command now opens a window: the PC as it read it, the process count and target, the advice, a tick box for every phase and every startup app, the options, the key, a live log and progress, and buttons for undo, the free report, the folder and restart
  • It is the same one file: the window is drawn from XAML held in the script and the work runs in a second PowerShell instance, so nothing is installed and the window never freezes
  • The console flow stays: $env:OMNIDX_MODE='console'
  • New switches: -Skip for phases, -NoRestart, -Probe (the PC as JSON), -Screenshot (draws the window to a PNG without showing it)
  • The Windows check draws the window on every change and the picture on the site comes from it
v1.2.0 · September 2026

The debloat

  • Thirty more app patterns: the new Outlook, Teams, Copilot, Edge's in-game overlay, the widgets runtime, and the games, media players, antivirus and shopping trials PC makers add. Removed for every account and from the image
  • OneDrive uninstalled when nobody is signed in to it; kept, minus its auto-start, when you are. Undo reinstalls it
  • Legacy Windows removed when present: Internet Explorer 11, the 2009 Media Player, WordPad, Steps Recorder, Math Input Panel, XPS printing, Work Folders, the PowerShell 2.0 engine. Fax and Scan stays with a printer, Hello face with a Hello camera. Undo re-enables each
  • Edge's shopping assistant, recommendations, Spotlight, feedback prompts and usage reporting off by policy
  • Kept gone: consumer features, suggested apps, silent installs, account nags and the "finish setting up" screen off by policy
  • Cleanup: temp files older than a day, the Windows Update download cache and the peer-to-peer cache, with the space freed printed
  • The free report lists the legacy pieces it would remove on your PC
v1.1.0 · September 2026

Reads more, asks better, proves the number

  • Shows what starts with Windows and lets you pick what stays on, by number, before switching the rest off
  • Offers to close Discord and Spotify so they can be tuned in the same run
  • Finds games through Steam's library list, Epic's manifests and the Riot and Xbox folders instead of crawling Program Files
  • Checks your RAM speed against its rated speed and says outright when XMP / EXPO is off; warns on single-channel memory, an old GPU driver, a display set below its refresh rate, no page file, Windows on a hard disk, less than 16 GB, an old Windows 10 build, running on battery, another optimizer installed
  • Keeps the Xbox accessory service when a controller is connected; notes OEM extras and third-party antivirus without touching them
  • Prints a target process count for your PC, and writes the after-restart count to a file by a one-shot task that removes itself
  • Tunes the signed-in account when a standard user gave an administrator's password at the prompt
  • Free report mode now lists exactly what would be switched off and kept on your PC, and saves it
  • New cuts: Recall, lock-screen ads, Windows Error Reporting, Store app pre-launch, Sticky Keys popups, the ten-second startup delay, receive segment coalescing, the Widgets host, NVIDIA telemetry and its crash-report tasks, eight more telemetry tasks, per-game I/O and page priority
  • Refuses Windows Server and PowerShell 7 with a plain explanation; warns on a work domain, a pending restart, a virtual machine and low disk space
  • Report lists what was kept and why, the games it found, a summary file and full before-and-after process lists; a transcript of the run is saved
  • The command fetches past caches, hands PowerShell 7 over to Windows PowerShell itself, and takes options from one more line
  • Keys can move to a new PC by yourself, once every 30 days, from the key page (with the licence server)
v1.0.0 · September 2026

The first one

  • Reads the PC and decides the safe bar from what it finds
  • Startup apps, services, scheduled tasks, preinstalled apps, telemetry and background activity cut; system, network, Discord, Spotify and browsers tuned
  • The OmniDx power plan, sixteen game profiles, a BIOS checklist for the board, GPU control-panel notes
  • Restore point, a record of every change, undo in one file
  • Keys locked to the PC: TUNE for one, SQUAD for five