Miroslav Philharmonik CE (1) Registry Error

[hungrysponge]

I have owned Miroslav Philharmonik CE (the first one) for many years and have had no problem with it. I used it extensively on a recent project.

Windows recently updated. The day before the update, Miroslav loaded properly. The day after the update, I am now getting an error message every time it tries to load:
Registry error
Please ensure this product has been installed properly

I get this message when trying to load it into my DAW and when using the stand-alone version.

I first tried repairing the installation. No luck. Then I uninstalled and reinstalled Miroslav. I still get the same message.

Is there any solution to this problem?

TIA,
Steve.

DAW: Reaper v6.51/win64 rev 1cca36 (Mar 5 2022)
OS: Windows 10 Home v21H1 build 19043.1645

[DarkStar]

As this is primarily a user to user forum, not official Technical Support, other users may chip in. But please remember that the same symptoms do not necessarily mean the same problem.

Meanwhile, the best thing to do is contact Support, via here. If Searching the FAQs does not help there is a red button link to the Technical Support form, for some one to one investigation and help. Response time aims to be within 2 working days (US (East Coast) Business hours, generally), but in the current circumstances please allow some more time.

And, to help others who run into a similar problem, please let us know what you did to resolve the problem. Please do not quote directly any correspondence from Support, as that may apply only to your particular circumstances and may lead others down the wrong track.

[hungrysponge]

No real solution was offered to actually fix the problem.

A workaround was offered, though: I need to run my DAW and the stand-alone program in Administrator Mode from now on to get it to work.

Well, at least I can use it again.

Barely satisfied,
-- Steve

[DarkStar]

Ah, I did not notice the (1) in your post.

The first generation of Miroslav Philharmonik uses files in folders and Registry Keys that are more protected in Windows 7 (or even Vista?) onwards. But it seems odd that it ran OK in Windows 10 before the latest update. I would have thought that the problem would show up in Windows 10 before.

Anyway I am glad that you have got it sorted out.