MMDevApi.dll bug report (Windows 11 24H2)

I'm the developer of text-to speech (TTS) application, it has been distributed for many years, and there have been no problems with MMDevApi.dll, from Windows XP to Windows 11 23H2. Now I get dozens of complaints about the same situation: a user upgraded Windows 11 to 24H2, and now my program crashes, and in the Event Viewer the error description has a reference to MMDevApi.dll.

Problems detected:

1. The text-to-speech program crashes if the list of audio output devices is changed.
2. The text-to-speech program crashes if a computer voice starts reading text aloud (voices for SAPI 5 are used).
3. The text-to-speech program does nothing, a user runs any audio/video player, and the text-to-speech program crashes.

The first point is obvious: the program uses IMMDeviceEnumerator interface to keep track of changes in the list of output audio devices. If the list changes, my program crashes in Win11 24H2. The cause of the problem is the MMDevApi.dll system library. Win11 23H2 and previous versions of the operating system did not have this problem.

Interesting discovery was made by one of the users: if you launch the “Windows 11 Media Player” application and keep it open, and then launch the text-to-speech program, the program works stably (the TTS program does not crash).

Re-registering the MMDevApi.dll system library did not help. Changing the compatibility mode for the EXE-file to “Windows 10” did not help.

As far as I know, the developers of several other TTS programs have encountered the same problem. Apparently the problem is related to a library MMDevApi.dll in the 24H2 update, but what to do and how to fix it is unclear. Please, help!

Here is the error information in the Event Viewer.

Log Name:      Application
Source:        Application Error
Date:          10/31/2024 11:07:11 AM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Faulting application name: balabolka.exe, version: 2.15.0.880, time stamp: 0x671d5513
Faulting module name: MMDevApi.dll, version: 10.0.26100.1882, time stamp: 0xbe6f88f4
Exception code: 0xc0000005
Fault offset: 0x0002564d
Faulting process id: 0x264C
Faulting application start time: 0x1DB2B41EE0B94D1
Faulting application path: C:\Program Files (x86)\Balabolka\balabolka.exe
Faulting module path: C:\WINDOWS\System32\MMDevApi.dll
Report Id: 0def1e0f-f143-4998-840b-4573e20dcd0e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
   <System>
     <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
     <EventID>1000</EventID>
     <Version>0</Version>
     <Level>2</Level>
     <Task>100</Task>
     <Opcode>0</Opcode>
     <Keywords>0x8000000000000000</Keywords>
     <TimeCreated SystemTime="2024-10-31T03:07:11.0418263Z" />
     <EventRecordID>1889</EventRecordID>
     <Correlation />
     <Execution ProcessID="16332" ThreadID="6424" />
     <Channel>Application</Channel>
   </System>
   <EventData>
     <Data Name="AppName">balabolka.exe</Data>
     <Data Name="AppVersion">2.15.0.880</Data>
     <Data Name="AppTimeStamp">671d5513</Data>
     <Data Name="ModuleName">MMDevApi.dll</Data>
     <Data Name="ModuleVersion">10.0.26100.1882</Data>
     <Data Name="ModuleTimeStamp">be6f88f4</Data>
     <Data Name="ExceptionCode">c0000005</Data>
     <Data Name="FaultingOffset">0002564d</Data>
     <Data Name="ProcessId">0x264c</Data>
     <Data Name="ProcessCreationTime">0x1db2b41ee0b94d1</Data>
     <Data Name="AppPath">C:\Program Files (x86)\Balabolka\balabolka.exe</Data>
     <Data Name="ModulePath">C:\WINDOWS\System32\MMDevApi.dll</Data>
     <Data Name="IntegratorReportId">0def1e0f-f143-4998-840b-4573e20dcd0e</Data>
     <Data Name="PackageFullName">
     </Data>
     <Data Name="PackageRelativeAppId">
     </Data>
   </EventData>
</Event>