Xbox restart after starfield update

Yes.. same o allways. Reinstall, Restart, Update....

This error is common here to me. To reproduce I only need to restart PC without closing the game first.

I use XBOX Ultimate and play starfield in XBOX and PC.

Microsoft or Bethesda needs to fix this problem. Is very annoing.

follow these steps

To restore the settings of a limited edition Starfield headset, the main thing to do is to reset the headset and, if necessary, force an update through the Xbox.

1. Reset the Headset:

Press and hold the mute button and the power button simultaneously for about 15 seconds.

This process will force a reset of the headset, and then you can reconnect it and check if the Starfield sounds have been restored.

2. Force Update on Xbox (if applicable):

Connect the headset to the Xbox.

Go to Settings > Devices and Connections > Controllers and Headsets.

Locate the connected headset and click on the options menu (three dots) below Configure.

Even if it says "No update available", press the A button on this message to force the update.

After the update, the Starfield theme sounds should be restored

I can confirm that Bethesda Starfield cannot launch (via Steam) under Windows 11 23560.1000, 23565.1000 or 23570.1000.

- Install any prior build/release of Windows 11 pre 23560.1000

- Install Steam,

- Install latest graphics drivers for nvidia/ati card,

- Install all Windows updates prior to 23560.1000 or out-of-band updates,

- Restart,

- Install Starfield,

- Steam -> Play -> application runs normally,

- Restart,

- Steam -> Play -> application runs normally,

- Update to 23560.1000, 23565.1000, 23570.1000,

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no registry/file/device failures,

- Check for / install any device driver updates, e.g. latest nvidia driver,

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no

- Uninstall Starfield + Restart + Reinstall Starfield

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no,

- Use Recovery -> Go Back to restore to previous windows build,

- Restart,

- Without reinstalling Starfield, Steam -> Play -> *application runs normally,

I also observed that manually attempting to launch the executable also results in a simple termination during startup, and procmon/windbg doesn't show anything significant. While this may be a bug in Starfield's code, perhaps undefined behavior, it is clearly triggered by something that changed in Windows recently.

I look forward to mocking you for replying with a form post listing steps to try.

PS: With both 23560.1000 and 23570.1000 I have submitted Feedback reports that include recordings of the application attempting to launch.

Because of xbox app is broken when you uninstall-reinstall the game or verify the game files, files are not uninstalling completely or not installing correctly. So first uninstall the game from xbox app then uninstall the xbox app. Reset microsoft store from settings>apps>advanced settings. Check documents/my games if there is starfield folder delete it. Install ccleaner for pc open disk analyzer on ccleaner and search for starfield, delete every file you see there. Restart. Reinstall the xbox app from microsoft store, then install starfield at one time without pause and you're good until next update...

I can confirm that Bethesda Starfield cannot launch (via Steam) under Windows 11 23560.1000, 23565.1000 or 23570.1000.

- Install any prior build/release of Windows 11 pre 23560.1000

- Install Steam,

- Install latest graphics drivers for nvidia/ati card,

- Install all Windows updates prior to 23560.1000 or out-of-band updates,

- Restart,

- Install Starfield,

- Steam -> Play -> application runs normally,

- Restart,

- Steam -> Play -> application runs normally,

- Update to 23560.1000, 23565.1000, 23570.1000,

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no registry/file/device failures,

- Check for / install any device driver updates, e.g. latest nvidia driver,

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no

- Uninstall Starfield + Restart + Reinstall Starfield

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no

- Restart,

- Steam -> Play -> application exits immediately, no obvious failures show via procmon - no,

- Use Recovery -> Go Back to restore to previous windows build,

- Restart,

- Without reinstalling Starfield, Steam -> Play -> *application runs normally,

I also observed that manually attempting to launch the executable also results in a simple termination during startup, and procmon/windbg doesn't show anything significant. While this may be a bug in Starfield's code, perhaps undefined behavior, it is clearly triggered by something that changed in Windows recently.

I look forward to mocking you for replying with a form post listing steps to try.

PS: With both 23560.1000 and 23570.1000 I have submitted Feedback reports that include recordings of the application attempting to launch.

I can confirm that I had the same issue and performed all the steps you mentioned above with the same results.

It really is a mockery of the end user when all the replies seem to be stock responses that the majority of users would have already tried, what is the point of the insider channel if Microsoft aren't going to listen to the feedback and just try to deny any error on their part.

I understand it may be a coding issue with Bethesda but as the game worked prior to the latest update I very much doubt it.

EDIT: I have to admit egg on my face for this one because for some reason after uninstalling 23570.1000 and pausing updates for a week the update was reinstalled today 23/10 and Starfield is running fine even with mods installed, I have no idea what the original issue was but I'm glad the issue resolved itself