Safety, reliability & recovery

Picketdesk is built around one promise: it can never lose a file or an icon. Here is the machinery that keeps it — and, if something ever looks wrong, exactly which lever to pull.

The three safety nets

A picket's files are hidden from Explorer while Picketdesk draws them. Three independent mechanisms make sure they always come back:

  1. Clean exit. Quitting Picketdesk un-hides every file it hid and leaves a receipt on the desktop that lists them. Once that restore has started, nothing in the app hides a file again before it exits, so your files cannot vanish a second time on the way out.
  2. The watchdog sibling. A separate process watches the app; if Picketdesk is killed hard, the watchdog restores the icons automatically. It is started so that it is not part of Picketdesk's process tree, so ending Picketdesk's whole tree does not end the watchdog with it. It is itself watched: Picketdesk checks every 30 seconds that the sibling is still the process it started, and re-arms a new one if it was killed — so the net cannot quietly go down and leave you unprotected without anyone noticing. Only a run of quick losses stops it: if three new siblings in a row are gone again within ten minutes (a start that antivirus blocks or kills at once), Picketdesk stops trying, writes so in picket.log, and Settings → Safety shows the net as down. It then tries once an hour, so a block that lifts later does not leave the rest of the session without a net. A sibling that stayed up longer is always replaced. It does not depend on the ledger file either: if workspace.json is locked when the app dies it waits a few seconds, if it is unreadable or corrupt it walks the rotated backup instead, and in every case it also sweeps the desktop for files carrying Picketdesk's claim marker — the same evidence the launch sweep spends.
  3. The manual rescue. Start menu → Picketdesk - Restore desktop files (quits Picketdesk): un-hides every file Picketdesk hid, then tells you in a window what it restored and anything it could not. It is picket-app.exe --restore-icons underneath — the installer adds no command to your PATH, so typed by hand it needs the full path, "%LOCALAPPDATA%\Picketdesk\picket-app.exe" --restore-icons for the default install folder, and it answers in the receipt and picket.log rather than in the console. The uninstaller runs it too, and listens to the answer: if a file is still hidden it warns you and keeps Picketdesk's records, even when “Delete the application data” was ticked. If Picketdesk is still running, it is first asked to quit (the same full restore as tray → Quit) and the rescue waits up to 15 seconds for it to close completely; one that is still closing by then gets up to 30 seconds more and is never stopped in the middle of its last restore and save — so the files stay restored instead of being re-hidden a moment later by the live instance. That quit usually puts every file back itself: the rescue's window then says so and points you to the receipt the quit wrote, “Picketdesk restored your files.txt”. A Picketdesk that has stopped responding is closed instead; if even that fails, nothing is restored under it, and the uninstaller asks you to end picket-app.exe in Task Manager and retry, or to cancel before anything is removed.

Additional guarantees:

Restarting Explorer is not a fix The hidden attributes live on disk, so restarting Explorer only re-reads what is already there — it can never bring hidden files back. If icons ever stay hidden after a hard kill: Start menu → Picketdesk - Restore desktop files (quits Picketdesk).

Pickets and their files not showing? Two steps

Very rarely, a Picketdesk session can get stuck — no pickets on screen, and the files inside them not visible either. It looks dramatic, but nothing has happened to your files: they are exactly where they were, briefly marked hidden, and Picketdesk keeps a precise list of every one. Bringing them back takes seconds:

  1. Close Picketdesk. Right-click the tray icon and choose Quit Picketdesk — quitting is itself the full restore: every hidden file is un-hidden on the way out. If the tray icon isn't responding, open Task Manager and end Picketdesk; that is the case the watchdog covers — it runs as a separate process, notices the moment the app is gone and shows every file again, usually within a couple of seconds. If anything is still hidden after that, start Picketdesk again: the launch re-checks every hidden file, and tray → Quit Picketdesk then restores them.
  2. Still missing something? Start menu → Picketdesk - Restore desktop files (quits Picketdesk) — it un-hides everything on Picketdesk's list and shows you what it restored. Belt and braces. (By hand: "%LOCALAPPDATA%\Picketdesk\picket-app.exe" --restore-icons for the default install folder. If even the Start-menu entry is gone, Settings → Apps → Installed apps → Picketdesk → Uninstall runs the same restore before it removes anything.)

Then start Picketdesk again whenever you like. Your pickets, layouts and files all come back exactly as they were — recovering this way never loses a thing.

Reliability, day to day

Files & storage

Default location %APPDATA%\com.picketdesk.app\ (or the --profile / cloud-sync redirect target):

