ReStory Bugs & Fixes: What Patch v1.0.010r Fixed, Paint Not Working, 0x11C7 & Stuck Parts

Quick Answer: Check your version number before anything else — patch 1.0.011r (August 19) broke soldering, and the hotfix for it is a separate download. If cleaned parts show grey solder lines you cannot work on, you want 1.0.011.f1r; until you have it, drop the part on the desk and pick it back up. Three patches before that cleared the launch-week blockers, the long save freeze, and the paint-palette bug. Of what none of them touched: if paint refuses to go onto a device, you are probably missing the paint tab in the Home Depot app or the canned air, not hitting a bug. If the game won't start on Windows 11, it is almost certainly error 0x11C7 from Smart App Control. If your PC runs hot, cap your frame rate. And parts still fall under the cleaning machines and behind the lamp, so add them one at a time and never end the day on top of a missing piece.

Version note: Current for patch 1.0.011r (August 19, 2026) and the 1.0.011.f1r hotfix the developers announced in the forums the same day, with player reports checked through August 20. The hotfix has no store announcement of its own — the version number comes from developer replies in the soldering thread, linked below. Otherwise sourced from the developers' patch announcements, their August 7 known-issues list, their forum replies, and player reports before and after each patch, all linked inline. Single reports are labelled as such.

A crash or a hung save costs you the day's queue, which is why the save freeze below is worth fixing before it bites. (Screenshot: Mandragora / tinyBuild)

Soldering Broke in Patch 1.0.011r — and the Hotfix Is Separate

This is the newest problem on the page and the one most likely to be yours right now. After patch 1.0.011r on August 19, a cleaned part can come out with its solder lines greyed out and refuse to accept the iron.

The developers found it the same day. Eugene Kisterev replied in the soldering thread — "We found a bug in the latest patch and working on a hotfix" — and posted again a short time later: "Hi we released a hotfix. Could you try if it's working? Version 1.0.011.f1r." Check your version number. If Steam has not pulled the hotfix yet, restart the client rather than assuming the bug is unfixable.

A developer-side reply in a second thread gives the exact recipe, which is worth knowing because it tells you what to avoid until you have updated:

1. Clean the part, but do not solder it
2. Put it into your inventory and take it back out
3. The soldering breaks — no blue lines

They add that they are not certain this is the only route in, and ask players who hit it another way to describe what they did.

The workaround, confirmed by several players independently: put the part down on the desk or workbench, then pick it back up. One player called this the thing that rescued parts he thought were permanently ruined. A second route is to run the part through the ultrasonic again and solder immediately when it comes out. A third player reports it can take a couple of tries. The rule underneath all three is the same: do not let a cleaned-but-unsoldered part sit in your inventory — solder it while it is still on the bench.

One player reports the workaround did not help after the update. Treat that as the reason to get onto 1.0.011.f1r rather than relying on the desk trick.

Cleanliness Stuck at 0% on a Motherboard

Related but not identical, and not confirmed fixed: a motherboard that demands cleaning and soldering while the cleanliness meter refuses to move off 0%, with the brush, the canned air and the sonic bath all doing nothing. Three players report it on different devices — an xi-box, and a PlayStation board twice. One describes it as sometimes jumping straight to soldering and sometimes not.

There is no repair for the affected part. The working answer players have settled on is the blunt one: abandon that specific part and buy a replacement, rather than spending more days trying to clean it. If it is a story device rather than a shop job, roll back a save instead — see the save rollback section below.

What Patch 1.0.011r Fixed (August 19)

The third patch is mostly achievement and cleaning repairs, plus one quality-of-life addition that changes how you handle loose parts:

The patch also adds competition-complete music and a shredder sound.

What Patch v1.0.010r Fixed (August 13)

The second patch is three lines long, and the first one is the launch week's loudest complaint:

The same announcement puts the game at 300,000 copies in its first week and adds a soundtrack and an expanded 45-page artbook as separate paid items. The developers say a free content update with a new gadget is already in progress.

What Patch v1.0.009r Fixed (August 11)

