Hollow Knight Silksong Crash on Startup PC Fix (Steam/Epic)

What is the Hollow Knight Silksong Startup Crash?

Hollow Knight: Silksong, released September 4, 2025 by Team Cherry on Steam, Epic Games Store, and Xbox Game Pass for PC, suffers from a recurring launch-day crash that prevents the game from reaching the main menu. Players encounter one of several symptoms: an instant return to desktop with no error window, a Unity 6000.0.50f1_aa6e6f1b3a8c error referencing the bundled Unity runtime, a generic "Silksong has stopped working" dialog, or a black screen followed by a hang before the splash.

The most common root cause is a missing or out-of-date Microsoft Visual C++ Redistributable. Team Cherry confirmed in the September 2025 hotfix patch notes that the Unity 6 runtime requires VC++ Redistributable 2015-2022 (x64) version 14.40.33810 or newer to initialize correctly.

When does it occur?

• Immediately on launch, before the Team Cherry logo appears
• After clicking "Play" in Steam or Epic Games Launcher with a black screen flash
• After installing a fresh Windows update (KB5074109 onward) without rebooting
• When a controller (DualShock 3, Xbox 360 receiver, generic XInput pad) is plugged in
• On Windows 11 24H2 or 25H2 with the GeForce Experience or NVIDIA App overlay active
• After moving the game install folder between drives without re-verifying files

Common causes

• Missing Visual C++ Redistributable 2015-2022 x64 — Unity 6 will not start without vcruntime140_1.dll from version 14.40+
• Corrupted shader cache — old DX11 shader bundles persist after a GPU driver update and trip the Unity loader
• Outdated GPU driver — drivers older than NVIDIA 566.36 / AMD Adrenalin 25.1.1 / Intel Arc 31.0.101.5333 fail Unity 6's feature check
• Controller conflict — Steam Input passes through device IDs that Unity's new input system cannot parse (most common with DS3, generic XInput)
• Overlay injection — GeForce Experience, NVIDIA App, Discord, MSI Afterburner, RivaTuner, OBS Game Capture
• DirectX 12 fallback failure — Silksong defaults to DX11 but falls back to DX12 on certain RTX 40/50 series, triggering a D3D_FEATURE_LEVEL_12_0 mismatch
• Antivirus quarantine — Bitdefender, Avast, and Windows Defender SmartScreen flag Hollow Knight Silksong.exe heuristically on first launch

Step-by-step fixes

1. Install the latest Visual C++ Redistributable (the #1 fix) — Download VC_redist.x64.exe directly from Microsoft at aka.ms/vs/17/release/vc_redist.x64.exe. Run the installer, choose "Repair" if it says already installed, and reboot. This single step resolves the majority of Silksong startup crashes.

1. Verify game files — In Steam: right-click Hollow Knight: Silksong > Properties > Installed Files > "Verify integrity of game files". In Epic Games Launcher: Library > three-dot menu on Silksong > Manage > Verify. Expect 30-200 MB of redownload on first verify.

1. Clear the Unity shader cache — Navigate to %LOCALAPPDATA%\Team Cherry\Hollow Knight Silksong\ and delete the il2cpp_data and shaders subfolders. Do NOT delete SaveData (your save). The cache rebuilds on next launch (longer first load is expected).

1. Unplug all controllers and disable Steam Input — Disconnect every USB controller, then in Steam: right-click Silksong > Properties > Controller > set "Override for Hollow Knight Silksong" to "Disable Steam Input". Reconnect controllers one at a time after the game reaches the menu to identify the offender.

1. Update GPU drivers and clear the cache — NVIDIA users: install Game Ready driver 566.36 or newer via the NVIDIA App or DDU + clean install. AMD: install Adrenalin 25.1.1+. Intel Arc: install 31.0.101.5333+. After install, delete %LOCALAPPDATA%\NVIDIA\DXCache and %LOCALAPPDATA%\AMD\DxCache.

1. Disable all overlays — Steam: Properties > General > uncheck "Enable the Steam Overlay while in-game". Discord: User Settings > Game Overlay > toggle OFF. NVIDIA App: Settings > General > Overlay > OFF. Close MSI Afterburner, RivaTuner Statistics Server, and OBS before launching.

1. Force DirectX 11 via launch options — Steam: right-click Silksong > Properties > Launch Options > type -force-d3d11 -screen-fullscreen 1. This forces the Unity 6 runtime to use the stable DX11 path and skips the DX12 feature negotiation that fails on some RTX cards.

1. Whitelist Silksong in Windows Defender and your antivirus — Settings > Privacy & Security > Windows Security > Virus & threat protection > Manage settings > Exclusions > Add exclusion > Folder. Add the full Silksong install folder (typically C:\Program Files (x86)\Steam\steamapps\common\Hollow Knight Silksong\). Repeat for any third-party AV.

If it still doesn't work

If Silksong still crashes after all eight steps, check the Unity Player log at %USERPROFILE%\AppData\LocalLow\Team Cherry\Hollow Knight Silksong\Player.log. Search for the strings LoadLibrary, D3D11CreateDevice, or Crash!!! — these point to the failing subsystem. A line containing vcruntime140_1.dll confirms the VC++ Redistributable fix. A D3D11CreateDevice failed line means your GPU driver is too old or your monitor is running an unsupported refresh rate (try setting your display to 60 Hz before launching).

For the specific Unity 6000.0.50f1 error, the patch on October 17, 2025 introduced a workaround: add the launch option -systemallocator (Steam Launch Options) to bypass Unity's broken default memory allocator on certain Ryzen 7000/9000 systems. Persistent crashers can downgrade to the launch-day build via Steam: Properties > Betas > select launch_build from the dropdown. Report new crashes on the [Team Cherry support page](https://support.teamcherry.com.au) with your Player.log attached.