Virtual Midi Synth will not start automatically

It seems you're using an AdBlocker or JavaScript is disabled!

This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).

This 10 seconds wait is to let you update your AdBlocker whitelist...

Got it, show me the content...
Please enable JavaScript!
Posts: 4
Joined: December 17, 2015 - 18:17
Virtual Midi Synth will not start automatically

Don't know since when, but starting Cakewalk, no VMS is present. So I installed v.2.7.3 again. By installing, the two registry entries (......\Drivers32) are present: midi1 shows VirtualMidiSynth. When I reboot my system, I loss these entries.

The same happens with your latest version 2.8.0. I must execute VirtualMidiSynth.exe again (that popup's a window -> Midi driver is not correctly installed. Want to fix it. BEWARE admin privileges are needed). Doing this brings back the registry entries.

Uninstalling / Installing without AntiVir Software did not help. Uninstalling / Installing with admin preivileges did not help. Changed CompatibilityMode to "Run this program as administrator" did not help.

What can I do to fix this problem ? Please help.

Kind Regard

Dieter

Attachments (Only registered users)
VirtualMIDISynthconf.txt
Posts: 1542
Joined: March 25, 2012 - 01:19
Re: Virtual Midi Synth will not start automatically
Cid wrote:
By installing, the two registry entries (......\Drivers32) are present: midi1 shows VirtualMidiSynth. When I reboot my system, I loss these entries.

It seems that you've got something that resets those keys upon reboot.

Cid wrote:
I must execute VirtualMidiSynth.exe again (that popup's a window -> Midi driver is not correctly installed. Want to fix it. BEWARE admin privileges are needed). Doing this brings back the registry entries.

That feature was added to help people experiencing the same behaviour as your.

The threads below are the ones that lead me to deciding to add such feature:
https://coolsoft.altervista.org/en/forum/thread/773
https://coolsoft.altervista.org/en/forum/thread/775
https://coolsoft.altervista.org/en/forum/post/2709#post2709

Have a look at them, maybe you'll find something similar to your configuration.

The first thing that comes to my mind is: open registry (once the key has been fized) and change the permissions of the Drivers32 key such as no-one can change it, then reboot.
This way, if you're lucky, some program will comply because it won't be able to change keys and you'll find out who's resetting them...