Missing items & save recovery
Use this page before reopening the game or changing a save. It separates the July 25 server incident—where every item disappeared or the account rolled back—from an ordinary local crash, PC move, Steam Cloud mismatch, or damaged backup. Official patch 1.01.05 later added automatic backups every 24 hours with up to 30 days of retention, but that newer safety net does not make the two recovery paths interchangeable.
Read the failure first, then choose one next test.
Close Task Bar Hero now. Do not relaunch or play. Compress the entire %USERPROFILE%\AppData\LocalLow\TesseractStudio\TaskBarHero folder in its current state and attach it to the official Item Disappearance form. If this incident description does not match, use ordinary Path B below.
This fan-made guide does not upload, inspect, or repair saves. Use the linked developer notice, form, FAQ, and support address for recovery.
Match the symptom, then take only the next action shown. The newest official incident instruction overrides the older relaunch-first preparation sequence for players whose entire inventory vanished or whose data rolled back.
This matches the developer's server-incident recovery case, not an ordinary local-save repair.
Next test: Keep the game closed, do not play again, compress the entire TaskBarHero folder as it exists now, and attach that archive to the official Item Disappearance support form.
An isolated Market, Mailbox, Cube, crafting, or server transaction is not the same symptom as a full inventory wipe.
Next test: Stop risky transactions, preserve a copy of the current folder, note the time and exact error, and use the official bug/support channel. Do not roll back the whole save merely to chase one missing item.
Installed game files may be missing or corrupted.
Next test: With the game closed and the save folder backed up, use Steam Library > TBH: Task Bar Hero > Properties > Installed Files > Verify integrity of game files before renaming any save.
The newer save may not have synchronized, while launching either PC could upload or receive the wrong state.
Next test: Keep the game closed on both PCs. Copy the likely-good PC's whole TaskBarHero folder before allowing Steam Cloud or Task Bar Hero to touch it.
An older local or Steam Remote .es3 copy may be the last ordinary recovery option.
Next test: After ruling out the incident and copying the folder, test one local backup by modification time. If none is usable, check Steam Remote Storage; then stop and contact support if no copy works.
An automatic backup may exist within the official 24-hour and 30-day retention window, but the patch note does not publish a self-service restore location or guarantee a usable snapshot.
Next test: Keep the game closed, preserve the current local folder, record when the last good state was seen, and contact official support about the retained backup before making destructive file changes.
Path A is the July 25 mass-disappearance or rollback response. Path B is ordinary local recovery. If Path A matches, stop after submitting the official form and wait for developer instructions; do not continue into Path B.
For a July 25 all-item disappearance or rollback, do not relaunch. With the game closed, compress %USERPROFILE%\AppData\LocalLow\TesseractStudio\TaskBarHero in its current state—not just SaveFile_Live.es3.
Attach the compressed folder to the developer's form. This fan site cannot receive the archive or restore server-held items. Keep your original archive unchanged.
The official notice says recovery work is underway and a schedule will follow. Check that notice for a newer instruction before reopening.
For an ordinary launch failure, migration, Cloud mismatch, or damaged save, copy the folder outside the game directory. Then run Steam > Properties > Installed Files > Verify integrity; this repairs the installation, not the save.
Choose SaveFile_Live_1.es3 through SaveFile_Live_5.es3 or a timestamped backup by modification time. In a working copy, preserve the live file and name one copied candidate SaveFile_Live.es3.
If local backups fail, test the closest useful Steam Remote .es3 file in a copied folder. If no copy works, stop changing files and contact official support.
For ordinary problems after 1.01.05, tell support when the last good state existed. The developer says saves are backed up every 24 hours and kept for up to 30 days, but has not published a guaranteed self-service restore workflow.
Guardrails
These are stop conditions, not optional cautions. A fast experiment can overwrite the evidence or good copy needed for a later recovery.
For the July 25 incident, the newest official instruction is to close the game and refrain from launching or playing again. It overrides the older FAQ's relaunch-first preparation for this symptom.
Renaming a backup, pulling Cloud data, or deleting the live file changes evidence the developer may need. Submit the current folder first when the incident matches; ordinary tests belong in a copy.
Steam Cloud may synchronize an empty or incorrect state. Keep Task Bar Hero closed on that PC until its entire save folder has been copied somewhere safe.
Task Bar Hero Tools has no save uploader, login repair, or account access. Use only the developer's official form or support address, and never include a Steam password.
Incident source: the developer's “Response to Server Instability and Item Disappearance Issues,” checked 2026-07-27. It covers the July 25 KST incident and tells players with a full inventory disappearance or rollback not to play, to compress the entire TaskBarHero folder, and to submit the linked form.
Ordinary source: the developer-pinned “TBH Save Data Recovery Guide,” checked 2026-07-27. It provides the Windows location, backup names, file verification, multi-PC and Cloud warnings, manual restore sequence, Steam Remote fallback, and support handoff.
Backup update: official patch 1.01.05, published August 11 and checked 2026-08-17, says the save system now backs up saves every 24 hours and keeps backups for up to 30 days. The note does not identify a local filename, promise that every snapshot is restorable, or publish a self-service recovery sequence.
Priority rule: the symptom-specific incident notice overrides the older FAQ's relaunch-first preparation for matching July 25 cases. For ordinary later problems, preserve the current folder and mention the new retained-backup window when contacting support. This page is not a live server-status monitor.
Scope: this unofficial page cannot inspect, upload, merge, or repair saves, confirm server inventory, or guarantee recovery. The location is verified for Windows only; no native macOS, Linux, or Steam Deck path is claimed.
Use the incident links for a full disappearance or rollback. Use the FAQ and Steam Remote link only for ordinary local recovery after the incident has been ruled out.
FAQ
Use these answers to confirm which path applies before reopening Task Bar Hero, changing Steam Cloud, or renaming a local file.
The official Windows folder is %USERPROFILE%\AppData\LocalLow\TesseractStudio\TaskBarHero. Keep the game closed. For the July 25 incident, compress it in its current state; for ordinary recovery, work from a separate copy.
If the full inventory vanished or the account rolled back after the July 25 instability, close the game and do not relaunch. Compress the whole TaskBarHero folder and attach it to the official Item Disappearance form.
Not for a July 25 full disappearance or rollback. The developer says continued play may make recovery difficult. Keep it closed, preserve the folder, submit the form, and check the notice before resuming.
The official notice asks for the entire TaskBarHero folder, not one selected file. Compress it after closing the game and submit it only through the developer's form, not this website.
No. The incident path starts with no relaunch and an official submission. Ordinary recovery covers a local launch failure, PC migration, Cloud mismatch, or damaged backup and may use verification or restore tests.
On the ordinary path, preserve the folder, choose by modification time, and test one copied candidate as SaveFile_Live.es3. A newer empty or wrong Cloud state can overwrite another PC, so back up that PC before launching. Use Steam Remote only if local backups fail.
No. This fan site has no save uploader, Steam login, or server access. It only separates the official incident and ordinary recovery paths. Send files only through the developer's form.
Yes. Official version 1.01.05 notes say saves are backed up every 24 hours and retained for up to 30 days. The note does not publish a guaranteed self-service restore path, so preserve the local folder and contact official support with the last known-good time.