1. What administrator access is for
Windows protects certain settings and files. CoreX may need administrator privileges for the system-level operations you choose, including applying or reverting selected Windows tweaks, changing or resetting DNS/network settings, managing restore points, and cleaning protected Windows locations. The exact operation depends on the feature and Windows configuration.
| Feature | Why elevated access may be needed | Your control |
|---|---|---|
| Windows Tweaks | Some tweaks edit protected registry values, services, scheduled tasks, or other system settings. | Choose which tweak to apply or revert; review its description and create a backup or restore point first. |
| DNS and network settings | Windows may require elevated rights to change adapter DNS settings, reset them, or flush the DNS cache. | Start the operation yourself and confirm any Windows approval prompt. |
| Restore points | Windows System Protection operations are protected system tasks. | Request creation or management of a restore point; Windows may require approval and system protection must be available. |
| Cleaner | Some system temporary, update-cache, or dump locations are protected. | Select the cleanup operation; review what it targets before confirming. |
| App installation | An installer or package manager may request access depending on the package and its install scope. | Choose the app to install. Review any Windows or package-manager prompt before approval. |
2. What happens if you decline
If you cancel a UAC request, the operation that required elevation may stop or fail. Other non-privileged features can remain available. You may also close CoreX without approving the request.
3. Network connections
CoreX can connect to third-party services for the functions described in its Privacy Policy, including PostHog analytics, GitHub update checks, and diagnostics you manually start. These network connections are separate from administrator permission. An administrator prompt does not mean CoreX receives your passwords or account credentials.
4. Use only on systems you may administer
Use CoreX only on your own PC or a device you are authorized to manage. On a work, school, shared, or managed device, follow the owner's or organization's rules. A Windows administrator prompt is not permission to override those rules.
5. Before system changes
- Read the explanation for each tweak or operation.
- Create a restore point where appropriate, and back up important files separately.
- Apply changes one at a time so you can identify unexpected effects.
- Do not approve a prompt you did not expect or cannot explain.
6. Contact
Questions about permissions or an unexpected prompt: email help.mahinulislam@gmail.com or report it at GitHub Issues.