The patch announcement clears the entire August 7 known-issues list and adds three items that were never on it. If your problem is one of these, update the game — that is the whole fix:

The developers say the next update is already in progress. Everything after this point is not covered by the patch — either the developers have not named it, or players are still reporting it.

One thing the patch does not do: take back achievements that fired early. "How Did I Do It" still shows a 100.0% global unlock rate, because the fix stops future false unlocks rather than revoking past ones. If it popped on your account before August 11, it stays popped.

Game Won't Start: Error 0x11C7 (Windows 11)

Symptom: the game refuses to open on first launch and throws error 0x11C7.

Cause and fix: Windows 11's Smart App Control is blocking it. The player who reported it found that disabling the feature let the game open, and a developer (posting as k1mon) replied that the report was "very useful information." At least one other player confirmed the same error.

Read this before you flip it. Smart App Control lives in Windows Security under App & browser control, and Microsoft's own FAQ states that once it is off, turning it back on requires resetting or reinstalling Windows — it is not a toggle you can undo on an afternoon. Newer Windows builds have started allowing re-enablement from the Security app, so check what your own machine offers before you decide. If that trade is too steep, report the error in the developers' bug thread and wait for a patch instead.

Crash on Startup: D3D12Core.dll Access Violation

A different launch crash from 0x11C7, with a different cause. The crash report names Unity 6000.3.10f1, exception 0xC0000005 Access Violation in D3D12Core.dll, thrown during D3D12CreateDevice while Unity initialises DirectX 12.

The player who posted it was on Windows 10 build 18362 (version 1903) with an RTX 3060 Ti, and upgrading to Windows 11 fixed it. Single report, but the diagnosis is specific and checkable: 1903 shipped in 2019 and its DirectX 12 runtime predates what current Unity builds expect.

Before you reinstall an operating system over a game, check your Windows version with winver and update Windows normally first — 1903 is many feature updates behind, and the fix here may be the update rather than the jump to 11. If you are on a current Windows 10 build and hitting this same exception, that is new information and worth posting.

Save / End-of-Day Freeze (Patched August 13 — Verify)

Symptom: ending the day or saving freezes the game — a minute for some players, two to four minutes for others, with Windows marking it Not Responding. Players reported it in both the demo and the full release, on hardware well above the recommended specs, and v1.0.009r did not fix it.

v1.0.010r names it: "long save issue and possibly crash on saving." Treat that wording as the developers' own uncertainty rather than a guarantee — they fixed the slow save and think it may also have been the source of the save-time crashes.

Two days on, the silence is starting to mean something. All three of the big freeze threads have stayed quiet since the patch: no new reports, and no confirmations either. On a board this active — where the paint and competition threads picked up new reports over the same two days — a freeze that was still happening at the old rate would have produced them. That is absence of evidence rather than a fix anyone has verified, so update, then test on a day you can afford to lose, and keep the no-clicking rule below until someone confirms the crash is gone too.

The one rule that costs you nothing: do not click anything while it is frozen. Two players independently report that clicking during the freeze crashes the game outright, turning a wait into lost progress. Start the save, take your hands off the mouse, and wait it out.

Workaround: run Steam as administrator. One player in the bug thread tested it in both directions — "running Steam normally brings the issue back. As soon as I run Steam as an administrator again, the problem is resolved." That two-way test is stronger evidence than the usual "this worked for me."

The developers add two checks worth doing if admin rights alone don't help:

• Confirm your antivirus or Windows Security isn't blocking creation of the save file.
• Check that the files in your save folder aren't marked read-only.

Developer Eugene Kisterev is on it and has asked for two specific data points. In the long-running thread — ten-plus reporters and still collecting after the patch — he wrote: "We're looking into it. Can't confirm yet on what's the actual problem but we'll test it on more machines and fix in next hotfixes. Could you also write if you have SSD or HDD and confirm you have enough space on it?"

