Dorico 6 fails to launch on Windows 11

Disabling an OS security feature because a software developer has been far too slow to fulfill their responsibilities (signing their software dlls or ensuring quality assurance in Windows updates) is absolutely unacceptable. You pay good money, only to end up with a program that won’t even launch. Dorico and WaveLab don’t work.

Hi. I find this statement inappropriate. I’ve purchased a product that doesn’t even run, and I’m just being told to wait—with no clear timeline. Who would buy a car that won’t even start? Dorico, WaveLab—everything is crashing or failing. Surely the quality of your software shouldn’t depend on how many other Windows machines it happens to be installed on. For the past month, I’ve had to use MuseScore for notation and other software for mastering instead of WaveLab. If a proper solution isn’t provided soon, I will have no choice but to switch to other products permanently. You can’t produce music with software that’s effectively dead.

Since MicroSoft’s Smart App Control utilizes both digital signatures and an AI reputation based algorithm to determine whether an app is safe to run, one cannot simply point to a digital signature as the culprit. It may very well be the case — but there should be a way that software vendors, like Steinberg, can vet new and updated software so that it can initially pass a reputation test in the absence of user data.
I worry that competitors of apps might create bots to flood negative reports that would eventually cause the AI to shut down the ability to run what is actually a legitimate, reliable, and safe application.

The products just run perfectly fine, it is the Microsoft cloud and AI stuff that believes it is bad software. Microsoft decided to implement a mechanism that is clearly stopping valid and legal software from working.

Why don’t you ask Microsoft why they install this software on your machine without your consent.

If you buy a car, park it in a garage and the parking attendant locks the garage, do you go to the car manufacturer complaining you can’t go out?

@GibsonSG, I’m very sorry for the inconvenience caused by this issue. We are working on a solution, but at the moment I can’t commit to a specific timeline for when we’ll be able to release updates with all components signed. Our products have a lot of shared components, so all those components need to be rebuilt, re-signed, integrated, and tested, and all our main applications then likewise have to go through the same process. As soon as I can provide an update, I’ll do so.

Not the first time, see: Dorico Pro 6 won't launch due to 'Qt6QmlMeta.dll' and 'Qt6QmlModels.dll'.

In Steinberg’s defense, there are a number of things which could keep this from popping up on their radar.

  • Enterprise-managed PCs typically have SAC disabled
  • If you have Developer Mode enabled, as most developers do, SAC is normally not enabled
  • If you have optional diagnostic data off, SAC is normally not enabled

As a developer, unless you are aware of the above, there’s a decent chance your CI/CD system doesn’t have Smart App Control enabled, and therefore you wouldn’t run into this.

In recent Windows 11 releases, if you are up to date on your updates, you can enable/disable Smart App Control without resetting your PC. In older builds of Windows 11, you had to reinstall Windows to turn it off.

From the FAQ, this is what Smart App Control is checking

What does untrusted mean?

When a developer creates an app, they are encouraged to “sign” the app using a digital certificate that verifies their identity, that the app is really published by them, and that the app hasn’t been tampered with by somebody else after the developer published it. You can think of it a bit like a painter signing a piece of art, except harder to fake.

Signing is one part of what can make an app trusted or untrusted. The other part is experience. Our intelligent cloud-powered security service sees a huge number of apps every day and uses that knowledge to predict if an app is safe or not safe — even apps we’ve never seen before. However, in some cases, the service is unable to make a confident prediction either way.

If the security service can’t make a confident prediction about the app, and the app doesn’t have a valid signature, it’s considered untrusted.

I’m an app developer, how can I get Smart App Control to not block my app?

The simple answer is, sign your app with a valid certificate.

Pete
Microsoft

Hi. I find this statement inappropriate. I’ve purchased a product that doesn’t even run, and I’m just being told to wait—with no clear timeline. Who would buy a car that won’t even start? Dorico, WaveLab—everything is crashing or failing. Surely the quality of your software shouldn’t depend on how many other Windows machines it happens to be installed on. For the past month, I’ve had to use MuseScore for notation and other software for mastering instead of WaveLab. If a proper solution isn’t provided soon, I will have no choice but to switch to other products permanently. You can’t produce music with software that’s effectively dead.

Hello. Aren’t companies informed in advance about major changes from Microsoft’s side, so that they can adapt their products accordingly? Take the transition from EWS to MS Graph, or the authentication changes, for example… I really hope you manage to get a handle on this situation; I’d hate to have to switch to alternatives, as these products have become quite dear to me over the years. You aren’t the only ones facing this, though—iZotope is dealing with similar issues. Heavyocity is too, though they did provide an update (for Microf Shimmer) within 24 hours of me submitting a support ticket. As of today, however, their portal is now being blocked by SAP. It seems the entire music industry has been caught napping.

I do not speak for Steinberg here.

This may actually be specific to the unsigned Qt (a third-party library for UI) DLLs. This is not the only musician product I’m seeing this in.

If something happened which caused those libraries to be untrusted by default (like a new exploit or a supply chain attack), this can happen, even after software leaves QA and is shipped to customers. I have no knowledge of such a thing happening, but it would explain why there are so many of these cropping up.

Qt doesn’t provide signed binaries themselves and they expect their customers to compile them from source in most cases (which gives each one a different thumbprint, even if the same source) and then sign them themselves, with their own certificates, which is a bit of a burden on the consumer.

The “correct” approach would be for Qt to provide signed binaries that they stand behind for their commercial customers. I have no idea if that is planned, but it’s becoming an increasing problem. They are requiring one company to sign another company’s code. That’s how some OSS works, but that’s a bit of a risk.

2026-11-17 Edit: Checked with Qt this morning. They do sign their commercial binaries appropriately. You only need to sign them yourself if you build from source.

I get the position you’re in here, and the upset, but it’s not as simple as described.

My recommendation to you, if you are on a current Windows 11 release and up to date with updates so you can set it back on afterwards without a reinstall, and you are not adventurous with what you install or allow to be installed, then temporarily disable SAC. Verify that it doesn’t say you will have to reinstall to change it before you do so, though.

Pete
Microsoft

Pete, Is there a way for Microsoft to include apps and services (dll’s, etc) in a vetted list so that SAC wouldn’t have to rely on a reputation analysis? It appears that much of this is done “in the cloud” (i.e., not on local machines) so, where there is not a valid signature, a vetted list could be checked. — Or does this open a back door to be hacked?
— Jim
(I appreciate you monitoring and participating in these discussions!)

As already mentioned, including by @Psychlist1972 , there is a solution. Deactivate Smart App Control, for now. If you believe in the use of SAC take it is a temporary solution and, as soon as the fix is distributed, you can reactivate it later.

Just blaming Steinberg here is the completely wrong approach, @dspreadbury answer is absolutely appropriate in this situation.

So you obviously already know that this is not a pure Steinberg issue.

Pete explained you the complex process of getting every single component signed within the Steinberg product palette, so I think you are a bit overreacting here.

This shouldn’t be a problem anymore, since KB5127936 (October 28, 2026) has been rolled out.

image

Well I’v got a Win 11 Home preinstalled on a Asus Laptop, and that KB5127936 does not appear in the list of availabele updates. So still I cannot use Dorico. Waiting seems a bad circle: how will window know that the libraries are runing securely on computers if it impedes to run them? Well, it’s above what you like or not like - if you like to disable SAC against MS recomendation, then face a laboursome reinstall… and run into the same problem with the next dorico update … or if you do not like that. Really: it is not possible that some steinberg-person calls a microsoft person and tells them: hey, here are some dll we guarantee to be safe to use - we would not distribute them otherwise - with their checksums and all, could you please tell your apparatus to let them pass? I insist that the situation is unpleasant.

This KB is just a correction for some installations, not all. You can check if it is relevant to you by just opening the Smart App Control Settings and try to deactivate it. As @Psychlist1972 mentioned, if it warns you about a required reinstall you don’t have the fix. Then you can decide if you want to continue or stop.

No, that is not the way SAC works. Every time the DLL’s are rebuilt they get a different checksum and therefore make them invalid for SAC. I guess the QT libraries are rebuilt by Steinberg, so that is no feasible approach.

Just to make it clear what SAC is, it is another component in Windows to check for maliciuous software and it does it by contacting some kind of cloud system. If you disable it you still have Windows Defender, which is a proven solution as a Antivirus product. So SAC is not the one and only component in Windows.

I have no idea, honestly. AV and other security areas are a bit of a black hole to me, and the info is kept close to the chest by those teams for fairly obvious reasons.

Feedback Hub provides a way to provide Smart App Control feedback about particular apps.

In reality, the “vetted list” is code signing that rolls up to a trusted authority. Why? Abused/compromised certificates can be revoked to minimize damage.

Pete
Microsoft

Not sure if that was a hypothetical “Why?” or “Why do you want to know? Either way, I probably don’t know enough about the system to make any determination!
I guess it’s a bit of a dilemma/paradox (or whatever one may call it); the easier an OS – and AV Software – make it for vendors to roll out new and updated applications, the easier it becomes for hackers.

I updated my post above. Qt does sign their commercial binaries. You only need to sign them yourself if you build from source. So they are doing the right thing there.

Pete
Microsoft

I don’t exactly consider disabling a security feature to be an acceptable workaround. Why should the customer, of all people, have to take on these security risks? When I buy a product, I’m not responsible for the manufacturing process, and I expect a product that works without having to take on any risks on my end. Otherwise, the product must be labeled accordingly. Warning: this only works under these restrictions. Here in Germany, there are regulations governing this. This takes product liability to the point of absurdity. If this catches on everywhere, well, good night. Microsoft also bears some of the blame here. These problems are now popping up everywhere with software that was still running just yesterday. It seems some restrictions have been tightened here. Introducing security features is a good thing, but suddenly crippling a huge amount of software in the process is unacceptable. This affects the entire software world—applications, games. It leads to users shutting down SAP. That accomplishes absolutely nothing. At the very least, I’d like to see the option for users to mark individual files as safe until an update is available. After all, people have to make a living. The whole thing feels like a “take it or leave it” situation.
“I think you’re overreacting a bit here.” Full-time professionals will judge this differently. Let’s hope they finally roll out a fix soon :slight_smile:

Would be interesting to see the regulations that govern this specific case, I can read German.

Ok, so did you inform Microsoft about this as well? Or are you just complaining here in the Steinberg forum?

So you are saying I’m not a “full-time professional” and therefore can not judge this issue?

For me there is no more need to continue this discussion with you, I’m out here.