You are here
Home › Forum home › VirtualMIDISynth › Bug reports › No "VirtualMIDISynth #x" MIDI device ›No "VirtualMIDISynth #x" MIDI device
Please let our ADS show!
This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:
- disable your AdBlocker by adding CoolSoft website to whitelist
- give the proper cookie consent
- enable JavaScript for this website
This seconds wait is to let you update your browser configuration...
Ok, I've done the required changes... now show me your content!- Fierra2005
- Posts: 3
- Joined: December 2, 2017 - 19:35
- Ziya Mete Demircan
- Posts: 30
- Joined: April 19, 2017 - 08:14
Try to Uninstall and reinstall (VMS). Maybe this helps.
Maybe it can also be caused by: After some system updates (especially Windows 10) some problems may occur on some systems.
If this is not the case, you need to provide more detailed information.
What software are you using
How did you set up
What is your operating system and so on.
- Fierra2005
- Posts: 3
- Joined: December 2, 2017 - 19:35
Even if i reinstall, It gives this initialization error: Error reading configuration registry key: HLKM\SOFTWARE\CoolSoft VirtualMIDISynth\path. Blame Windows 10.
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
There's a well-known issue related to Windows "major version" updates that completely reset the multimedia layer and garble all of the configured devices.
It was already reported at 1703->1709 upgrade, and now is happening again at 1709-->1803...
I'm still investingating on it but, since it happens only at major upgrades, it's not so easy to reproduce.
I suggest you to remove + reinstall VMS (not reinstall but remove + install from scratch).
If it still doesn't work, try a manual reset then a reinstall (see this FAQ).
- Ziya Mete Demircan
- Posts: 30
- Joined: April 19, 2017 - 08:14
O.K.
I completely removed the software to solve the user's problem.
Then I started the experiment... then, I have some news :/
Unfortunately, v2.4.0 can not edit the registry on my machine. (Win7, 32bit)
If you first install prior version and then update it to v2.4.0, it works fine. (I tried with v2.0.0 => v2.4.0)
I don't know why.
(During all installation stages, antivirus/anti malware is disabled.)
Maybe this helps.
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Ziya Mete Demircan wrote:Unfortunately, v2.4.0 can not edit the registry on my machine. (Win7, 32bit)
No, it's not your machine.
I've found a bug in setup script that caused installation keys not be saved correctly on x86 systems.
It only happens on clean installations; systems where a previous version was already installed (in the same folder) worked with no errors (that't why I haven't found it previously).
Since version 2.5.0 is almost ready to be released, I'm not going to backport the fix to 2.4.x.
Please wait for 2.5.0-beta3 to be released there...
Thanks for your detailed reporting and tests ;)
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Just released version 2.4.1 that backports the setup procedure fix.
Check it out here: VirtualMIDISynth
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal