Windows 11 version 26H2 (build26300.9550) - post install multiple Microsoft games fail to run

Question

Windows 11 version 26H2 (build26300.9550) - post install multiple Microsoft games fail to run

Dan Hunter 0

before - Windows 11 - unknown version and build - multiple microsoft games open and run with no problems
problem - Windows 11 version 26H2 fails to install using windows update
solution - download and installed stand alone update package for Windows 11 version 26H2
after - Microsoft Solitaire and casual games starts to open, then terminates
retry - uninstall, download, re-install Microsoft Solitaire and casual games - same problem
alternate - tried to open Clockmaker: Match 3 Puzzle Game - same symptions as Solitaire - starts to open then terminates
multiple shut downs of PC during steps 1 thru 6
final - chat with Microsoft support

0 comments

2 answers

Your answer

Answer 1

For Microsoft Store games that start to open and then immediately close after the 26H2 standalone update, use the Microsoft Store and app recovery steps first:

Sign in with the Microsoft account used for the games.
Close the game completely, then reopen it.
Check Windows Update: Start > Settings > Windows Update > Check for updates. Install any available updates.
Update Microsoft Store: open Microsoft Store > Library > Get updates.
Repair or reset the affected apps:
- Start > Settings > Apps > Installed apps
- Select Microsoft Solitaire Collection or the affected game
- Select Advanced options
- Select Repair
- If it still fails, select Reset
- Note: reset can remove app data for that app.
If the app still fails, reinstall it from Microsoft Store > Library > Install.
Restart the PC after these steps.

Because the issue started after upgrading to Windows 11 version 26H2, also check for upgrade-related problems and submit feedback through Feedback Hub if the failures continue.

If multiple Microsoft Store games are affected after the upgrade and the steps above do not resolve it, use the Windows upgrade troubleshooting guidance for installation and post-upgrade issues, then contact Microsoft support as the next step.

Answer 2

Hendrix-V 20,225 Microsoft External Staff Moderator

Hi Dan Hunter,

Since multiple Store games started closing immediately after the Windows 11 26H2 update, and reinstalling Solitaire did not help, it would be useful to check whether Windows system components were affected during the update.

Please try these following steps:

Open Terminal (Admin).
Run: DISM /Online /Cleanup-Image /RestoreHealth
When completed, run: sfc /scannow
Restart Windows and test the games again.

If the games still close immediately, please check Event Viewer > Windows Logs > Application immediately after reproducing the issue and share the error entry associated with the affected game. The Faulting application, Faulting module, and Exception code would be particularly helpful for narrowing down the cause.

I hope this helps identify what is causing the applications to terminate.

Hendrix-V 20,225 Reputation points Microsoft External Staff Moderator

2026-10-16T07:53:51.97+00:00

Hi Dan Hunter,

I just wanted to follow up and check if the information I provided was helpful. If you have any further questions or updates regarding this issue, please feel free to let me know in the Comments section. I'd be happy to assist you.
Dan Hunter 0 Reputation points

2026-10-16T23:40:54.4133333+00:00

I ran the commands as instructed, but interpreting the output in the event viewer is something I have never done. I have filtered the viewer down to an 8 minute custom view and saved it. Frankly, it's a wonderful pile of gibberish at this point.
Hendrix-V 20,225 Reputation points Microsoft External Staff Moderator

2026-10-17T01:16:55.8366667+00:00
Hi Dan Hunter,

Thank you for running those checks. I understand why Event Viewer looks overwhelming, especially when an 8-minute window can contain many unrelated entries, but you do not need to interpret the whole custom view. Instead:

Open Event Viewer > Windows Logs > Application.

Launch Solitaire and let it crash/close.

Immediately return to Event Viewer and look for an Error recorded at approximately the same time.

Open that error and copy the text from the General tab.

The most useful details will be entries containing the application's name and fields such as Faulting application name, Faulting module name, and Exception code.

Please paste that specific event here. We can then use the actual crash details to determine the next troubleshooting step rather than trying additional fixes blindly.