The answers ruled his hypothesis out before the fix shipped. Every reporter who replied is on an SSD with plenty of free space — 50 GB, 150 GB, "more than half my storage." The affected machines span AMD and Intel CPUs, Radeon and NVIDIA GPUs, and range from a Ryzen 9 7900X with 64 GB of RAM to an i9-9900KF. There is no shared hardware factor visible from outside. Two smaller clues that are worth adding to the thread if they match you: one player had the same freeze in the demo, and another says it started at day 8 with saves getting progressively longer, which would point at save-file growth rather than configuration.

A separate, quieter report: the manual Save Game menu option gives no confirmation feedback, and the game still warns about unsaved progress on exit afterwards, so players cannot tell whether it worked. Two reports. Unrelated to the freeze, but it means "did my save go through" is currently unanswerable from inside the game — the save folder timestamps are the only way to check.

Paint That Won't Go On

Patch 1.0.011r fixed the painting palettes UI and the Brick Game quest item, which between them cover the two hardest variants below. Update before working through any of this — the sections are kept because the causes that were never bugs still apply, and because nobody has posted a post-patch confirmation on the Brick Game yet.

The busiest live problem on the board, and most of it is not a bug. Reports run across four languages and split into three distinct causes, so work through them in this order before concluding your save is broken.

1. The colour is not in your dropdown — you have not bought it. Paints are sold on your in-game PC, in the Home Depot app under a separate tab with a palette icon, well below the tools. Two threads end the same way: a player stuck on the "paint this in retro Atari colour" objective had tried every colour they owned, and the answer was that the required one was for sale the whole time. The second player in that thread replied "I did not see the paint tab the whole time." Once the paint arrives, drop it onto your airbrush and it appears in the spray dropdown.

2. You own the paint and nothing happens — check for canned air. Spraying requires it, and running out produces the same do-nothing result as not owning the colour.

3. Both are in place and it still refuses. One player worked this one to a conclusion over several days in their thread: reloading the game repeatedly eventually made the colour apply, and their read afterwards was that the failure only happens the first time you use each new type of paint. That is one player's pattern from their own save, not a confirmed mechanic, but it costs nothing to test — quit to desktop, relaunch, and try that colour once more before you rearrange your day around it.

The hard variant is clustering on one device, and restarting does not clear it. Three players now describe the same wall on the story Brick Game — the little handheld console, the Tetris one — with the paints bought, the spray gun bought, and the left mouse button producing nothing at all: no colour, no progress on the bar. One reinstalled the game and it changed nothing; one watched streamers do the same step without trouble; one had painted normally on their own PC, moved the save to a second machine through Steam Cloud, and now gets the airbrush achievement firing while the paint never applies. They are posting in three different languages, which is why this looks smaller on the board than it is.

So the reload trick above is not universal. If you are stuck on the Brick Game specifically and you have already confirmed the paint and the canned air, reloading is worth one try and no more. There is no known fix past that point, and reinstalling is the step that has already failed for someone. If you are about to move a save between machines mid-story, keep the original PC's save file rather than relying on Cloud alone.

The developers are on the thread, and their working theory is your hardware. Eugene Kisterev asked the latest reporter for their specs, with the reason attached: "Usually that happens on really old configurations." That is a lead rather than an answer — nobody has posted a spec comparison across the reporters — but it is the first time the paint failure has been attributed to anything. If you are reporting this, lead with your specs. A second player in that thread confirmed the same symptom with no fix, and a third linked three further threads on the same problem, which is a fair measure of how spread out this is.

Wall Paint Is a Separate Problem

Distinct from device paint, and now three reports rather than one. The symptom is that the colour reverts the moment you confirm it:

• One player bought paint three times trying to make their walls pink; each time, pressing apply turned it back to grey. They are on Steam Deck and suspect that is the variable.
• A second player, on the same thread, has pink walls that stayed pink — which is what makes the Deck theory worth testing rather than dismissing.
• A third cannot apply wall paint at all: "Every time I try to apply the paint it just goes back into the box on the windowsill and now i can't do anything else" — that last clause is the concerning part, because it describes being stuck rather than just failing.

No developer reply on the wall variant, and no workaround anyone has confirmed. Do not spend money on more paint expecting the next tin to behave differently; three purchases produced three identical failures for the first reporter.

