Ticket
QwenWorkA report that can be acted on
Nine out of ten 「it does not work」 reports cannot be reproduced. Five fields fix that, and none of them take more than a minute to gather.
The five fields
| Field | What to write | Why it matters |
|---|---|---|
| System | Windows 11 23H2 x64 / macOS 15.2 arm64 / Ubuntu 24.04 | Half of all issues are platform-specific |
| Version | 2.1.0, and the build date if you have it | Behaviour changed between 2.0 and 2.1 |
| Error text | Copy the exact string, or screenshot it | Paraphrasing loses the searchable part |
| What you tried | Network change, reinstall, cache clear | Prevents being asked to repeat steps |
| Timestamp | Date and local time of the failure | Lets the vendor check edge or API logs |
A report that gets answered
OS: Windows 11 23H2, x64 (msinfo32 reports x64-based PC)
Build: 2.1.0, package qwenworkcn-setup-x64.exe, 403 MB
Symptom: blank window on first launch after install, no error text
Already tried: two reinstalls, cleared %APPDATA%\QwenWork, switched networks
Time: 2026-11-19, around 10:20
Extra: corporate domain machine behind a forced proxyA report that gets a question back
"Installed it, it will not open, what now" — no OS, no build, no symptom, no time. The only possible reply is "please send your OS version", and two days disappear in one round trip.
Where to send it
Product defects go to the vendor's support, through the client's help menu or the official site. Problems with this site's pages — a wrong size, a dead link, an instruction that does not hold — go through the same form and are handled by whoever maintains the page.
Do not attach installers or logs containing personal data. If a log is needed, redact account identifiers first; a support ticket is not the place to leak a client's data.
Check the FAQ first — nine of the thirty entries are install failures with known fixes.