1. Installer will not run or CoreX will not launch
- Check that your system is Windows 10 (21H2+) or Windows 11 x64 and that the download completed.
- Re-download only from the official release page. Do not disable SmartScreen or antivirus to force a launch.
- If Windows displays a publisher or security warning, verify the source and signing information before proceeding. Cancel if it is unexpected.
- Restart Windows, try launching from the Start menu, and record any exact error text.
2. A dashboard reading is blank or does not match another tool
Not all PCs expose every sensor. GPU, temperature, fan speed, and storage health can depend on hardware, driver, WMI/SMART support, and vendor utilities. Compare after allowing a refresh, check that Windows drivers are current, and do not infer hardware failure from a missing reading alone.
CPU, memory, and network readings change as other processes run. Different tools may sample at different intervals or calculate utilization differently.
3. A UAC administrator prompt appears
Windows protects operations such as changing selected tweaks, adapter DNS, restore points, or protected cleanup targets. Approve only a prompt that follows an action you just started and whose purpose you understand. Canceling may stop that operation; it should not require approving an unrelated prompt. See the Permissions Guide.
4. A tweak failed or Windows behavior changed
- Read the specific tweak description and failure message. Check Windows version, policy restrictions, and whether another tool manages the same setting.
- Do not rapidly reapply the same tweak or apply many unrelated changes while troubleshooting.
- If CoreX provides a revert action, use it only after reading what it restores. The original value may have changed since the tweak was applied.
- Use Windows recovery/restore options only after reviewing what they will undo. A restore point is not a backup of personal files.
5. DNS change caused connectivity problems
- Check that the intended network adapter was selected and that its connection is active.
- Restore the DNS values you recorded before the change, or use the reset-to-default action if automatic network DNS is intended for your setup.
- Reconnect to the network or restart Windows if needed, then retry the connection.
- If a workplace, school, VPN, router, or security product controls DNS, contact its administrator rather than overriding its configuration.
6. Cleaner could not remove some files
Windows may lock files that are in use or deny access to protected locations. Close relevant apps and restart Windows if appropriate. Do not manually delete unfamiliar system files to work around a failure. Some cleanup targets, such as crash dumps, can be useful for support diagnosis.
7. Winget/Chocolatey app installation failed
Check the internet connection, package manager availability, package name, and installer output. A package can be unavailable for a Windows version, architecture, or source. Third-party packages are maintained independently of CoreX. Verify publisher and prompts before retrying; contact the package maintainer for package-specific failures.
8. Restore point could not be created
Windows System Protection may be disabled, storage may be insufficient, or Windows may reject the request. Check Windows System Protection settings, available disk space, and permissions. Do not assume a point exists until CoreX/Windows confirms success.
9. Where to find help and logs
The README lists CoreX logs under %APPDATA%\CoreX\logs\. Settings may be stored separately in the user profile; exact locations can vary by build. Open the app's log-folder action if available. Before sharing a log, inspect and redact private content, usernames, IP addresses, and local paths.
- Search existing reports and open a new issue at GitHub Issues.
- Include CoreX version, Windows version/build, the feature used, the exact steps, and what you expected versus what happened.
- For private privacy questions, contact help.mahinulislam@gmail.com rather than posting personal data publicly.