Emulator

Try using the Reset All Settings button on the Advanced config tab.

I wonder if it's possible that there is an issue with the Qt6 interface?
If so, then this is the biggest regression yet.

In my experience, whenever I selected a game, the program hangs for a few seconds before the program closes altogether. It doesn't even spit out a crash log. It's that big of a regression.

Update 2026-10-3:
I Can confirm version 2606 is also affected by this on my end.

My build is
Windows 11 Home 26H2
NVIDIA RTX 4060 Laptop(8 GB VRAM)
Intel Core i7 13650HX
64 GB DDR5 RAM

I think I've figured out the problem. It's likely a stack overflow.

Log Name: Application
Source: Application Error
Date: 2026-10-04 9:47:42 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User:
Computer:
Description:
Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x49b795d5
Faulting module name: ucrtbase.dll, version: 10.0.26100.9444, time stamp: 0x2bbefd73
Exception code: 0xc0000409
Fault offset: 0x00000000000a527e
Faulting process id: 0x4258
Faulting application start time: 0x1DD547C42F990C3
Faulting application path: D:\Emulators\Dolphin-x64\Dolphin.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 3a132998-f4ae-4c54-9b36-da95800e18d6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

97649


Application
AkiTaka



Dolphin.exe
0.0.0.0
49b795d5
ucrtbase.dll
10.0.26100.9444
2bbefd73
c0000409
00000000000a527e
0x4258
0x1dd547c42f990c3
D:\Emulators\Dolphin-x64\Dolphin.exe
C:\WINDOWS\System32\ucrtbase.dll
3a132998-f4ae-4c54-9b36-da95800e18d6

Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x49b795d5
Faulting module name: ucrtbase.dll, version: 10.0.26100.9444, time stamp: 0x2bbefd73
Exception code: 0xc0000409
Fault offset: 0x00000000000a527e
Faulting process id: 0xC9B8
Faulting application start time: 0x1DD547A52DEAB5C
Faulting application path: D:\Emulators\Dolphin-x64\Dolphin.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: c9755d0a-d1c5-4bca-ad8a-92d9e8892280
Faulting package full name:
Faulting package-relative application ID:

I have reinstalled and repaired the redistributables and restarted. Still the same.

Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x49b795d5
Faulting module name: ucrtbase.dll, version: 10.0.26100.9444, time stamp: 0x2bbefd73
Exception code: 0xc0000409
Fault offset: 0x00000000000a527e
Faulting process id: 0x4110
Faulting application start time: 0x1DD5486470CB029
Faulting application path: D:\Emulators\Dolphin-x64\Dolphin.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: a3a7be8a-a419-4a83-95de-850cd8079c70
Faulting package full name:
Faulting package-relative application ID:

Have you tried the Reset All Settings button on the Advanced config tab in Dolphin ?

I have done so as well.

To no avail.

I wonder if it has to do with the recent Windows 26H2 update?

I can confirm that all versions BEYOND version 2503x64 are affected by the crashes that happen when selecting a game from the UI.

If you figure out the first specific development version that introduced this issue it would be easier to narrow down the cause.

well, that's the thing, they all worked fine until after applying the 26H2 update. 2506 is the first version to be affected by the crashes onwards. I believe it was also the first version that integrated Triforce Arcade board support.

There are many versions between 2503 and 2506. Please figure out the first one that's problematic for you.
https://dolphin-emu.org/download/list/master/1/

JSYK, HAGS is currently enabled on my laptop.

"2503a" is the final version of Dolphin that runs properly. All the others beyond that, don't work at all. I've exhaustively checked all of those ones hoping for a miracle. even the latest build had no luck.

There are many versions between 2603a and 2606, e.g. 2606-203.
https://dolphin-emu.org/download/list/master/1/

To find out which Dolphin development release an issue first appeared in, you can use a process called bisecting.
For this, you will need a known good release where the issue does not happen and known bad release where the issue does happen.

For each iteration, test the release halfway between your current known good and bad releases. If it's good, it becomes your new known good release, and if it's bad it becomes your new known bad release.

Repeat until you have identified the first bad development release.

Ive turned of HAGS and restarted; the issue is still occurring on the latest build of Dolphin.

as well as the earliest build of Dolphin beyond version 2503a.

I can confirm no luck with the Dolphin version 2609a. The 0xc00000409 error is still present.

Despite all I've tried, I guess I'll have to wait for Patch Tuesday at this rate.

Good morning, everyone.

I am now updated to Windows 11 26H2 Build Ver. 26300.9711(as of 10-13-2026)

I have installed the newest build of Dolphin (2609-81)

The error still pursues.

Exception code: 0xc0000409
Fault offset: 0x00000000000a527e

Event Viewer is the only place I can read this.