# Ember Optimizer

A portable Windows desktop optimizer with an original dark interface inspired by the supplied examples. It includes a real hardware scanner, an individually selectable tweak library, a small recommended profile, and recovery for registry changes.

**71 choices: 40 current-user registry settings, 19 optional app removals, and 12 manual guides.** The 59 automated choices include gaming settings, desktop preferences, privacy options and debloating. They are not 59 independent ways to increase FPS.

## Download and run

The primary website download is **Ember-Setup-1.0.exe**, a per-user Windows installer. Open it, choose whether to create a desktop shortcut, and click **Install Ember**. The default location is `%LOCALAPPDATA%\Programs\Ember Optimizer`. Setup adds an entry to Windows Installed apps and a Start-menu shortcut. Opening Ember after setup is optional. Setup does not apply any optimizer settings.

To uninstall, close Ember, then use Windows Settings → Apps → Installed apps → Ember Optimizer, or open `Uninstall-Ember.exe` in its installation folder. Restore tweaks in Ember first if you want them reversed: uninstalling the app leaves your settings and `%LOCALAPPDATA%\EmberOptimizer\backups` intact. Modified app files are preserved for review rather than deleted. A temporary uninstaller helper can remain in Windows Temp until normal cleanup.

The portable ZIP is also available as an alternative:

1. Extract the entire portable ZIP to a folder you can write to.
2. Double-click `Ember.exe`. Keep `Ember.exe.config` beside it.
3. Let the scanner inspect your PC. Opening Ember or running a scan does not apply tweaks.
4. Review the individual benefits and tradeoffs, select a small batch, then use the apply action. Save work and sign out/back in afterward when needed.

Requirements: Windows 10 or Windows 11, x64, .NET Framework 4.8, and built-in Windows PowerShell for app inventory and optional Appx removal. Current Windows 11 systems include the needed framework. No administrator account is required for the supported actions. Use a Windows release that still receives security updates.

This is a custom, unsigned build with source included. Windows may show an unknown-publisher or reputation prompt; verify the source and included file hashes before choosing to run it. Do not disable antivirus, SmartScreen, or other protections to use the application.

## Your Ryzen 5 7600X build

The requested target is a Ryzen 5 7600X, 32 GB DDR5 rated for 6000 MT/s, integrated Radeon graphics, and an approximately 932 GB SSD. Ember reads the running machine instead of presenting those requested specifications as measured facts. Firmware, drivers and WMI can leave some fields unavailable; SSD capacity and volume free space are different measurements. The RAM kit's rated speed may differ from its configured rate.

AMD lists two graphics cores for the 7600X's integrated Radeon GPU. That small GPU will often be the limiting component in demanding games. Registry changes cannot turn it into a dedicated gaming card. Lower in-game rendering resolution, suitable quality settings, compatible drivers, and correct memory configuration are the practical priorities. A large FPS improvement is not guaranteed.

Start with the **seven recommended registry settings**: Game Mode, three related capture preferences, desktop transparency, taskbar animation, and window minimize animation. The capture changes are useful when you do not need Windows recording, and they may do nothing for performance if recording was already off. Related capture controls are counted as separate settings, not additive performance gains.

Desktop appearance changes mainly affect Windows and Explorer. Privacy options mainly affect personalization. Removing a dormant app usually does not improve gaming FPS. The UI describes these distinctions for every entry; the selected or active count is not an optimization percentage or benchmark.

## Scanner and measuring performance

The scanner reads hardware and Windows information on the PC where Ember runs. It does not upload the hardware inventory. The dashboard reports specifications, not FPS, input latency, temperatures, live utilization or an estimated performance gain. Some hardware data may be unavailable or reported differently by firmware and Windows. Export the PC report from Recovery for motherboard, OS, driver details and any scan warnings.

For an actual comparison, run the same game's benchmark or route three times before and after a small batch. Keep resolution, graphics settings, driver, scene and background apps fixed. Compare average FPS and 1% lows. Keep a change only if its behavior and tradeoff work for you.

## Registry compatibility and recovery

All automated registry edits are confined to the signed-in user's `HKEY_CURRENT_USER` hive. Ember records the original value, its type, and whether the value existed before writing. Recovery restores that prior state, including deleting a value that was originally absent, when the recorded state permits it.

Backups are stored in `%LOCALAPPDATA%\EmberOptimizer\backups`. Keep that folder if you want to undo registry changes later. These are setting-level journals, not complete PC backups or Windows restore points. Avoid editing the same setting with another optimizer between applying and restoring; recovery may report a conflict rather than overwriting a later change.

An **Active** or matching status means the registry currently contains the target value. It does not establish that Windows is honoring that value, that the feature is active, or that performance improved. Many UI preferences are cached and need a sign-out/restart. Some Windows versions ignore or replace legacy preferences, especially content-delivery subscriptions, Peek and older Game DVR controls. Application state, Windows policies and updates may also override a preference. See `SOURCES.md` for scope and documentation limits.

No automated tweak changes boot configuration, timers, HPET, CPU overclocking, memory timings, services, network stack settings, Defender, firewall, UAC, Windows Update, or security mitigations.

## Optional app removal

The Debloat list contains **19 exact package names**. Only an installed matching package for the current user is eligible. Missing packages are skipped; newer Windows releases may already omit several legacy apps. There are no wildcard, all-user or provisioned-image removals. Windows Store, Xbox identity and gaming services remain outside the removal catalog.

Read each app's tradeoff before removal. Export local recordings, mail, tasks, flows and other data you need. Uninstalling an app can remove its local data. App removal is **not reversed by registry recovery**. A supported app may be reinstalled manually through Microsoft Store, but availability and data recovery are not guaranteed, especially for retired apps. Removing a legacy app may be permanent.

## Guides

The 12 guides explain hardware and game settings that need your judgment. They open the relevant Windows Settings page or an official AMD page, and do not silently apply those changes. EXPO/6000 MT/s is memory overclocking: support and stability depend on the CPU, motherboard and kit. Ember does not modify UEFI settings or assume that the kit's advertised rate is stable.

## Source and build

The `source` folder contains the C# source, manifest, resources and `build.ps1`. Build it from Windows PowerShell in that folder:

```powershell
.\build.ps1
```

The script uses the local .NET Framework x64 C# compiler and WPF assemblies, with no downloaded build dependencies. The compiled application is written to `source\build` by default. `catalog.json` is a readable reference for the packaged tweak entries. See `LICENSE.txt` and `SOURCES.md`.

The executable also provides read-only export modes. Use full output paths:

```powershell
.\Ember.exe --scan C:\YourFolder\hardware.json
.\Ember.exe --inspect C:\YourFolder\tweak-status.json
.\Ember.exe --catalog C:\YourFolder\catalog.json
```

Building the package and inspecting the PC do not activate tweaks. Apply/remove operations are explicit UI actions. Validation uses an isolated simulated registry, not live PC optimization settings.