Separate reports in the same family, each currently single-source: the game crashing outright on entering the paint screen; and paint being sold with no colour names shown, which is what turns a specific paint request into trial and error.

Crashes

Several distinct crash reports appeared on day one, each currently from a single player, with no patch yet:

• Crashing when changing window focus — alt-tabbing out of the game. If this is your pattern, play fullscreen and avoid switching away mid-repair.
• Crashing when the game closes — annoying rather than costly, since the day's save has already happened.
• Crashing on save — the one that costs you progress, and the reason the save-freeze workaround above is worth doing pre-emptively.
• Repeated hard crashes on an RTX 3060 Ti, from a reviewer who reports the game crashing "HARD" within short sessions while heavier titles run fine.

Two of them have now converged on specific screens. A new thread reports crashing repeatedly on the paint step — the poster says they now avoid accepting jobs that need painting — and the first reply is someone crashing on deep cleaning. Those are the same two screens the 91°C overheating report names as its triggers, which makes the overlap below worth taking seriously rather than treating as coincidence.

The practical read: the overheating reports and the crash reports look like one problem seen from two directions, and the one player who capped their frame rate reported the crashes stopping. Try the FPS cap before you conclude your install is broken — especially if your crashes cluster on painting, cleaning or the in-game browser.

Overheating and Heavy Hardware Load

Symptom: unusually high CPU and GPU temperatures for a stylised 3D repair game — several players say it runs hotter than far more demanding titles.

Reports in the thread: an RTX 5070 with a Ryzen 7700X sitting at 65-70°C in gameplay against 48-50°C in menus; another player at 1080p with a 60 FPS cap still reporting CPU heat with current drivers; the original poster overheating even on lowest settings.

A second, worse case landed after the patch: an i9-13900HX laptop with an RTX 4070 hitting 91°C, from a player who runs Cyberpunk and Crimson Desert below 80°C on the same machine. Their trigger was specific — cleaning components — and later selling items and using the in-game browser. That pattern points at UI-heavy screens rather than the 3D scene, which is the opposite of what you would expect.

What to do, in order of what has actually worked for someone:

1. Cap your frame rate. The developers name this directly alongside verifying files and updating GPU drivers. The original reporter capped to 30 FPS and said "It hasn't crashed since." The 91°C laptop reporter capped to 30 FPS and dropped to 65°C.
2. Try VSync with an uncapped frame rate instead. The same player got below 70°C this way and kept a playable frame rate — but temperatures still spiked to 90°C on the selling and browser screens. Better than a 30 FPS cap, not a solution.
3. Watch it with Steam's in-game performance monitor, which the developers also suggest, so you know whether the change did anything.
4. On a laptop, try the Power Saver power plan. One player suggests it as a stopgap; nobody has confirmed it.
5. Expect a partial result. One player notes the 30 FPS cap costs enjoyment and their CPU still reached around 60°C — this is mitigation, not a fix, and the load pattern looks like an optimisation issue rather than anything on your end.

The patches have not settled this, and one report points the wrong way. One player said temperatures improved after v1.0.009r. A different player on a Ryzen 7 7800X3D opened a thread the day after saying the opposite: their CPU now runs at 70°C where it previously peaked at 50°C, with idle at 45°C and fans audibly ramping, and they attribute the change to the patch. Two players, two opposite directions, no developer comment — so check your own temperatures after updating rather than assuming either result. A third thread reports unusually high GPU utilisation on an RTX 4070 Ti, which fits the same optimisation picture.

Firmware Updates: Fixed, But Not How You'd Expect

The symptom, now historic: an order required a firmware update, and the game answered "not possible for this device" — even with the upgraded UNLOCK-TOOLKIT. The order could not be cleared, and because online orders carry a delivery deadline with no cancel option, two players watched jobs they physically could not finish run overdue.

v1.0.009r fixed it, and the two devices were fixed differently. Players who updated report both halves in the MyPod thread:

• The MyPod firmware update now works. One player confirms two MyPod firmware jobs completing normally after the patch.
• Guitars had the firmware requirement removed entirely. The same player found all three guitars waiting in the back no longer asking for firmware at all; a second player states plainly that the task was "removed from guitars and some other item completely."

