Fallout 4 Stuck in Cryo chamber

David Murphy

Distinguished
Jun 7, 2013
48
0
18,530
So I recently started a new game on Fallout 4.
I did everything normally. Bombs dropped, entered Vault 111, got in the cryochamber, watched my wife get murdered etc.
But then he goes back to sleep and wakes up again but after he wakes up I literally can't do anything at all.
The wife's body is gone from the cryochamber but I am stuck inside mine. Can't move the mouse, can't move the character, can't do anything.

So far I have tried:
Restarting the game.
Restarting the computer
Removed all mods
Deleted all previous save games
Started another new game
Uninstalled and reinstalled the game
Used commands to teleport to different locations

None of these have worked. When I teleported to different locations I had exactly the same problem but in a different location.

I tried 'Setstage mq101 805' then 'Setstage mq101 900' and absolutely nothing happened at all.
No error message saying the command didn't work. It went through as they usually do, but I still cannot progress through the game.

Does anybody have any advice?

Thanks
 
Solution
How many SSD or HDD's do you have? One thing i'm wondering about is even though you've deleted the mods and verified the files I feel somewhere in the game file (uploaded in Steam) there is a corrupt file causing this issue. I would try this if you have multiple drives (in order as listed).

-Delete all mods from the game files and uninstall them from Nexus Mod Manager (If your using this tool as well)
-Delete all saves
-Verify integrity of game cache in Steam
-Uninstall the game from the drive your currently using
-Reinstall Fallout to another drive

I had to do this for Skyrim when I heavily modded it and even though I removed the mods the game still had bits and pieces of the mods still in the game folder which was still kept by...


Yeah it's a legit copy. I couldn't see a 'repair' option. Closest there is is 'Verify integrity of game cache' which I also tried with no luck :\

I didn't back up the original files, but I deleted literally everything to do with the game when I reinstalled it.
 
dasBenni has Fallout 4 28 Nov, 2015 @ 10:39pm
Long shot: At the point this happens, open console.
Type

SetStage mq101 805

Close console
Wait for screen to turn all white

Open console
Type
SetStage mq101 900

Close console
found this on the steam forum when it buuged out.
give it a try it worked for me.

it should teleport your currently awake partner back into the cryo opposite, they will fall asleep. then sequence should continue as normal.



 


Tried creating a female character as you suggested and got the same thing :\



Tried that already. I did say that in the OP. Absolutely nothing happens when I use those commands. Almost like I never put any commands in to begin with (but I definitely did)
 
How many SSD or HDD's do you have? One thing i'm wondering about is even though you've deleted the mods and verified the files I feel somewhere in the game file (uploaded in Steam) there is a corrupt file causing this issue. I would try this if you have multiple drives (in order as listed).

-Delete all mods from the game files and uninstall them from Nexus Mod Manager (If your using this tool as well)
-Delete all saves
-Verify integrity of game cache in Steam
-Uninstall the game from the drive your currently using
-Reinstall Fallout to another drive

I had to do this for Skyrim when I heavily modded it and even though I removed the mods the game still had bits and pieces of the mods still in the game folder which was still kept by Steam.

Also make sure in properties that they game is checked off to make sure its automatically kept up to date.
 
Solution
You are right, I have an SSD and HDD. Windows and Fallout are on the SSD, Steam is on the HDD.

I will give that a try asap.
Thanks matey



 

that could be your using the wrong key to open the console try using the # or @ keys if your using a keyboard set to something other than english u.s.

i was pressing the tilde key and nothing happened. i hit @ key and the console command then appeared to work.