Click Play,get a grey flash,land back on the Steam library.No error,no crash reporter.Annoying-but launch crashes are usually one of six things,and they're fixable if you change one setting at a time and relaunch between each.
1.Your GPU driver(the developer's own#1 answer)
Aarimous said it plainly in his official sticky:updating graphics drivers fixed the majority of launch-crash reports his team received.The crash happens in the few milliseconds where the engine asks Windows for a swap chain-an older or half-applied driver says no,and the process dies before frame one.
Grab the driver from NVIDIA/AMD/Intel directly,pick Clean Install(or AMD's Factory Reset),and actually restart.Device Manager saying"best driver already installed"proves nothing-it checks a lazier database.
Reverse case matters too:if it started dying right after an update,roll the driver back.
2.The DirectX 11/12 coin-flip
On first boot the game asks you to pick a renderer and writes that choice to a config.If that prompt got eaten-by a fast double-click,a controller,or the Steam overlay-the engine boots,finds no directive,and quits.Players have confirmed the loop only broke once the flag was forced manually.
Right-click→Properties→General→Launch Options:
-d3d11
Minimum spec is DirectX 11,full stop(GTX 750 Ti/R7 360).On a card that merely tolerates DX12,forcing-d3d11 isn't a workaround-it's the correct setting.
3.Windows Security quietly ate a file
Now the most common false-positive on Steam.Defender's behavioural scanner sees a small unsigned.exe chewing through memory like a woodchipper does,and files it away.Next launch:"Failed to launch game process."
Windows Security→Virus&threat protection→Protection History.Restore anything timestamped with your crash,then add the whole install folder as an exclusion(Steam\steamapps\common\Infected Wood Shredder).Official-launcher games only,obviously.
4.Missing runtimes(the silent.dll death)
The bundled_CommonRedist installer often fails behind Steam's UI,so MSVCP140.dll never lands and the game exits without a word.
Install or repair:
•DirectX End-User Runtime(June 2010)
•VC++2015–2022,both x86 and x64-the x86 half is the one people skip and the one the game wants
•VC++2010+2012(x86)
Then run whatever sits in the game folder's_CommonRedist/redist/Installers.Those are the exact versions the dev shipped.
5.Overlays fighting over the same window
Steam,Discord,NVIDIA/AMD overlay,and Xbox Game Bar all want to inject during window creation.Two at once=the window never finishes initialising=fatal.
Disable them one at a time,testing between each:Steam overlay(per-game is enough),Discord Game Overlay,Xbox Game Bar,RTSS/Afterburner,RGB suites.
Aarimous's second-line suggestion was Compatibility Mode-same idea,different mechanism.Try Run as administrator,Windows 8 mode,and Disable fullscreen optimizations.
6.A poisoned config or shader cache
The one that makes people reinstall twice and change nothing.Verify integrity won't touch it-Steam only validates files inside the install folder,while your bad renderer flag and corrupted shaders live in%LOCALAPPDATA%,%APPDATA%,and Documents\My Games.
Press Win+R,visit each,rename the game's folder(don't delete),and clear Steam\steamapps\shadercache\<appid>.Relaunch-the game rebuilds from defaults and re-asks the DX11/DX12 question.Answer it deliberately this time.
Quick check:are you actually under spec?
Minimums are modest but specific-Win10 64-bit,8 GB RAM,GTX 750 Ti/R7 360,DX11,2 GB free.Integrated graphics with 8 GB shared memory can pass the store page and still fall over allocating its first texture array.
Fast triage:unplug the second monitor,set the primary to native res in Windows first,add-windowed.Boots now?Your problem was a display handshake,not the game.
The order that fixes most installs:driver clean-install→-d3d11→Protection History→runtimes→overlays→nuke LocalAppData.About ten minutes,and you'll know exactly which step was yours.🔧🪵
Why Does Infected Wood Shredder Keep Crashing On Startup?
Nov 21, 2026
Leave a message