If you parked a save waiting for this, load it and just deliver the order. A player who had shelved the game over a stuck Guitar Legend job came back after the patch, found the update still unavailable, and assumed he had to start over. He didn't: two other players pointed out the requirement is gone, and he delivered the guitar as-is. The firmware step never becoming available on that order is the fix working, not the bug persisting.

The developer has now said it outright. A player posted on August 16 that the patch notes claimed a fix while the guitar firmware still refused to update, and Eugene Kisterev answered directly: "You don't need to update firmware on guitars now. We removed this task from todo lists. Just finish the order." The reporter accepted it and closed the thread. A second player in the same thread reports the patch cleared two devices that had been backed up behind the bug.

That is the whole answer, and the confusion is understandable — nothing on screen tells you a requirement was deleted rather than satisfied. If a guitar order shows no firmware step, hand it in.

Check your achievement list after loading a parked save, too. One player had "obtain all upgrade certificates" pop the moment they logged in post-patch — an achievement they had already qualified for while the bug was blocking them.

The wider lesson stands for the next bug like this: while a blocker is live, decline the affected job at the point of accepting it rather than parking it, because online orders run on a deadline the game gives you no way to cancel.

Parts That Vanish Under the Cleaning Machines

Symptom: the order refuses to close with "don't forget to remove unneeded part from the desk", but the part is nowhere on the workbench. It has fallen underneath the ultrasonic bath or the UV cleaner, and the machine's idle position covers it. The main thread is at nineteen posts and still collecting reports.

Patch v1.0.009r lists "some gadgets stuck in sonic bath" as fixed, which is narrower than what players describe here. The official wording covers a whole device failing to leave the cleaner. Players in this thread are losing individual small parts underneath the machine, and the developers have never named that. Keep the prevention rule below until post-patch reports say otherwise.

Two players independently worked out the same cause: you dropped the part while the machine was still moving. The bath slides back into its tucked-away position on a timer; a small item released before it settles falls through to the desk instead of into the tray, and the machine then parks on top of it. One player adds a second trigger — something large already occupying the bath, with a small part dropped on top of it. A third report from the UV cleaner describes the identical sequence.

The rule that prevents it: wait until the machine has fully stopped moving before you release anything into it, and put parts in one at a time. That costs a second per part and is the only reliable protection while the patch is out.

If a part is already gone:

1. Locate it first. Step away from the workbench but leave the job on it, open the notebook, and hover the entry for the dirty part — the game highlights where it thinks the piece is. If the highlight sits under a machine, it is this bug and not a part you misplaced.
2. Spam-click the cleaner. Open and close it, run it forward and back, repeatedly. One player recovered an Atari base this way; another suggests dropping something from the spare-parts pile in to knock it loose.
3. Swap the order off the mat and back. Move a different order onto the mat so the stuck device gets boxed, then swap them back. This works less often than the click method — one player reported the part simply not reappearing.

This does lock story progression. Two players hit it on story jobs and could not continue, so the early advice that it only affects online orders is wrong. There is still no unstuck command.

A second variant is now confirmed by two players: payment money left permanently on the desk. The game keeps asking you to clear the desk and will not let you touch the cash — one player had it from a previous order, another from money found inside a device. Same family, same absence of a fix.

Parts That Vanish From the Desk Entirely

A separate pattern from the one above, and it now has five reports in its own thread. The part disappears the moment you drop it — not under a machine, just gone — while the order still insists something is left on the table.

Restart the game before you assume it is lost. One player found the missing part sitting in their parts box after quitting and relaunching. That is the only recovery anyone has reported, and it does not always work: another player's part was neither on the table nor in the box, with the game still claiming it was on the desk.

Competitions used to be the case with no way out — v1.0.009r changed that. The parts box being unavailable during a competition was on the developers' known-issues list and is fixed, so the restart recovery now works mid-competition too. That matters because the game still offers no way to abandon a competition in progress; before the patch, two players were left holding competition boxes they could neither finish nor cancel.

