Everything we know can go wrong, who it affects and what to do about it. Some of it is Windows doing what Windows does; some of it is a trade we made on purpose, and this is where it is written down. Found something that is not here? Tell us in the Discord.
The status command shows what is still in place on your PC: $env:OMNIDX_MODE='status'; irm omnidx.net/go.ps1 | iex
Who: Every PC tuned with 1.85.0 or later, unless the "Group service hosts" box was unticked.
What happens: Windows normally gives every service a process of its own. The tune lets them share again (about twenty processes fewer), as Windows did until 2017 and still does on PCs with less memory. If one service in a shared process crashes, the others in it stop too until Windows starts them again, usually within a minute. Sound, the network address and name lookups, Wi-Fi, Bluetooth, WMI (the part most often crashed by lighting and monitoring tools) and Windows Update keep a process of their own, so a crash elsewhere does not touch them.
What to do: Run the status command: it lists every service that stopped unexpectedly in the last seven days. If one keeps stopping and something stops working with it, run the tune again with $env:OMNIDX_FLAGS='-NoGroup'; irm omnidx.net/go.ps1 | iex (or untick "Group service hosts" in the app) and restart: every service gets its own process again. Tell us in the Discord which service it was.
Rare. Checked after every restart by the keep task, which writes any unexpected stop into its log.
Who: Everyone, after a big Windows update.
What happens: A feature update can reset service start types, switch scheduled tasks back on and put values back.
What to do: The keep task puts them back three minutes after the next sign-in, if you said yes to it. The status command lists what Windows put back. Or run the command again: same key, same PC, free.
Expected. It is what the keep task is for.
Who: Anyone who uses Edge or any app that uses Windows' old web engine.
What happens: Windows switches the task \Microsoft\Windows\Wininet\CacheTask back on by itself the next time that engine's cache is used, which brings one background process back.
What to do: Nothing: the keep task switches it off again quietly at each sign-in, and the status command does not count it as undone.
Known Windows behaviour, handled since 1.84.0.
Who: Windows 11 24H2 and later.
What happens: Resume and phone linking are switched off by the policy Windows' own files name for it, and the helper still starts with the shell on some starts and not on others (two filmed starts of the same setup: one with it, one without). It is one process, about 45 MB, and does nothing while Resume is off.
What to do: Nothing needed. Ending it in Task Manager is harmless.
Being looked into; this entry will say when it is fixed.
Who: Anyone who updates the network driver.
What happens: A new network driver starts with its own defaults, so Energy-Efficient Ethernet, Green Ethernet and the other savers are on again.
What to do: Run the command again after a driver update. On a Spanish, Portuguese or other non-English Windows these were missed before 1.84.0; they are found by their driver keyword now.
Expected.
Who: Rare: some older or unmanaged switches that rely on flow control.
What happens: The tune turns flow control off on the adapter you use. A few switches drop packets without it.
What to do: Device Manager › your network adapter › Advanced › Flow Control › Rx & Tx Enabled, or undo. OmniDx Hub leaves flow control on.
Known.
Who: Players of the games whose settings files the tune writes.
What happens: A game update, or the game itself on a new graphics setting, can write its file again.
What to do: Run the command again; it only changes lines already in the file and backs each file up first.
Expected.
Who: Anyone with them open during the run.
What happens: Their settings files can only be changed while they are closed; the tune offers to close them and skips them if you say no.
What to do: Close them and run the command again.
By design.
Who: PCs with Smart App Control on, or a work or school app control policy.
What happens: PowerShell is locked down, so the tune stops before reading or changing anything.
What to do: On a home PC: Windows Security › App & browser control › Smart App Control. At work or school: that PC is not yours to tune.
By design: it changes nothing rather than half-running.
Who: Anyone who picks the x86 PowerShell from Start's search.
What happens: The 32-bit PowerShell sees only half of Windows' settings. The one command switches to the 64-bit one by itself; the script run there by hand stops without changing anything.
What to do: Nothing, with the one command. By hand: open "Windows PowerShell", not the x86 one.
Handled since 1.84.0.
Who: Anyone whose Windows is not in English.
What happens: Before 1.84.0 a few checks read English names: the Wi-Fi advice, the network adapter's savers and the touch screen check. They read what the hardware reports now, in any language. The app, the report and the payment pages are in English.
What to do: Nothing. Ask in the Discord in your language.
Fixed in 1.84.0 and 1.85.0.
Who: Most home PCs.
What happens: The films run on a clean Windows in a virtual machine: no graphics driver, no sound card, no lighting software. A home PC adds its drivers' helpers (needed), anti-cheat (needed by its games), lighting, mouse and cooler software, and your apps.
What to do: The report's "still running, by who ships it" list says what each one is. Each lighting or mouse suite has its own "start with Windows" setting, or a switch in OmniDx Hub › Running.
Expected.
Everything it changes is written down first; setup.ps1 -Undo puts it back.
Who: A fresh install without a Wi-Fi driver yet, or with the cable out.
What happens: The tune needs omnidx.net for the key and the script. Since Edition 1.4.1 it waits up to two minutes for a connection and otherwise waits for a later sign-in (up to five); before that, it gave up.
What to do: Since Edition 1.5.0, make the stick on the same PC and answer Y to its drivers: the network and Wi-Fi drivers go in at the first sign-in. Otherwise connect, then sign out and in, or run it from OmniDx Hub › Tune.
Handled since 1.4.1; drivers on the stick since 1.5.0.
Who: PCs set up with Windows 10 (for hardware Windows 11 does not support).
What happens: Microsoft's free security updates for Windows 10 ended in October 2025. The Edition, the tune, games and drivers work the same, but the PC gets no new security fixes, and FACEIT needs Windows 11 from October 2026.
What to do: Windows 11 where the PC supports it, or Microsoft's Extended Security Updates for Windows 10. Setup says so at the end of a Windows 10 install.
Microsoft's decision; told up front.
Who: Only if you said yes to saving this PC's Wi-Fi network on the stick.
What happens: Windows exports a network with its password in plain text; the stick holds that file until the new Windows' first sign-in adds the network and deletes it.
What to do: Keep the stick to yourself until then, or say no and join the network by hand (a cable works without it).
By design, off unless you say yes.
Who: Every stick made with this PC's drivers.
What happens: Graphics drivers are large, and the maker's or Windows Update's is newer than the one on the PC, so the stick leaves it out; so are printers and firmware. Windows shows a basic display driver for the first minutes.
What to do: Nothing: setup's drivers step asks Windows Update for it, and OmniDx Hub › Drivers links the maker's page for the newest one.
By design.
Who: A stick made on one PC and used to install another.
What happens: Drivers go only on the hardware they are for, so the other PC's are simply not used; nothing breaks. The stick maker asks whether the stick is for this PC; making it again clears the first PC's drivers.
What to do: Answer N to the drivers when the stick is for a different PC; Windows Update installs that PC's drivers.
Harmless.
Who: Desktops set up with OmniDx Edition.
What happens: Setup switches off Realtek's helper on a desktop: sound and the jacks work without it, the Console does not.
What to do: OmniDx Hub › Running › Realtek Audio Console helper › on.
By design, one click back.
Who: Only if you switched off the NVIDIA Control Panel helper in OmniDx Hub › Running.
What happens: The Control Panel and digital vibrance need that helper.
What to do: Switch it back on in the same place.
By design; it is on unless you turn it off.
Who: PCs without Microsoft's WebView2 runtime (rare on Windows 11).
What happens: OmniDx Browser runs on WebView2; without it, setup leaves Edge as the browser and says so.
What to do: Windows Update installs WebView2; run setup again afterwards.
By design.
Who: Laptops at 150 % scaling and 1366 x 768 screens, before Edition 1.4.1.
What happens: The window's bottom edge was out of reach.
What to do: Nothing since 1.4.1: the windows fit the screen they open on, and pages scroll.
Fixed in 1.4.1.
Who: Windows 11 clean installs where Smart App Control was still evaluating.
What happens: The Edition's apps are compiled on your PC, so they carry no publisher's signature, and Smart App Control would block them. Setup switches it off while it is still evaluating; if it is already on, setup stops without changing anything.
What to do: Nothing, if setup ran. Defender, SmartScreen and the firewall stay on.
By design.
One line zips the logs, the PC as it was read and the change records to your desktop, with no key, no registry exports and none of your files: $env:OMNIDX_MODE='support'; irm omnidx.net/go.ps1 | iex. Attach it in the Discord or to an email. Undo is always one line: $env:OMNIDX_MODE='undo'; irm omnidx.net/go.ps1 | iex.