FilePurpose
workspace.json (+ .bak…, .daily, .corrupt-*) Pickets, assignments, free icons, usage, rules, settings — atomic writes, time-spaced backups, corrupt-load fallback. What belongs to this PC — where its pickets and icons sit, which files it hid, its own settings — is kept in workspace.local.json (below); the positions and settings here are only the starting point for a PC with none of its own. Keep any .corrupt-* copy: it is a layout that did not parse, and later launches try it again.
layouts\ / snapshots\Pages / time-machine states.
picket.log (+ .old)Rolling diagnostics (tray → Export logs…, which takes both). In the default dir only — never in a synced folder, so each PC keeps its own. Every line names the process that wrote it ([pid app], [pid watchdog], …). These processes coordinate rotation and writes through an empty picket.log.lock sidecar; a process crash releases its lock automatically.
redirect.txt Cloud-sync pointer (in the default dir only). Followed only when it names a local drive path, so a planted marker cannot redirect your whole configuration to a network share. If the folder it names is missing at launch (drive not mounted, cloud folder moved), Picketdesk waits a few seconds, then starts empty and read-only with a warning box — it never loads an older copy from the default dir in its place.
ledger.local.json Left by earlier versions, which kept the record of hidden files here. It has moved to %LOCALAPPDATA% (below); this copy is still read for as long as it exists, and only ever gets smaller.
backups\ Quit's backups, picket-backup-YYYYMMDD-HHMMSS.json (the time in UTC): the newest 10 are kept and older ones removed. In the default dir only — never synced, and never moved by Move configuration to another folder… — so one PC's Quits never touch another PC's copies. Settings → Quit backups → Open backups folder opens it.
import-backups\ / last-import-result.json Before every Import…, a complete copy of the layout and pages it replaces (picket-before-import-<time>.json); the newest 10 are kept, and each import deletes the oldest beyond that; and the latest import's result. Beside workspace.json, so they follow Move configuration to another folder…. Settings → Recent import and recovery copies lists them, and Open recovery folder opens the folder.

The rebuildable caches live apart, in %LOCALAPPDATA%\com.picketdesk.app\, and never follow the redirect: index.sqlite (the search index and its WAL), ocr-cache.json (the image-text transcript), file-identities.json (the Windows file identity of each desktop item Picketdesk keeps records for — what proves that a file renamed in letter case only while Picketdesk was stopped is the same file, not a different one that took the name) and icon-cache\ (extracted icons and thumbnails, kept under 512 MB by removing the least recently used first). An index.sqlite that is no longer a database is set aside as index.sqlite.corrupt-<time> — kept, not deleted — and a fresh index is built in its place. They describe this PC's desktop and hold nothing you could lose, so a roaming profile never has to copy them at sign-in and a synced folder never hands one database to two PCs. Existing copies move across on the first launch that does this; --profile still keeps everything in the one folder it names.

The same folder holds the records that belong to this PC and nobody else: workspace.local.json, this PC's own part of the layout — where each picket and loose icon sits on this PC's screens, the record of which files this PC tucked into a picket (what Quit, the watchdog and --restore-icons read to give those files back), and this PC's own settings: Start with Windows, hotkeys, folders to index, virtual desktop pages and docking profiles (with the profiles themselves, in docking\); ledger.local.json, a second copy of that record; and page-approvals.json / instruction-approvals.json, what this PC has approved a page, a zone or a folder to do; and crash-reports\, the crash reports this PC kept (the newest 20, for at most 90 days) with your choice about sending them — Settings → Crash reports; nothing in it is sent without that choice. Not %APPDATA%: on a company network with roaming profiles or folder redirection that folder follows the person to every PC they sign in to, and a record there would be the person's, not the PC's. The first launch of this version moves the approvals across, and reads a workspace.json from an earlier version whole and splits it at the first save (a crash in between loses nothing); deleting the configuration folder for a fresh start does not delete the record of hidden files with it.

Troubleshooting

SymptomDo this
Pickets and their files not showing The two steps above: close Picketdesk (the watchdog restores everything in seconds), then Start menu → Picketdesk - Restore desktop files (quits Picketdesk) if anything is still shy.
Desktop icons missing after a crash / forced shutdown Start menu → Picketdesk - Restore desktop files (quits Picketdesk), or use tray → Restore hidden desktop files… after the next launch. (Normally the watchdog has already done it for you.)
Files look missing on my other PC (synced Desktop) Fix it on the PC that runs Picketdesk, not the other one: take the items out of their picket, or quit Picketdesk, or run Start menu → Picketdesk - Restore desktop files (quits Picketdesk) there. Un-hiding them on the other PC (attrib -h -s) does not stick — while a picket still holds the claim, Picketdesk re-hides anything that was un-hidden from outside. If your Desktop is cloud-synced, Picketdesk says so on its Settings → Compatibility card at startup.
Every file in your pickets also shows on the desktop File Explorer is set to show protected operating system files, which shows the files Picketdesk hid too. Picketdesk never changes that setting for you: in File Explorer open Options → View and tick Hide protected operating system files (Recommended). Settings → Compatibility says so when this is the cause. If only some files show twice, Settings → Safety lists the ones that could not be hidden and why.
A box says Picketdesk cannot find the WebView2 Runtime, or could not open any picket window Your files were left on (or put back on) the desktop. When the runtime is missing, the box offers to open Microsoft's WebView2 page: install the Microsoft Edge WebView2 Runtime from there (the “Evergreen Bootstrapper”). When it is damaged, repair it under Windows Settings → Apps. Then start Picketdesk again. Setup checks for the runtime too, before it installs, stops or removes anything — an upgrade included — and ends with that same offer; uninstalling still works without it.
One tile, or every file of one type, shows no icon after Picketdesk closed on its own twice Picketdesk closed while drawing that file's icon on two launches in a row, the second time while drawing it on its own — usually a faulty shell extension for that file type — so it now skips that icon instead of closing at every start. When the icon is the one every file of that type shares, every such file goes without it, and editing a file does not bring it back. Icons that were only being drawn at the same moment are not skipped. picket.log names the file. Update or remove the extension, then tray → Refresh icons to try the icon again.
Something misbehaves and you want Picketdesk inert Start with picket-app --safe — icons untouched, no desktop mouse hook.
Anything else odd Tray → Export logs… and attach the zip to an e-mail to support@picketdesk.com — it holds picket.log plus your workspace and machine facts.

Known limitations