Your next version.
One step at a time.

What are you trying to do?

Use the right 0.10 file.

Choose a package on the 0.10 downloads page. Your browser checks its SHA-256 before you save it. Keep extracted files together.

All-user setup may request administrator approval. The tester and USB creator include their application runtime. The USB creator needs a separate, licensed Microsoft Windows ISO matching the exact source details shown in the app.

Install Reineryu Control.

1. Get the current-user setup.

   Download the 0.10 Reineryu-Control-Center-Setup.exe. Confirm that its release information says 0.10.3. Do not use a file named “Test Setup”; that is reserved for isolated developer tests.

2. Close any running copy of Control.

   Finish an active operation before closing. Keep a copy of any recovery records and captures you need.

3. Run setup and review its notice.

   Choose a dedicated installation folder, follow setup, and choose whether to add a desktop shortcut. Installing the app does not replace Windows or apply performance tweaks automatically.

4. Open Reineryu Control from Start.

   Check the version in the app, then follow the welcome steps below. The application runtime is included; you do not need a separate development SDK.

Update without reinstalling Windows.

1. Match your installation type.

   Use the current-user setup for an app installed only for your account. Use the OS all-user setup for the copy preinstalled with Reineryu OS. If you do not know the scope, confirm it with the developer before running setup.

2. Download the matching 0.10 preview installer.

   0.10 has not been published to the automatic update feed. Use the manual preview downloads; the app’s update check does not install this testing build.

3. Close Control, then run the matching setup.

   Keep the existing installation destination. Do not switch between current-user and all-user setup. The isolated installer test covered upgrading 0.9.1 to 0.10; a real all-user OS upgrade still needs external testing.

4. Reopen and check the update.

   Confirm the version, open Update Center, and choose Verify installed files and recovery database. Check that saved settings records and captures remain available.

Make Control yours.

Use Back and Next to move through setup. Finish later saves your progress. You can reopen the welcome flow from Update Center.

1. Welcome: review the preview’s scope.
2. Hardware overview: review detected hardware; unavailable values stay unknown.
3. Gaming priorities: save your preference.
4. Appearance: choose your app theme or open Windows Themes.
5. Performance profile: choose a benchmark protocol; this does not apply Windows tuning.
6. Driver readiness: review the reported health findings.
7. Game launchers: optionally discover installed games.
8. Optional utilities: review the tools included with Control.
9. Privacy: review local monitoring and data behavior.
10. Recovery readiness: review the recovery guidance.
11. Optional baseline: optionally save a reminder for the designated tester PC. No benchmark starts here.
12. Setup complete: choose Verify app and recovery database, then Save baseline and open Home.

The saved baseline records readable starting settings. App verification does not certify Windows installation, game compatibility, or recovery.

Use the switches, keep your originals.

1. Open Tweak switches.

   Search for a setting or filter by category. Expand the row to read its purpose, support limits, and recovery information.

2. Change one supported setting.

   On applies that control after any required review. Off restores the saved original value when a recorded change can be safely reverted. “Already set” can mean no Reineryu change exists to undo.

3. Respect disabled controls.

   Guided and unsupported settings stay disabled with an explanation. There are eight implemented reversible controls, not a completed set of every requested optimization. The custom image’s build 26300 remains outside the validated tuning range.

4. Check the result and keep recovery records.

   Use Recovery to review or restore recorded changes. Run controlled performance comparisons on the designated tester PC. Do not stack changes onto an unexplained regression.

Driver Health includes corrected inventory handling and firewall-profile reporting. Missing or unsupported readings remain unavailable and must not be read as a clean bill of health. Installation Diagnostics offers app verification, local Setup logs, and a diagnostic preview before export.

Try a CPU latency-hint experiment.

1. Open Tweak switches.

   Filter to CPU or search for “latency-hint”. Expand one control to read its behavior, build range and proposed value.

2. Review availability and the saved baseline.

   A missing API or unsupported Windows build keeps the switch unavailable. Energy preference also requires autonomous policy enabled. Example values are not measured recommendations.

3. Change only one control at a time.

   If you choose to experiment, select a value, turn on its switch and review the confirmation. Off restores the exact original value recorded for that power plan. Read the research and remaining work.

