Contact
This site and CoderBag LLC, the company that makes Quick CPU, are two different parties — this site is a guide library; Quick CPU itself is developed by CoderBag. Who to contact depends on what you need, so this page routes both correctly rather than pretending to be one unified support desk.
Contact quick-cpu.org
For anything about this site itself — a factual correction, an outdated screenshot, a broken link, or general feedback on the guides and comparisons — email contact@quick-cpu.org. This is the right address for content issues: something this site got wrong, missed, or should cover that it currently does not.
What this address is not for: Quick CPU technical support, bug reports in the app itself, or account/licensing questions. None of that is something this site can act on, since it does not build or maintain the software — see below for the actual publisher's contact.
Contact CoderBag about Quick CPU itself
For anything about the app — a bug, a crash, a feature request, or a question about how a specific setting behaves — the right contact is CoderBag directly, the company that develops and publishes it. Their support address, support@coderbag.com, is listed in the app's own About dialog (Help → About), which is worth confirming for yourself rather than taking any third-party site's word for it, this one included.
See our page on who makes Quick CPU for what is and is not publicly known about CoderBag, and coderbag.com for anything this site does not cover.
Reporting a bug or issue effectively
If you are reaching out to CoderBag about something not working correctly, a few details make the difference between a quick fix and a back-and-forth: the exact Quick CPU version (Help → About), your Windows version, your CPU model — see system requirements if you are unsure which of those matter — and the specific steps that trigger the problem. Screenshots of the actual behaviour, rather than a description alone, tend to get resolved faster.
If the issue is something this site can actually help with instead — a guide that describes a menu location that has since moved, for instance — mentioning the specific page and what changed helps far more than a general "this is outdated" note, since it lets a correction get made precisely rather than guessed at.
Response times and scope
This site is maintained independently and cannot promise a specific response time, though genuine corrections and clear bug reports are read. It also cannot speak on CoderBag's behalf about their own response times, refund or licensing questions (Quick CPU is free, so this rarely comes up), or feature roadmap — those questions belong with CoderBag directly, not with this site.
Looking for something else first?
The FAQ covers most common questions about installing, using, and troubleshooting Quick CPU.
Go to the FAQ