It has not made competitions safe. A report posted the same day as the patch describes a competition Xbox losing its back panel off the table, surviving both a failed snap-back and a remove-and-replace, and then a second panel snapping into the assorted-parts box and vanishing. That is a single report and it isn't clear whether the player was on the new build, so treat it as a reason to keep adding parts one at a time in competitions rather than as a known post-patch bug.

One report names a way to soft-lock an order permanently: cannibalising an order's base part for a different device. A player disassembled a Nony PMP that came in as an order, put the parts in the box, then used that order's Frame to repair a second PMP they had bought. Buying a replacement Frame creates a new object the game will not assign to the existing order, so the order can never close. That is one player's account of their own save, but the prevention rule costs nothing: do not take parts out of an order's device to fix something else.

Before you conclude an online order is unfixable, search the desk itself. A player who had cannibalised an online order's device found the job stuck at "in progress" with no box anywhere on the table. Another player's rule — the order's box is open somewhere on your desk even when it looks empty — found it: the device was sitting behind the lamp, with no box around it. Devices handed to you outside the normal order queue don't always announce themselves.

Loose cash found inside a device sticks to the mat, and there is no way to hand it back. Three players report the same thing: a repair turns up money tucked in the back of a phone, they put it on the work mat, and it can never be moved again. Nothing breaks — the mat is just permanently occupied. The community read is that it belongs to the device's owner and there is no mechanism to return it yet. Nobody has reported it blocking a repair, so it is a cosmetic annoyance rather than a reason to roll back. Leave found cash where you found it until this gets an answer.

The lamp is now its own trap, with two reports. Both players dropped a story item near the desk lamp and could not pick it back up by any means; one had to roll their save back to an earlier day. The second one names the mistake that makes it permanent: they advanced to the next day hoping it would reset, and it did not. So the rule when anything lands somewhere you cannot retrieve it is the same rule as for the save freeze — stop, do not end the day. Ending the day banks the broken state into the save you are about to keep. Roll back instead; see the save-file section below.

The Atari Lynx Batteries Are Not Duplicating

Symptom: you pull a battery out of the Atari Lynx, both visible batteries disappear at once, and more keep appearing — so it looks like the game is spawning duplicates and blocking the job.

This is the device working correctly. The Lynx takes six batteries, not two. Removing the top one makes the next slide up into place, and the pair vanishing together is the game making them easier to reinsert as a set. Three players explained it in the thread and the original reporter — who had already filed it on the bug tracker as a soft-lock — withdrew it. Look at the battery compartment: it is visibly long enough for six.

Parts in the Sonic Bath Show as "Missing"

Not a bug, but it costs you money. While parts sit in the ultrasonic cleaner, the order's checklist marks them as missing, and several players have bought replacements they already owned before noticing.

The rule that avoids it: disassemble the whole device first, order every replacement part you actually need, then start the wash. Do not shop while the bath is running.

Save Files: Where They Are and How to Roll Back

The game has no save slots. It keeps the five most recent saves automatically, the highest-numbered file being the current one, and the other four exist as corruption backups. That makes a rollback possible without starting over — which matters for the sonic-bath freeze above and for the branching-ending achievements.

On Windows the folder is:

%userprofile%\AppData\LocalLow\Mandragora\Restory\SaveData

Disable Steam Cloud before you touch anything in there. A player who worked this out on the forums notes that leaving Cloud on makes Steam pull the newest file back down the moment you launch, undoing the swap. Move the current save somewhere safe, and the game loads the next most recent one.

Recovering a Save You Thought Was Gone

There is a second folder next to SaveData, and it is the reason a wiped save is usually not a wiped save:

%userprofile%\AppData\LocalLow\Mandragora\Restory\BackupSaveData

A player who lost 48 hours of progress — the game was running in the background and he clicked through New Game and its confirmation prompt without seeing them — recovered a day-66 save from it after the thread had already written the run off. His procedure, verbatim in effect: open BackupSaveData, pick the most recent of the files in there (his folder held four, one dating back to the June beta), copy its contents over the ones in SaveData, and launch.

