What happened?
A Windows user reported that after installing PawWork, there is no desktop shortcut. They have to open the installation folder manually and create or locate a shortcut themselves.
For non-technical users, this makes the app feel missing after installation and adds unnecessary setup friction.
Which area seems affected?
Platform shell, packaging, updater, signing, paths, or permissions
Impact
Makes a workflow harder, but there is a workaround.
Priority triage
P1.
Windows is in the current product scope, and this sits directly on the install-to-open path. Even though a technical workaround exists, the default installer should leave users with an obvious way to launch PawWork. For non-technical users, no desktop shortcut can look like the install failed.
Steps to reproduce
- Install the current Windows PawWork installer.
- Finish installation with the default options.
- Check the Windows desktop.
- No PawWork desktop shortcut is created.
Expected behavior
The Windows installer should create an obvious launch entry by default. At minimum, it should create a desktop shortcut or make the shortcut option clear during installation.
PawWork version
Reported after the 2026.5.7 update announcement. Exact installed version not yet confirmed.
OS version
Windows. Exact version not yet confirmed.
Reproducibility
Reported by Zhang Jiawei in the Chunke AI Workbench Lark group on 2026-05-08. Needs confirmation against a fresh Windows install.
Scope boundary
This issue only tracks the missing desktop shortcut after Windows installation. A separate report about the Windows client becoming invalid after about a week needs more symptom details before filing or fixing.
Verification
- Build or inspect the Windows installer configuration and confirm the intended shortcut behavior.
- Verify a fresh Windows install creates the expected launch entry by default, or clearly presents an install option if that is the chosen product behavior.
- Keep the fix scoped to launch-entry behavior. Do not bundle the separate "client becomes invalid after about a week" report without a reproducible symptom.
What happened?
A Windows user reported that after installing PawWork, there is no desktop shortcut. They have to open the installation folder manually and create or locate a shortcut themselves.
For non-technical users, this makes the app feel missing after installation and adds unnecessary setup friction.
Which area seems affected?
Platform shell, packaging, updater, signing, paths, or permissions
Impact
Makes a workflow harder, but there is a workaround.
Priority triage
P1.
Windows is in the current product scope, and this sits directly on the install-to-open path. Even though a technical workaround exists, the default installer should leave users with an obvious way to launch PawWork. For non-technical users, no desktop shortcut can look like the install failed.
Steps to reproduce
Expected behavior
The Windows installer should create an obvious launch entry by default. At minimum, it should create a desktop shortcut or make the shortcut option clear during installation.
PawWork version
Reported after the 2026.5.7 update announcement. Exact installed version not yet confirmed.
OS version
Windows. Exact version not yet confirmed.
Reproducibility
Reported by Zhang Jiawei in the Chunke AI Workbench Lark group on 2026-05-08. Needs confirmation against a fresh Windows install.
Scope boundary
This issue only tracks the missing desktop shortcut after Windows installation. A separate report about the Windows client becoming invalid after about a week needs more symptom details before filing or fixing.
Verification