@SP.

Hi,

Actually, I have 3 monitors. I will give it a go. However, I fail to see how two versions of the program can go from working to not working almost overnight. They worked fine with all 3 monitors working.

John CB

@SP.

Hi,

I just tried rebooting with 2 monitors, no change. Rebooting with 1 monitor, no change.

John CB

@browj2 OK. In case you didn't try to delete/rename the musicmaker.ini file to reset the program settings, I suggest you try that as well. It should be located in the \AppData\Roaming\MAGIX\MM2026_Premium\ folder. But you'll find this file only if you were able to start and close Music Maker normally at least once. Next, in case it still doesn't start, you might simply try to disable Internet in case it gets stuck on trying to connect to the in-app-store.

@browj2

Hi John,

No, I don't see the specific problem you raise here.

BUT, there are quite a number of people, myself included, who use Adobe Audition CC and who are experiencing a very similar "bug" (not sure about other Adobe apps, I only use Audition). Specifically, it freezes during boot-up; for me it occurs whilst attempting to create the User Interface. Sometimes the full UI appears, but then nothing can be done to actually edit any audio; within no more than a few minutes the freeze occurs again!

I'm not sure whether non-Adobe users can access their user forums but the specific thread is here.

I have raised this as a bug with Adobe Technical, but I wonder whether this is something actually caused by a recent Win 11 update? If I hear any thing possibly relevant to this from Adobe Support I will post here again.

Jeff

@emmrecs

Hi Jeff,

Thanks for the information. I suspect MS as well as that is the only explanation for such an occurrence since MM 2025 has also been affected.

I have loaded most Magix programs that I still have on the computer, new and old, and they all work, including Samplitude Pro X8 Suite.

I will raise a ticket with Magix, for what it's worth.

@SP.

Hi,

I turned off internet access for my computer, restarted Music Maker 2025, no change.

The first thing that I did was remove the ini file. A new one was not generated as it seems that Music Maker doesn't get to that point during opening; it stalls first. Putting back the working ini file did not help.

John CB

@SP.

Hi,

In trying to raise a ticket, I have to put in the version. I can't get to About to see the version. What is the latest version number for MM2026 Premium?

Thanks,

John CB

@browj2

Hi John

The version number for MMM 2026 is 34.0.0.6

I, too, cannot replicate the issues you are having, including spreading different panes over 2 monitors, restarting they come back into their last used positions.

I am on the 591.86 drivers.

John EB

@browj2 @johnebaker

Just for "completeness" of information, I'm running the 595.71 drivers.

Jef

Hi,

Below is what Magix AI told me to check and I did. The startup problem still exists for both 2025 and 2026.

This freezing is a known issue under Windows 11, typically caused by conflicts with certain Windows accessibility features or third-party applications. Please ensure the following Windows "Ease of Access" features are turned off:

• Text cursor indicator
• Screen reader (Microsoft Narrator)
• Screen magnifier
• Speech recognition

Additionally, close or disable these third-party applications before starting Music Maker, as they are known to cause conflicts:

• Reverso (Desktop App)
• Grammarly (Desktop App)
• Sticky Password
• DeepL (Desktop App)
• ZoomText
• Wacom Tablet Apps/Integration (disconnect your Wacom Tablet if connected)
• Microsoft Power Automate (Desktop App)

There is no direct evidence that a Windows 11 update or your NVIDIA driver version is the cause. While you have already set an exception for Bitdefender, you may also try temporarily disabling it to rule out interference.

This is most frustrating. Checking on the German forum, the same problem raised there has not been resolved.

I will keep pursuing Magix.

John CB

@browj2 You could try installing Music Maker in the Windows Sandbox app. That's a clean environment. If it starts without any problems there, we'll at least know that something in your actual Windows installation is blocking the program from running. If it also stops at Set Views inside the Sandbox app, it's likely a problem caused by Music Maker itself.

@browj2

Hi John,

Seeing this thread again has reminded me I intended to post an update on my similar trials with Adobe Audition.

After much reading (in the Audition forum and elsewhere) I eventually came across what, unlikely as it might seem, has proved to be the solution, for me and, it would appear, a multitude of other users!

But first, do you have any MIDI equipment/interface permanently connected to your computer? In my case I have a Midiman USB Midisport 4x4. I ask that because, if so, it may be the unwitting cause!