The order matters more than the steps. Do this before you play another session, because new saves overwrite the backups too. And note what did not work for him: a Windows system backup taken hours later was useless, because Steam Cloud pushes its copy over the local file on launch — the same trap as the rollback above. Turn Cloud off first.

One correction to the story people tell about this: New Game does prompt you. It shows an explicit warning that you will lose all progress. That does not help if the game is running behind a browser window and you click through both, which is exactly how this one happened.

Soldering That Won't Take

If the solder lines are grey, this is not the section you want — that is the patch 1.0.011r regression at the top of the page. This one is about lines that are visible but will not fill.

Reported as a bug on day one, but it reads as an input-timing problem: click the soldering iron, move the cursor onto the line, hold the mouse button down, drag along the line, and release at the end. Players who release mid-line get no result and read it as a failed repair.

A cleaned part that still needs soldering does not keep its cleaned status when it goes into the inventory — it comes back out dirty and has to be cleaned again. Four players describe it in the same thread, and the patch did not change it. Solder before you store: the same rule that avoids the grey-lines bug also avoids re-cleaning the part.

A Device That Stays "Unfinished" With Every Box Ticked

Reported for the Robby robot dog: the parts list shows everything cleaned and assembled, the device still counts as unfinished, and stripping it back down and rebuilding fixes it — after one to three attempts.

Check your screws before you call it a bug, because that is what a developer-side account asked first and what the reporter's own follow-up points at:

1. Look at the jar lid in the bottom right that holds your screws. Any left in it means the build is genuinely incomplete.
2. Try to put the device on the counter for pickup. If screws are missing, the game tells you so at that moment — it is the clearest signal available and most people never trigger it because they are still staring at the checklist.

The checklist is what misleads here: it tracks cleaning and assembly, and a screw that was never driven home does not show up as an unticked line. If both checks are clean and it still will not complete, that is the bug, and the developers asked for saves and logs with the report rather than a description — a screenshot of the checklist does not tell them anything they can act on.

Motion Sickness: Three Players Say No

Asked directly on the forums, three players who describe existing motion sensitivity — one with a diagnosed balance disorder, one with severe motion sickness — all report ReStory not triggering it. Their reasoning is consistent: the camera is fixed for roughly all of the game, the zoom onto the work mat is brief and player-triggered, and the only free movement is a slow lean to reach a shelf just off screen.

Two caveats. This is player experience, not an accessibility feature — the game ships no motion or camera-shake toggle. And the demo has been pulled since release, so you cannot test it yourself before buying.

Controller: What "Partial Support" Costs You

Steam lists the game as Partial Controller Support, and the store page does not say which parts are missing. Players who asked in the forums got a concrete answer from someone playing that way: the soldering minigame is awkward, small screws are hard to highlight with the left stick, and the cursor moves slowly with no sensitivity setting. The same limits apply to the touchscreen controls. Others suspect the keyboard-mashing hacking minigame is the formal reason for the "partial" label, which is untested.

If a controller is your only input device, this is a real barrier rather than an inconvenience — the player who reported it advised against buying for controller play. The repairs are cursor work, and the game gives you no way to speed the cursor up.

A gamepad can also capture input at the very first screen: PCGamingWiki documents keyboard and mouse being disabled once a controller is detected, leaving you stuck at the opening data-collection prompt with no cursor. Unplug the controller if you cannot get past it.

Smaller Reports (Single Sources, Not Yet Patterns)

• No way to return to fullscreen after choosing windowed — a settings dead end with no reported workaround.
• Wall paint bought but unusable and a bugged competition repair — each one thread, each posted on launch day. The Atari Lynx battery report that sat here has been withdrawn; see the section above.
• The airbrush palette will not scroll on Steam Deck — one player with several palettes unlocked cannot reach the ones below the fold, with no reply yet.
• Steam Deck is "Playable", not Verified. The developers stated this before launch and said Deck work continues; players are already asking for it in the forums.
• More achievements fire early than the official list names — Business Shark and the soldering achievement both have reports. See the Achievements Guide.
• A post-credits delivery box that cannot be opened or put down — three reports since the patch. See the section below, which explains what is in that box.
• Tools gone after starting endless mode — see the section below; this is not a bug.
• A soldering step that will not complete on Takumi's PlayStation — the L-shaped power-supply joint, blocking main-story progress. One report, in German, with no reply.
• The same phone arriving over and over — one player reports receiving roughly five identical handsets to repair and hack in a row.
• Purchased PSPs that will not fully open for disassembly, with no highlight appearing on the screws. One report.

