Update failure game restarted nothinghappens

Dear. The game was purchased by GAMEPASS, but as is reported, if I download it, let the game download I don't need to buy another one, just keep playing. My problem was that when updating the game as requested by XBOX, the update crashed and it was necessary
to restart the entire system. After the system restarted I looked at the library and the game was no longer available. That's why I'm complaining. It was a system failure.

forums.epicgames.com/.../950366-Title-update-failure!!!!-Backup-your-game!!!!

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.

[quote user="brandiesel1"]^^ So are you saying that the updates cause the subsystem failure which in turn bricks the console?[/quote]The updates expose failure of an update subsystem component. They do not cause the failure. If you have a console that is
offline between several update cycles and the flash memory goes bad during that offline period, ANY update would cause a failure, not just a specific update.

Your console asked for an update because the hard drive failed and it could not read the previous install of the update. It's not the update that causes the failure but rather the failure causes the need for an update.