Is this safe? Is it a scam?

Three things to check before you pay a cent

None of these need a key, an account or a card.

📜

Read what it changes

Every service, task, app and registry value it touches is listed with the reason on Everything it touches, written by a tool that reads the script itself. The free look's copy of the script, omnidx.net/tune/look.ps1, is the tune with every part that changes Windows taken out, and the one-line bootstrapper is at omnidx.net/go.ps1. There is no compiled part and nothing obfuscated.

The full script comes with your key. To read the exact copy the one command would run on your PC (the one the Windows check tested, byte for byte) before it runs, this asks for your key, saves it to your desktop, shows its SHA-256 next to the published one, opens it in Notepad, and does nothing else. No administrator rights:

$env:OMNIDX_MODE='read'; irm omnidx.net/go.ps1 | iex

📋

Run the report mode

Free, no key. It reads your PC the way the tune does and counts your processes, then stops without changing anything. Watch what it says it found; if it has your machine right, it will cut around it right.

$env:OMNIDX_MODE='report'; irm omnidx.net/go.ps1 | iex

🧪

It is run before it is published

Every change to the script is parsed by PowerShell on a Windows build machine, run in report mode, then run for real with a key, then undone, before the site publishes it. The last run:

Every verified run the site has recorded, newest first

Script	Date	Processes	Changes	Run	Free look	Errors

One line per run of the check on its Windows build machine (a bare server image, not a gaming PC). "Processes" is the count before and after the tune without the restart the check never does. "Free look" is the report mode's own timing, which swings with the machine's cold start; the read's laps are steadier.

What that check proves, every push

Both scripts parse; the free report reads the machine and changes nothing; the app window draws
The whole tune runs with a real key and reaches Done; the support bundle is written with the key masked
Status finds every recorded setting still in place, and no task of the tune is left to run at sign-in
A service, a task and a policy value are turned back on by hand; keep.ps1 sees all three without changing anything, then puts them back when it is run; a value it may not read is left out, never reported missing
A second run finds the bound key without being given it, records a handful of changes, leaves a startup app you turned back on alone, and takes down the sign-in task versions before 1.117.0 left
A third run with Extreme on top records its extras and leaves status clean; undoing that run alone puts only Extreme back and leaves the tune standing; then undo walks back the rest, leaves no record behind, and one more undo says there is nothing left
A bad key is refused; keys from the key tool are accepted and a corrupted one is not
A run that records noticeably fewer changes than the last published one fails, so a change that quietly stops doing something cannot ship
Every capture of the script's output in the check, fourteen of them, is scanned for PowerShell's own error text; the count is in the published run record with the lines around each, and a count above the last published run's fails the check, so what a buyer sees on screen cannot get noisier unnoticed
The one command itself is run end to end against a copy of the site on the build machine: it must fetch the verified copy, match its hash and run; with the served copies altered by one line it must refuse to run anything
Every page of this site is opened in a real browser at desktop and phone width before it publishes, and the key page and the buy buttons are driven against stand-in answers: no page that throws, sells with the key desk shut, shows the wrong keys, carries a dead link or anchor, or fails a WCAG A or AA rule (contrast, names on links, keyboard reach) in either the dark or the light look goes live. The key page is also driven against the real licence-server code, with a stand-in Square and mail server: land from a payment and the key is on screen, a refund shows as refunded
The licence server's money path runs offline on the same push, and before every deploy of it: a Squad payment mints three keys and sends one email, a repeat sends nothing, a bad signature is refused, each key locks to one PC and a second is refused, a refund switches the keys off, a partial refund tells the owner once instead of touching a key, and guessing is shut out: twenty wrong receipt numbers, ten wrong owner tokens or forty made-up keys from one connection close that connection for ten minutes while everyone else is served
Only a script that passed all of the above is what your command fetches: the check publishes the exact copy it tested next to its hash (tune/verified.json), and the one command asks for that copy, not the newest push

🔎

Watch what it sends