The Story Stops After the Akiba Contest

Two reports, and worth separating from the licence-order stall it superficially resembles. The symptom: you finish the Akiba contest and the story simply stops — "no one is showing up." The second player had come to the forum the day before with the same question.

One caution about what you will read in that thread. The reply the reporter got was "apparently it is a bug the devs are working to fix" — but that is another player relaying it, not a developer post. We checked the game's announcements and found nothing about an Akiba contest blocker in any patch note or developer reply, including in v1.0.010r. It may well be a real bug and the developers may well be on it, but as of now that is an expectation someone repeated, not a fix on the way.

Practical position: two reports is enough to know you are not alone and not enough to know the cause. If you keep saves, roll back to before the contest rather than waiting. And note that this is a different stall from buying licences too fast, which is now at seven reports with its own named cause.

After the Credits: Your Tools Are in the Delivery Box

Symptom: you finish the story, start endless mode, and every upgraded tool is gone from the workbench and absent from the shop. It reads like the ending wiped your progress.

It did not. Two players answered this independently in the thread: depending on which ending you got, the main characters come by the shop and hand your tools back as gifts a few minutes of game time in, and all of it arrives in the delivery box.

The rule that saves you the panic — and possibly the box: after the credits, empty the delivery box before you accept a single order. One of the two reporters is explicit that jobs you take will stack on top of the tools sitting in there. That also gives the best available reading of the separate three-report problem where the post-credits counter box cannot be opened, put down or emptied, and blocks later courier deliveries: it is the same box, already holding your returned tools. Nobody has confirmed that link with a developer and there is still no workaround for the stuck version, so treat "empty it first" as cheap insurance rather than a proven fix.

Competition Repairs That Show a Box Instead of the Device

Symptom: a competition job loads with the device's outline replaced by a plain box, and every part has to be placed into it in an exact arrangement that mostly refuses to register.

Four reports now, up from two, and they name specific devices: the camera, the Polaroid, the Xbox and the Walkman. One player spent seven hours on a camera and left a negative review over it. Another says it is happening on "pretty much every device" for them, with only the simple repairs completable by luck.

The workaround comes from the one player who got past it: finish the bugged job if you possibly can, then buy another copy of the same device — the replacement did not bug out for them. That is one person's experience, not a rule, but it is cheaper than restarting a competition you cannot abandon.

Your Key Was Revoked (Third-Party Sellers)

Not a game bug, but it is the busiest thread on the board and the answer is not obvious. More than a dozen players who bought ReStory from Green Man Gaming or Kinguin found the key revoked from their Steam library after activation, in several cases after being charged. One player's read is that the reseller's regional pricing was wrong and the listing was later corrected to match Steam's price in that region.

Take it to the seller, not to Mandragora or tinyBuild. A Green Man Gaming moderator posted in the thread confirming they are aware of the situation and directing affected buyers to GMG customer support. Several players report tickets already open. The game's developers cannot restore a revoked third-party key.

How to Report Something

The developers pinned a bug reports and troubleshooting thread on launch day and accept reports through the Steam forum, their Discord's bug-reports channel, or their support site. What they ask for:

• A short description of the last few steps before the problem happened.
• Screenshots or video.
• A compressed copy of your ReStory game folder — the thread lists the exact paths for Windows, Mac and Linux/Steam Deck.

For performance problems specifically, they ask you to first update your OS and GPU drivers, make sure the game uses your dedicated GPU rather than integrated graphics, verify file integrity or reinstall, and temporarily disable overlays such as the NVIDIA app and Discord.