Game no longer works after last update

[Oriflame]

Get error message "Something went wrong in the Shader Cache Builder process. Exit Code = 0xC000012F"
-Edit; fixed by uninstalling all c++ runtimes (did get errors for the -2022 one t hough during this process) then nuked every c++ runtime entry in the registry (regedit) and rebooted; then installed each c++ runtime one by one without any errors on the -2022 one (which was giving errors on install and uninstall previously); then reboot and blam problem fixed.

[Tunnfisk]

Originally posted by Oriflame:

Get error message "Something went wrong in the Shader Cache Builder process. Exit Code = 0xC000012F"

Delete old shader catalog and run a "verify file integrity" on Steam.

[Oriflame]

Originally posted by Tunnfisk:

Originally posted by Oriflame:

Get error message "Something went wrong in the Shader Cache Builder process. Exit Code = 0xC000012F"

Delete old shader catalog and run a "verify file integrity" on Steam.

same issue: GUID: 9bd60c3c-1c9f-441c-b8fc-c8b58efb6a60

[Cyzxxikz]

Originally posted by Oriflame:

Originally posted by Tunnfisk:

Delete old shader catalog and run a "verify file integrity" on Steam.

same issue: GUID: 9bd60c3c-1c9f-441c-b8fc-c8b58efb6a60

idk if you found it since this changed, but.
paste "%AppData%\Fatshark\Darktide" into Run dialog box (Windows key+R)

also i did see one user reporting turning off FSR solved it for them.
another fixed it with a full reinstall of windows after having tried just about everything.

[Oriflame]

Originally posted by Cyzxxikz:

Originally posted by Oriflame:

same issue: GUID: 9bd60c3c-1c9f-441c-b8fc-c8b58efb6a60

idk if you found it since this changed, but.
paste "%AppData%\Fatshark\Darktide" into Run dialog box (Windows key+R)

also i did see one user reporting turning off FSR solved it for them.
another fixed it with a full reinstall of windows after having tried just about everything.

Same error with Vermintide 2 since update as well I am noticing ; RAGE 2, Red Dead Redemption 2, Cyberpunk 2077, Battlefield 2042, Apex Legends (DX11), Hitman 3, Ready or Not (DX11), Rainbow Six Extraction, Destiny 2 all work fine; but since the last update to Vermintide 2 and Dark Tide in the past weeks those two games do not work at all and give the same error.

[Tunnfisk]

Originally posted by Oriflame:

Originally posted by Cyzxxikz:

idk if you found it since this changed, but.
paste "%AppData%\Fatshark\Darktide" into Run dialog box (Windows key+R)

also i did see one user reporting turning off FSR solved it for them.
another fixed it with a full reinstall of windows after having tried just about everything.

Same error with Vermintide 2 since update as well I am noticing ; RAGE 2, Red Dead Redemption 2, Cyberpunk 2077, Battlefield 2042, Apex Legends (DX11), Hitman 3, Ready or Not (DX11), Rainbow Six Extraction, Destiny 2 all work fine; but since the last update to Vermintide 2 and Dark Tide in the past weeks those two games do not work at all and give the same error.

Then I would go to FS official forum in the tech support section and ask for help there. I think there is also some support over on the Darktide Discord server.

[Oriflame]

Originally posted by Tunnfisk:

Originally posted by Oriflame:

Same error with Vermintide 2 since update as well I am noticing ; RAGE 2, Red Dead Redemption 2, Cyberpunk 2077, Battlefield 2042, Apex Legends (DX11), Hitman 3, Ready or Not (DX11), Rainbow Six Extraction, Destiny 2 all work fine; but since the last update to Vermintide 2 and Dark Tide in the past weeks those two games do not work at all and give the same error.

Then I would go to FS official forum in the tech support section and ask for help there. I think there is also some support over on the Darktide Discord server.

Ok thanks guys; sincerely appreciate your time and help.

[Oriflame]

-Edit; fixed by uninstalling all c++ runtimes (did get errors for the -2022 one t hough during this process) then nuked every c++ runtime entry in the registry (regedit) and rebooted; then installed each c++ runtime one by one without any errors on the -2022 one (which was giving errors on install and uninstall previously); then reboot and blam problem fixed.

[Cyzxxikz]

Originally posted by Oriflame:

-Edit; fixed by uninstalling all c++ runtimes (did get errors for the -2022 one t hough during this process) then nuked every c++ runtime entry in the registry (regedit) and rebooted; then installed each c++ runtime one by one without any errors on the -2022 one (which was giving errors on install and uninstall previously); then reboot and blam problem fixed.

appreciate you updating with the fix.