Prepare a custom Windows test.

1. Check the target PC and save the guide.

   Confirm Windows 11 x64 support, TPM 2.0, UEFI/Secure Boot, memory, storage, and device drivers. Windows Setup performs its own checks. Save this guide and the package’s START-HERE.txt somewhere you can access after restarting.

2. Extract the complete USB creator ZIP.

   On the designated external PC, extract Reineryu-OS-Media-0.10.3.zip to a local folder. Keep its kit folder beside Reineryu.MediaCreator.exe, then open the app.

3. Select the exact approved Microsoft ISO.

   Obtain your licensed Windows media directly from Microsoft. Its SHA-256, size, architecture, and build must match the source details in the creator. A different Windows release needs a reviewed source profile. Do not rename a different file to make it appear compatible.

4. Select a spare USB and prepare the files.

   Refresh the USB list and identify the drive by model, capacity, and serial. Testing supports eligible 16–256 GB USB drives. Confirm your authorization to use Windows and choose Prepare installation files. Approve the app’s Windows prompt using the same account.

5. Confirm the exact USB before erasing it.

   Back up every file on that USB. Review its identity and type the requested ERASE USB confirmation including its number. Formatting erases that USB. Wait for preparation, copying, and verification to finish; a failed run is not usable installation media.

6. Boot the separate test PC from the USB.

   Use the device maker’s boot menu and choose the UEFI entry. Keep TPM and Secure Boot enabled. Follow Windows Setup, select your licensed edition, and carefully identify the intended test disk. Setup still asks for disk, account, and privacy choices.

7. Verify the first sign-in.

   Reineryu Control is intended to be preinstalled. Confirm that it opens from Start, complete the welcome flow, then check networking, device drivers, Windows Update, reboot, and recovery. If Control is missing, preserve Setup logs and report a failed preinstallation test; manually installing it does not turn that test into a pass.

The Windows image is not included in the public packages. The local 0.10.3 ISO has now been assembled: 8.47 GiB, with 1,001 files matching the assembly inventory. Boot, installation and reset were not tested. Read the latest image status.

Microsoft Windows download → Windows 11 requirements →

Run the standalone tester.

1. Open the standalone tester.

   Extract Reineryu-Tester-0.10.3.zip, or open the copy under kit/testing in the USB creator package. Run Reineryu.Tester.exe.

2. Collect the installation checks.

   Choose Run read-only checks on the installed test system. Work through the 16 manual observations and mark each one Passed, Failed, or Not tested according to what actually happened. Save screenshots and Setup logs as supporting evidence.

3. Test recovery as separate operations.

   On the disposable installation, test recovery boot, Keep my files, and Remove everything separately. Check Control, another user account, Windows Update, and sign-in after each reset. Use the tester’s separate interrupted-install recovery observation; only exercise failure recovery on a disposable system.

4. Measure games on physical test hardware.

   Read the tester’s START-HERE.txt before starting. Save the study outside the OS disk, record stock and candidate identities, and collect the required matched A/B and holdout pairs under the same conditions. Capture starts only when the tester explicitly starts it. The development PC and recognized VMs are blocked from live gaming capture.

5. Export, review, and send the results.

   Use Save results ZIP for installation results. Backtest and export the FPS/delay study separately. Review files for personal information, then send them to the developer through your agreed channel. Nothing uploads automatically.

Frame timing and software event delay do not measure physical mouse-switch-to-pixel latency. Missing results stay unavailable, and exported reports never grant consumer-release status automatically.

Repair the app. Preserve the evidence.

Use the new Game Hub

1. Open Gaming in Control.
2. Choose Find installed games.
3. Search by name or choose a launcher. Use Add favorite to keep a title in your favorites.
4. Choose Play in Steam for a supported Steam game. Open Epic titles through Epic Games.

These buttons do not apply a performance profile. Game compatibility and real FPS results still require measurements on the tester’s PC.

Software checks, clearly scoped.

The 0.10.3 preview passed 152 core checks, 116 PowerShell checks and 42 native UI checks across 22 pages. Read current verification and remaining release gates. These checks do not establish real gaming improvements or successful Windows installation.