Safety
Every change is shown, recorded, verified and reversible.
Optimizers get a bad name by changing things quietly and leaving no way back. This is exactly how Nexus works instead, in plain words.
The life of a change
Preview
Exact current and new value of every setting.
Snapshot
The original state is recorded before any write.
Write
One UAC prompt, only if the change needs admin.
Verify
The value is read back. Partial failures are undone.
Record
The change and its original go into Restore Center.
Undo
One click writes the recorded original back, verified.
Preview: see it before it happens
Whether you switch on one tweak or apply a whole pack, Nexus first opens a review screen. Each change is listed with the exact setting it touches, its current value on your PC and the new value. Anything already in place says so. You can untick any item, and nothing is written until you confirm.
Snapshot: the original is recorded first
Before anything is written, Nexus records the original state of every setting the change will touch: registry values (including whether they existed at all), service start types, scheduled task states, power settings and system parameters. If Nexus creates a registry key that didn't exist, it remembers that too, so undoing removes it again while keys shared with other settings stay.
Write, then verify
After writing, Nexus reads every value back to confirm the change actually took effect. If a value doesn't read back as expected, the result says so instead of reporting success. No two tweaks own the same setting, so undoing one can never undo part of another.
When a change fails part-way
Many tweaks change several settings at once. If one part fails, for example because a policy blocks it, Nexus undoes the parts it already applied, using the snapshot it took a moment earlier. You never end up with half a tweak.
Record and undo
Every change goes into Restore Center with what it changed and the original value. From there you can undo one change, a group, or the last change, or simply switch the tweak off. Undoing writes back the recorded original, not a generic “Windows default”, and is verified the same way.
Protection against tampered history
The change history is a file on your PC. Restoring only accepts entries that belong to the tweak being restored: a registry path, service or task that isn't part of that tweak's definition is refused. A modified history file cannot make Nexus write somewhere else.
Dry-run mode
Switch on Dry run in the review screen and Nexus walks through the same steps, reporting what it would change, without changing anything. Use it to check a pack on a new PC before applying it.
Standard user, one UAC prompt per change
Nexus runs as a standard user. Some settings can only be changed by an administrator, such as machine-wide policies, services and scheduled tasks. For those, Windows shows one UAC prompt for that operation only. The elevated helper accepts only IDs from Nexus' own catalog, never a command line or a file. If you cancel the prompt, nothing is changed. There is no background service and no startup entry.
Windows restore points
Restore Center lists your Windows System Restore points, creates new ones and verifies that they were actually created. Make one before a big round of changes. It's a second, independent safety net that also covers drivers and system files.
One-way actions are labelled
A few things cannot be undone by their nature: uninstalling OneDrive, removing preinstalled Store apps, deleting temporary files and running repairs. They are labelled, ask for an explicit confirmation, and say what happens next. Every removed Store app keeps a Microsoft Store link to reinstall it.
Only documented settings, only where they apply
Tweaks use Group Policy, documented registry values, powercfg settings, SystemParametersInfo, service start types, scheduled tasks and documented PowerShell cmdlets. Each one is checked against your Windows build, edition, installed apps and network adapter; anything that doesn't apply is shown as not applicable instead of pretending to work.
On every build, the test suite applies, verifies and restores 358 of the 402 tweaks against a simulated system and checks that restoring leaves it exactly as it was. The rest (PowerShell, per-adapter and app-specific settings) are checked read-only on a real PC.
Popular “FPS tweaks” with weak evidence, like disabling Nagle's algorithm or core parking, are offered because people ask for them, but honestly labelled: Limited evidence, never recommended, never applied in bulk, and restored exactly. If you try one, measure before and after with the Benchmark.
What Nexus refuses to do
Some changes are popular in optimizer tools. Nexus won't make any of them, and here is why.
| Nexus never… | Why |
|---|---|
| Disable Defender, the Firewall or SmartScreen | They are security features. Any gain is a few percent at most, and the risk is your whole PC. |
| Disable Windows Update | It leaves you unpatched and breaks Store and driver updates. |
| Turn off VBS or HVCI | Core isolation protects the kernel. Nexus explains it in the BIOS Guide but never switches it off. |
| Edit boot configuration (bcdedit timer tweaks) | Boot changes can trigger BitLocker recovery and break timing on modern CPUs, with no reliable gain. |
| Edit the hosts file | Defender flags it as tampering, and it breaks Microsoft services unpredictably. |
| Install drivers | Kernel-mode drivers are a stability and security risk. Nexus never installs one. |
| Run “RAM cleaners” | Windows already manages memory. Purging caches causes stutter, not FPS. |
| Apply undocumented registry “FPS packs” | Undocumented values with no evidence are often ignored by Windows, or harmful. |
| Add itself to startup or send telemetry | Nexus runs only when you open it. Its one check-in is your account sign-in; no usage data is uploaded. |