It seems that, with a recent update to Win 11, M$ made changes to some part of the MIDI "protocol" and this produces a conflict with the drivers for that interface. Simply unplugging the interface before attempting to open Audition resolves the problem! Unfortunately, given the age of that interface there are no "recent" drivers for it, and whatever changes were made to that MIDI "protocol" by M$ do not enable it to function without its dedicated drivers - I tested this by uninstalling all of them and then replugging in the unit; Windows Device Manager reported it then as "Unknown Device" and it did not function. Reinstalling the official drivers returned it to full working order, but still with the "interruption" to Audition functioning.

I just have to remember to unplug its USB lead every time I open Audition!

HTH

Jeff

@browj2, @emmrecs, @SP.

Hi Everyone

Have you seen this M-Audio article regarding the MS MIDI update.

John EB

@johnebaker

Hi John,

Thanks for that link!

I was basically aware of the reason for the problem but that article very clearly sets out why, and how to avoid it. I have run the linked midicheckker.exe, which confirms I do have the "problem" driver installed so I now need to consider whether to follow the advice and uninstall the Windows Update(s) that started it all, or whether I can simply continue to unplug my interface when attempting to use any affected software.

Interestingly, so far at least, MM is not affected by this on my computer.

Jeff

@johnebaker @emmrecs

Hi,

John EB, thanks for the link and Jeff, thanks for the tips. I have an M-Audio M-Track interface so I'll go through the steps indicated by M-Audio as soon as I've finished downloading and installing Vasco StreetMaps.

I see that I have 3 updates this year, KB5074109, KB5077181, and KB5079473, with KB5086672 pending. I am wondering if this pending update resolves the problem.

@SP. Thanks for the sandbox idea. That is something that I have never tried but I should.

John CB

@johnebaker @emmrecs @SP.

Hi,

Success! Well, almost. I installed the pending update, unplugged the M-Audio M-Track and restarted. Music Maker now loaded correctly. Plugging the M-Audio back in causes Music Maker to freeze. Exiting Music Maker with the Task Manager, unplugging the M-Audio and restarting Music Maker again causes it to freeze, so the only way to get Music Maker is to restart the computer with the M-Audio unplugged.

I have not had the same problem with Samplitude Pro X8. Even though Music Maker and Samplitude are similar (a Music Maker project can be opened in Samplitude), Magix has something in Music Maker that is not in Samplitude.

I ran the midicheckker and it shows that I have the problem driver, wdmaud2.drv, installed, as required by the new MIDI stack.

Following the suggestions in the M-Audio article, I went to see if I could uninstall KB5077181. It doesn't show up on the list for uninstall. So, I guess that I am stuck with this until Miicrosoft or Magix comes up with a solution.

At least, I can now use Music Maker...with high latency when using MIDI.

John CB

@browj2

I also have that specific update and, as you have found, it cannot be removed. Unplugging the interface seems to be the only solution at the moment but, since it is my only MIDI interface I need to see if I can buy a class-compliant replacement! Thank you M$. 😡

Jeff

@emmrecs

Hi Jeff,

Even though my M-Audio has MIDI in/out, I don't use that. My keyboard is connected to the computer by USB and works fine with Music Maker so long as the M-Audio is disconnected.

I think I'll try out my wife's fifine audio interface to see if it is infected.

Since Microsoft has broken this, I'll ask Copilot for a solution and pester M$ a bit. Also, M-Audio can come up with a new driver, or Magix can fix Music Maker since the problem is not also in Samplitude.

John CB

@emmrecs

Hi Jeff,

CoPilot wins the day!

Method 1 — Disable the Windows MIDI Service (most effective)

This forces Windows to fall back to the legacy MIDI system that M‑Audio drivers expect.

Steps:

1. Press Win + R
2. Type: services.msc
3. Look for one of these:
   1. Windows MIDI Service
   2. MIDI Service
   3. MIDI2 Service
4. Right‑click → Properties
5. Set Startup type to Disabled
6. Click Stop
7. Reboot

After reboot, your M‑Audio device will use the legacy MIDI stack again.

This alone fixes the freeze for most users.

If that doesn't work, there is more. For me, that worked!

John CB