Support

Two channels, both read by the developer directly.

Updated 8 August 2026

Where to write#

Both are read by the person who writes the code. Feature requests are as welcome as bug reports: with no telemetry there is no other way to learn what people actually want changed.

Before writing#

Most reported problems are covered by Troubleshooting — an empty desktop, boards off-screen, a freeze caused by an offline network location, startup not sticking. It is worth thirty seconds.

What makes a report useful#

  1. Your DeskDrawer version — currently 1.2.5; see release notes.
  2. Windows version, and whether the desktop is backed up by OneDrive or another sync client.
  3. What you did, in the order you did it.
  4. error.log, from the tray menu → Open the configuration folder. It is plain text, you can read it before sending, and it makes a fix far more likely.

If the problem involves a freeze, mention whether any network drive, VPN or NAS was disconnected — that is the cause of nearly every freeze this product has had. See The same bug, five times: offline network locations.

Why your report matters more than usual#

DeskDrawer has no Telemetry. No crash reporting, no analytics, no usage data. When something breaks on your machine, nothing tells the developer — not the fact, not the frequency, not the Windows build.

That is a deliberate privacy decision with a real cost, explained in Shipping with no telemetry, and what it costs. The practical consequence is that your report may be the only signal a problem exists.

Response#

DeskDrawer is built by one person, so replies are not instant. Every report is read by the person who writes the code — there is no queue in between. When a report leads to a fix, that fix ships through the Microsoft Store and the release notes name the version it landed in.

Refunds#

Microsoft Store purchases are covered by Microsoft's refund policy and are requested through your Microsoft account rather than from the developer. See Licensing.