In a game as ambitious as Starfield, there will always be situations the developers overlooked during testing, such as quest bugs. One such bug can happen to players while trying to complete the main relationship quest with Sarah Morgan. Here's how you can fix the In Memorium quest bug in Starfield.
Starfield In Memoriam quest - Sarah Bug Fix
Issues occur with the Starfield In Memorium quest for players who begin the quest, then leave to complete other content. This means Sarah won't be with you at a key moment during the quest. Unfortunately, there isn't a specific bug fix right now. However, if you just work through the mission step by step, without doing anything else, you should be OK. The easiest way to fix it is to reload to a save point before the bug occurs and then do the quest again. If this isn’t an option because you’ve done too much in between, or don’t have a suitable save point, read on below.
Here are some known triggers for the bug:
- Can’t talk to Sona: When you get to the latter part of the In Memorium quest, which involves talking to Sona, you may not be able to speak to her when you approach her. As you gain Sarah as a permanent companion until this quest line is resolved, it means that if you don’t complete the quest you’re stuck with Sarah.
- Can’t talk to Sarah: If you approach the War Memorial with the quest active by Sarah isn’t with you, this can trigger the quest to move on but without the required conversation with Sarah. When you try to speak to Sarah later at the Lodge she’ll walk away and not speak to you, meaning you can’t progress.
Some players have reported that the issue will be resolved after talking to everyone after the funeral during the Missed Beyond Measure main storyline quest, but I can't confirm this. If you can, let me know in the comments.
If these fixes don’t work for you, you try a more drastic measure such as firing Sarah from your crew and meeting her back at the Lodge, but again this is not guaranteed to work. Outside of this, I suggest you contact Bethesda support and report it. Hopefully, it will be properly fixed in a patch soon.