Open Resource Monitor's network tab while it runs. You will see three requests to omnidx.net (the config, the record the Windows check wrote with the hash of the copy it tested, and that copy of the script, refused if it does not match) and, if a licence server is configured, one to it with your key and the PC fingerprint. That is all. The report stays in C:\OmniDx. And every service, task, app and value it touches is listed, generated from the script itself.

The straight answer

What it is

A PowerShell script that does, in one run and with a record, what a careful person would do by hand over an afternoon with Task Manager, Services, Settings and powercfg: turn off what runs for Microsoft rather than for you, set a power plan that keeps the CPU awake, tune the network adapter for latency, and set three per-game flags Windows never sets on its own. Then it writes you a BIOS checklist, because the biggest gain on most PCs is below Windows and no script can flip it for you.

What it is not

It is not a driver, a kernel module, an overlay, a "booster" that stays resident, or a thing that injects into games. It does not overclock anything, does not touch voltages, does not flash your BIOS, and does not turn off anything that protects you. It is also not magic: if your GPU is the bottleneck, fewer processes will not change your frame rate, though your frame times will get flatter.

Why it needs administrator rights

Because stopping a service, disabling a scheduled task, changing a power plan and writing to HKLM all need them. There is no way to do this job without them, which is exactly why you should read the file before you let it. It asks Windows for the rights itself, through the normal prompt, so you see the request.

Why it costs money

Because it took a long time to get right — which services a laptop needs, which anti-cheat breaks if you touch what, what the 2013 tweaks do to a 2025 PC — and because a key is what lets one person's purchase be one person's. The price is one you can pay without asking anyone, once.

What it will not touch, and what it cannot do

A tool that only lists what it does is hiding the other list. Here is the other list.

🛡️

Never touched

Microsoft Defender, the firewall, SmartScreen, UAC
Secure Boot, TPM, BitLocker
The Windows Update service — the standard tune leaves it updating by itself (it only never restarts the PC while you are on it); Extreme puts updates on your say-so, and Check for updates always works
Vanguard, Easy Anti-Cheat, BattlEye, Ricochet — or any game's files
Your drivers: nothing installed, updated or removed. It reads them and tells you which are old or missing, and where the maker's newest is
Your files, browser history, tabs, extensions, passwords
OneDrive when you are signed in to it, and your OneDrive folder either way
Voltages, clocks, fan curves, the BIOS itself — the checklist is paper
Memory integrity, unless you pass -Aggressive and then say yes again

🚫

Cannot do

Make a GPU-bound game faster — that is your graphics card's job
Fix thermal throttling — that is your cooler's
Change BIOS settings for you — nothing running under Windows can, and anything that claims to should worry you
Promise a specific process count — it prints yours, before and after, and the safe bar is different on every PC
Run on Windows 7, 8, a Mac, or Linux
Stop Windows Update from putting a startup app back — run it again; the key is yours

One honest limit on the lock. The key is bound to the first PC that runs it, and omnidx.net hands the full script only to a key, for that PC. Someone who bought it could still edit the check out of their own copy. The lock is there to keep one purchase one purchase, not to fight that person.

What leaves your PC

The full list, with where each piece is kept and for how long, is on the terms and privacy page.

🔑

The key check

Your key, a fingerprint of the machine — a hash of the board serial, the system id and the CPU id, which identifies the PC without describing it — and the CPU and GPU names so your own machines can be told apart. Only when a licence server is configured; otherwise the key is checked and bound on the PC itself.

🚫

Not the report

What it found, what it changed, the process counts and the BIOS checklist are written to C:\OmniDx and nowhere else. Nothing about your PC is uploaded.

📵

Nothing, afterwards

Nothing stays running, so nothing can phone home later. The only process of ours you will ever see is the PowerShell window while it runs. One exception, disclosed and offline: a task that runs once at your next sign-in, counts processes, writes the number to C:\OmniDx\after-restart.txt and deletes itself (-NoAfterCount skips it). Nothing watches for Windows updates: since 1.117.0 there is no keep task, and what an update turns back on is put back when you ask (run the command again, or the OmniDx Hub's Put them back).

"A script from a website that wants admin rights?"