You are here
Home › Forum home › VirtualMIDISynth › Bug reports › Program ignores 'never' selection for scanning for updates ›Program ignores 'never' selection for scanning for updates
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!- Drew
- Anonymous user
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Actually if an update has been found (but not yet installed), its version is stored and the whole check-new-version activities are skipped (because it already know that there's something new to install). Never setting will only skip the check but not the notification.
After reading your description (and use case) I agree that never should skip everything, not only the check task.
Will fix it in next version (this is a reason to update :)).
Meanwhile you can reset the updated status:
- close VirtualMIDISynth
- open VirtualMIDISynth.conf file with a text editor (you'll find it in C:\Windows\SysWOW64\VirtualMIDISynth folder for VMS1, in C:\Program files\VirtualMIDISynth for VMS2)
- remove (or comment by prepending them with a semicolon) the items LastCheck, LastVersionFound and LastVersionURL
- restart VirtualMIDISynth
Please confirm if the workaround works...
- TMN
- Anonymous user
I also encountered this issue. I have check for updates set to 'never', but I got a notification for 2.0.1.0.
After I updated but didn't reboot, the software notifies me every time it starts for new version.
I tried removing the LastCheck, LastVersionFound and LastVersionURL from VirtualMIDISynth.conf but it just came back. Removing the other lines just empty "LastCheck=" and "LastNotify=" lines back in the conf file, and notifications continue.
Blocking VirtualMIDISynth.exe in the Windows firewall stops the notifications.
- Drew
- Anonymous user
I ran into the same effect, simply commenting the lines out only causes the program to update the .conf file with new lines and continued notices. However what did work was commenting out those lines and setting the .conf file to 'read only'. Did that, restarted, and no notification pop-ups.
I'll keep an eye out for the updated release, thanks for responding so quickly!
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
The update is coming, stay tuned ;)
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal