You are here
Home › Forum home › VirtualMIDISynth › Bug reports › VirtualMIDISynth becomes unavailable and keeps prompting for reinstall (Win10-2004, build 10.0.19033) ›VirtualMIDISynth becomes unavailable and keeps prompting for reinstall (Win10-2004, build 10.0.19033)
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!Pages
- Sequenzzer
- Posts: 19
- Joined: June 3, 2017 - 02:22
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
Well, this is a quick-and-dirty workaround for you to quicky backup and restore MIDI registry configuration.
- download the attached ZIP file to a folder (I suggest a subfolder on your desktop)
- extract contained .bat files into the same folder
- now start VirtualMIDISynth and check that it reports the "driver missing" error
- allow VMS to fix the error (and reinstall driver)
- now immediately run midi-config-backup.bat to generate a backup of MIDI configuration (into files backup32.reg and backup64.reg)
- backup files can be restored manually or by running midi-config-restore.bat
WARNING: midi-config-backup.bat must be executed as administrator, so I suggest you to
- create a shortcut to midi-config-backup.bat on your desktop
- right click on the created shortcut
- select properties
- click Advanced
- check the Run as administrator checkbox
Now you can simply double-click on your desktop shortcut to restore a working MIDI config ;)
UPDATE 2020-05-30: wrapped paths into double quotes to make batch work in folders with spaces in path (thanks to @rookie_one) ;)
- Attachments (Only registered users)
- MIDI-Config-Workaround_v2.zip
- Sequenzzer
- Posts: 19
- Joined: June 3, 2017 - 02:22
Thank You Thank You THANK YOU! Works Like A Champ,and exactly what I was looking for in a workaround...
I very much appreciate your diligence,time,and effort looking into this issue,and coming up with this makeshift fix,sir....
Take Care and BE SAFE
Manik Groove
- Kyle Johnson
- Posts: 1
- Joined: May 21, 2020 - 19:02
One thing you could try is making a small service executable that runs with SYSTEM privileges that changes the registry value to the VMS driver. You can then watch the particular registry keys for changes using the RegNotifyChangeKeyValue() API call (see https://docs.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-regn...) for details.
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
@Kyle Johnson: that was the first idea I had; but it's like to fix something that continuously broke ;)
I need to find out what's causing that registry key to change and "convince" it to change it the way I like.
- rookie_one
- Posts: 1
- Joined: May 15, 2017 - 07:14
in that script, you might want to wrap the %~dp0\backup32.reg and %~dp0\backup64.reg lines in quotation marks.
If you don't, it might cause problems with users that put the scripts in a folder that have a space in the name
Also, I think switch pause for a timeout might be a better idea, since there might be some (like me) who will prefer to put the restore batch file in a scheduled task to run at startup. That way the task would not be kept in a running state
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
rookie_one wrote:in that script, you might want to wrap the %~dp0\backup32.reg and %~dp0\backup64.reg lines in quotation marks.
Good catch, thanks for your suggestion.
I've just updated it ;)
rookie_one wrote:Also, I think switch pause for a timeout might be a better idea, since there might be some (like me) who will prefer to put the restore batch file in a scheduled task to run at startup. That way the task would not be kept in a running state.
This won't be the "final fix" but just a workaround; most of the users will only double click it and I like they have an immediate feedback if something was wrong.
All power users (like you) are free to customize it as they like...
- stemarsi
- Posts: 3
- Joined: August 1, 2015 - 23:52
But the files must remain on the desktop, because I noticed that if you delete the files after doing the procedure, the error occurs again
- stemarsi
- Posts: 3
- Joined: August 1, 2015 - 23:52
Correction to me doesn't work with this bat file solution
- James Flasch
- Posts: 3
- Joined: May 31, 2020 - 21:17
I've had this problem since upgrading to Windows 10 Home (64 bit) 10.0.19041 last Wendesday.
Pages
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal