by kicking off a worker thread instead of blocking the main thread.

By default, Dorico initialises the eLicenser in an asynchronous fashion, i.e. We now know a bit more about this problem. I’m also happy to try beta versions of 6.12. I’m happy to reinstall 6.12 and collect debugging data if I’m told what is wanted. Hopefully the eLicenser team wil soon understand what is wrong with 6.12 on affected Windows systems and will be able to release a fix. However, many will not have realised, especially if Dorico is their only Steinberg product. I track eLicenser releases, so knew 6.12 had released and involved major internal restructuring, so would have gone for downgrading eLicenser to 6.11 even without Daniel’s post. It was unfortunate that a problematic version of eLicenser was the latest available when Dorico 3.5.10 was released, so it became the version bundled into the Dorico installer. It seems that this second attempt at releasing 6.12 has issues on some Windows systems, including yours and mine.

The first attempt at releasing 6.12 (which I think was Mac OS only) had to be withdrawn because it had issues. There was a lot of pressure to get eLicenser 6.12 released as 6.11 has major problems on recent versions of Mac OS. The eLicenser team are a separate part of Steinberg to the Dorico team, as I understand it. I’m a composer, not a computer whiz and after that supposedly nice upgrade from 3.5 to 3.5.1, I couldn’t get it to run! Why do you have to put your clients through such aggravation? Can’t you test your products before you release them? Dorico programmers ought to be ashamed of themselves releasing a product with such an obvious bug. I hate to sound negative, but I’ve spent so many hours trying to make 3.5.10 launch and only discovered how to fix it after figuring how to ask the right question on the forum. Yes, the downgrade worked, after uninstalling the most recent elicenser, restarting the computer, and installing the older one.

Download upgrade dorico 3.5 to 4