No matching sections. Try another search term.
Getting started and finding your way
Download and install CoreX from the official website, then sign in with a valid account. Rule management lets you review saved configurations; process management shows running programs; the core benchmark measures and compares cores. Identify the target program before changing its settings.
Available controls depend on your processor, whether the target is running, and the current configuration. An absent or unavailable option is not necessarily an error. Start with the existing settings and change one option at a time so that you can compare results and undo changes.
Back to contentsAdding a program and choosing how to manage it
Use the add control in rule management to select a running program, or browse for its EXE file. Check the name and path: a game launcher and the game itself may be different programs. You can prepare a configuration while the target is stopped, but saving it does not mean a running process has been changed.
Depending on the current state, the context menu offers joining a rule, saving an independent configuration, or managing only the current process. Following a rule and using an independent configuration are different choices. Do not treat temporary management as a persistent rule; check the current state before choosing an action.
Back to contentsEditing rules and checking the result
Select the target and open its advanced settings. For an existing independent configuration, you can also use its edit action in the context menu. Review the current values, change the required options, then apply and wait for the result. Avoid submitting again while a save is pending. Note the original values before editing.
Saved means the configuration was recorded; it does not guarantee that every runtime setting was applied. Read any partial-failure, incomplete-recovery or permission message. A closed window is not proof of success. Cancel does not undo changes already applied earlier; restore the original values and apply them when needed.
Back to contentsLeaving a rule and deleting an independent configuration
Open the target’s context menu and choose removal from a rule or deletion of its independent configuration, as appropriate. These actions differ: one changes rule membership; the other removes the independent configuration. Check the program name before confirming deletion. Deleting a rule does not terminate the program or its threads.
Wait for the result. If the message says the original configuration was retained or recovery is incomplete, do not treat deletion as successful. Resolve the reported issue before retrying; do not delete configuration files merely to dismiss an error.
Back to contentsCPU options and priorities
CPU affinity and CPU Sets are different processor-selection mechanisms, not interchangeable switches. Windows honours restrictive affinity settings when they conflict with CPU Set assignments. Check the active tab and selected cores before applying changes. Physical-core, SMT, P-core, E-core and CCD controls depend on your hardware.
CPU priority affects scheduling order, not processor frequency or a guaranteed speed increase. GPU, I/O and memory priorities concern different resources; do not set them all to the maximum. Real-time CPU priority can impair system responsiveness. Keep defaults unless you have a specific need, and check the application result.
Back to contentsBinding modes and scheduling pool overview
Binding modes select how CoreX manages the target. The scheduling pool is part of this configuration; enabling it can change which controls are available. Preferred core, companion core and automatic expansion options depend on the mode and hardware. Do not force unavailable options through other means.
Choose a mode, review the available options and core selections, then apply and check the result. Recheck the displayed values after switching modes. A mode name alone does not establish suitability. This guide covers operation, not internal binding strategies; no mode is promised to be faster for every program.
Back to contentsViewing and managing threads
In the process management dialog, switch to thread configuration to inspect thread IDs, names, CPU usage and state. Open the target thread’s management window and verify its owning process and ID. Set the required priority or core options, apply, and check for partial failures. A thread may exit while you are inspecting it.
Suspending a thread pauses its execution and may make its program unresponsive; resuming continues a previously suspended thread. These are not routine performance switches. Do not assume current-thread settings persist after a restart. If a thread is protected or access fails, follow the message rather than trying to bypass protection.
Back to contentsCore benchmarking and using the results
The core benchmark offers precision measurement and an all-core sprint. Select a mode, available scope and duration, then start. To finish early, stop and wait for completion. Close unrelated heavy workloads, keep the power mode consistent and compare repeated runs. Scores cannot be converted directly into game frame rates.
When available, using the recommended core only fills the preferred-core setting; you must still apply it. Reference-only results cannot be used through this button. A recommendation is not permanently optimal: background load, temperature and power conditions can change the measured result.
Back to contentsMemory cleanup and scheduled settings
The tray menu provides memory cleanup and scheduled-cleanup settings. Enable scheduling, adjust the interval, usage threshold and strength, and check the current scope. Intervals are in minutes. Automatic checks skip cleanup when memory usage is below the threshold. If saving fails, resolve the message rather than assuming the setting is active.
Lower memory usage after cleanup does not guarantee a faster program. Compare actual responsiveness rather than chasing the lowest number. To stop scheduled cleanup, disable it and save. This is separate from running a one-time manual cleanup.
Back to contentsExporting a backup and importing configuration
Use the configuration export action in settings, choose a destination and wait for the success message. Keep the resulting INI file: it contains configuration, not an installer. Back up your current settings before importing or making major changes. Review files before sharing them publicly, as they may contain local program paths.
Import supports INI configuration and legacy JSON rules. After selecting a file, review the result and any backup location, then inspect the rules and target state. Formats may contain different data. A successful import does not prove every running target was updated. Keep the error message and original file if import fails.
Back to contentsAccount, purchase and updates
The user center provides account details, license information and redemption. Purchase opens the official website in your external browser; check the selected regional edition. The international edition is not yet on sale. Changing the interface language does not change your license. Opening the sign-in window does not grant access when sign-in or license validation fails.
Use the client’s update prompt or download the new installer from the official site. Follow the setup wizard. If it reports a running old version, incomplete recovery or installation failure, keep the full message. Do not delete the old program and configuration to bypass checks. After updating, launch the installed copy and review your rules.
Back to contentsStartup, tray and pause controls
Closing the main window hides CoreX in the tray; it does not exit the program. To exit, use the tray menu and read any recovery message. A separate setting controls whether minimizing also hides it in the tray. Autostart opens CoreX on the next Windows startup but does not replace sign-in or license validation. Check for errors after changing it.
Pause and resume scheduling in the tray change the scheduling state. Pausing does not delete rules and is not proof that all settings have been restored. Resuming may be unavailable when the license is invalid or runtime recovery is incomplete. Resolve the license or recovery message first.
Back to contentsWhen settings do not take effect
Check, in order: sign-in and license state; target name and path; whether it is still running; rule-following versus independent configuration; whether you applied the change; and the result message. For threads, also verify that the ID still exists. Do not judge success or failure solely from old values in a list.
If the issue remains, record your CoreX version, the entry point, reproduction steps and complete error code. Hide phone numbers, redemption codes and personal information before sharing screenshots. Preserve your configuration for recovery and diagnosis. A UI issue does not require publicly posting internal logs or an entire configuration.
Back to contentsLanguage settings
Choose Language in Settings or the account center; both use the same preference. Save your edits, exit CoreX from the system tray, then start it again to apply the selected language. Closing the main window only hides it to the tray.
Changing the language does not change your rules or license. The China and international editions share one installer. The international edition is not yet on sale; downloading it does not grant an international license.
Back to contents