Nuendo 13.0.55 hanging on start

[nestling]

3950x, 64GB 2400, AMD RadeonPro WX3200, Gigabyte Aorus Master x570.
Nuendo 13.0.55, W11Pro 25H2 26200.7922
After 6 flawless years, following a recent windows 11 update, Nuendo 13 hangs on initialize (usually on ‘initializing Midi’) or if it reaches the hub, it will hang several min later. The crash dumps (below) are not yielding info I can ascertain. I am not able to undo the update - “option no longer available on this PC”

I get the following Windows Event IDs:

Warning: 10016 DistributedCOM - I’ve spent days attempting to mod permissions via Component Services but these same warnings persist regardless.
Error TPM-WMI 1796 -it says Secure Boot is not enabled, but it is.
Error TPM-WMI 1801 i have updated bios to latest and verified Secure Boot but Windows seems to not recognize this yet.
I was hoping to get another 5 yrs out of this set up. Any help would be beyond appreciated.

Nuendo 13.0.55 64bit 2026.2.26 12.50.03.609-freezedump.dmp (824.6 KB)

[stingray]

May be related to this: CB15 freezes om Midi Initialisation

[Psychlist1972]

Can you share any information about which MIDI devices you have? Any virtual devices like loopMIDI? Any old m-audio devices? Any Korg devices? Other third-party drivers like ESI? Any and all details here could help us track down what is happening.

Worst case, you can use the work around in the #start-here channel on our MIDI discord Windows MIDI / Audio

Pete
Microsoft

[nestling]

Thanks so much for your help Sir!

My primary midi box is an old M-Audio MidiSport Uno. I’ve never had any sort of midi issue. I record and mix audio via microphones mainly. No Korg devices. Sorry no idea what ESI is. But After days of forum reading and noting that gamers are lamenting identical issues ie freezing on start/hanging several minutes in, following the W11 update, I assumed this has to be more related to expiring security certificate conflicts ( recurring 10016s which refuse to adopt remediating edits - below) and all the secure boot nonsense which also refuses to comply with Mobo settings.

Prior to Nuendo’s failure there are no errors on Windows System event logs. After failure (this morning I started successfully, ran for a few min and exited but then I am unable to initialize again - it is frozen) I get the same list of culprits (despite doing everything in my current capacity to remediate - doing Nuendo on Windows as a profession since 1999):

Despite the prior System log event being a 1025: “The TPM was successfully provisioned and is now ready for use” - I get the following consistently:
The Secure Boot update failed to update Windows UEFI CA 2023 (DB) with error Secure Boot is not enabled on this machine.. For more information, please see …

The Secure Boot update failed to update Option ROM CA 2023 (DB) with error Secure Boot is not enabled on this machine.. For more information, please see ..

The Secure Boot update failed to update 3P UEFI CA 2023 (DB) with error Secure Boot is not enabled on this machine.. For more information, please see …

The Secure Boot update failed to update KEK 2023 with error Secure Boot is not enabled on this machine.. For more information, please see …

The Secure Boot update failed to update Boot Manager (2023) with error Secure Boot is not enabled on this machine.. For more information, please see ..

Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here.
DeviceAttributes: BaseBoardManufacturer:Gigabyte Technology Co., Ltd.;FirmwareManufacturer:American Megatrends International, LLC.;FirmwareVersion:F39;OEMModelNumber:X570 AORUS MASTER;OEMModelBaseBoard:X570 AORUS MASTER;OEMModelSystemFamily:X570 MB;OEMManufacturerName:Gigabyte Technology Co., Ltd.;OEMModelSKU:Default string;OSArchitecture:amd64;
BucketId: 98b69615ca769d8abbf66b38c57609863eaa24131c5f4d96f7bcdfecaaaa8588
BucketConfidenceLevel: Under Observation - More Data Needed
UpdateType:
For more information, please see …

---

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-N7PU4IH\solar SID (S-1-5-21-2953709888-3495788199-715128533-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

[trmupstage]

I have another thread open on that same issue. It has to do with Midi 2 and older USB MIdi drivers. I had to roll back a windows update to get Nuendo to open again. My main midi interface is a Midisport 4x4. On another forum, Pete said there were compatibility problems with those drivers. Kind of sucks. I wouldn’t evn know what midi interface to get at this point.

[bigcat75]

@trmupstage

I wouldn’t evn know what midi interface to get at this point.

Yeah, I use an old MOTU MTP AV USB. I hope this update doesn’t kill it. I’ve got MIDI Quest running perfectly with this thing and I, too, wouldn’t know what to get to replace it.

[nestling]

If drivers are the issue, I tried uninstalling the M-Audio Midisport. That hung the Management Console:

The application \Device\HarddiskVolume2\Windows\System32\MidiSrv.exe with process id 12552 stopped the removal or ejection for the device USB\VID_0763&PID_1011\6&2838f1dc&0&4.
Process command line: C:\WINDOWS\system32\midisrv.exe
List of affected devices:
USB\VID_0763&PID_1011\6&2838f1dc&0&4

Will try for a manual driver purge and see if Nuendo will start.

[Psychlist1972]

The M-Audio driver is a problem. We’ve always seen tons of errors from those drivers on Windows, but because the old stack had apps talking directly to drivers, it only resulted in app crashes or weird behavior that could be ignored.

The midisport uno works fine with our in-box drivers. There’s no need for a third-party driver.

Instructions for uninstalling the driver:

Initializing: All MIDI Inputs

Most third-party drivers still work. But some are quite buggy, and always have been. I checked, and the midisports going back 20 years are all class-compliant. They say they work on macOS without a driver, so they will work on Windows without a driver. The driver was only to support multi-client, which we now have built-in. Unplug the midisport and completely uninstall the downloaded midisport driver from Settings > Apps > Installed apps Reboot. If the driver was completely uninstalled, the m…

Pete
Microsoft

[Psychlist1972]

Reboot your PC first. Then follow the instructions in my post here.

Pete
Microsoft

[nestling]

Thanks Sir. All M-Audio app and drivers extracted and Nuendo opens as per usual. Will log some hrs and see if further issues present. Huge relief. Any thoughts on my secure boot / security permission circus? or will that get rectified in pending updates?

[Psychlist1972]

No idea what happened there. Did you get any bios updates on the PC “System Firmware” or similar? Turn off TPM?

Maybe also make sure drives are healthy?

Pete
Microsoft