You are here
Home › Forum home › VirtualMIDISynth › Bug reports › Installer Requires You To Reboot Regardless of the Closed Blocking Processes ›Installer Requires You To Reboot Regardless of the Closed Blocking Processes
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!- Anonimo_LLopi
- Posts: 96
- Joined: October 14, 2016 - 03:20
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
The message "client version doesn't match with the server version" confirms that one of VirtualMIDISynth.dll (the driver component, in C:\Windows\System32 and C:\Windows\SysWOW64 folders) or VirtualMIDISynth.exe (the synth component, in C:\Program Files\VirtualMIDISynth) was in use by some program so it hasn't been updated and it will be at next reboot.
They both should be detected by setup procedure but somehow they're not.
We should try to know which file is in use and by whom.
Please try these steps:
- before starting the setup procedure, open C:\Windows\SysWOW64 then select VirtualMIDISynth.dll and try to rename it (append an .old suffix to its filename)
- you shouldn't be able to rename it and Windows will show an error message telling you that file is in use by program xxx
- if instead you were able to rename it, open C:\Windows\System32 and do the same on the other VirtualMIDISynth.dll file
- you shouldn't be able to rename it and Windows will show an error message telling you that file is in use by program xxx
- if you were able to rename both .dll files, try ti rename VirtualMIDISynth.exe in C:\Program Files\VirtualMIDISynth
Please report which of the above steps failed...
- Anonimo_LLopi
- Posts: 96
- Joined: October 14, 2016 - 03:20
coolsoft wrote:before starting the setup procedure, open C:\Windows\SysWOW64 then select VirtualMIDISynth.dll and try to rename it (append an .old suffix to its filename)
you shouldn't be able to rename it and Windows will show an error message telling you that file is in use by program xxx
At first the explorer would completely freeze wherever I tried this (I was erasing stuff so that might have caused it) but after several attempts windows asked me to give permission to "Operacion de archivos" (translated from spanish to "File operation" idk if that's the name in english) and when I clicked yes it renamed it succesfully to "VirtualMIDISynth.dll.old"
coolsoft wrote:if instead you were able to rename it, open C:\Windows\System32 and do the same on the other VirtualMIDISynth.dll file
you shouldn't be able to rename it and Windows will show an error message telling you that file is in use by program xxx
It also let me rename this one
coolsoft wrote:if you were able to rename both .dll files, try ti rename VirtualMIDISynth.exe in C:\Program Files\VirtualMIDISynth
No problems renaming this one either
After trying all this I installed the last beta and it didn't ask me to reset the computer though
Here, I've recorded the renaming process and the installation: https://www.youtube.com/watch?v=4-lhBXh6eyI&feature=youtu.be
Now I'm gonna reset my pc and I will install it again to see if it ask me to reset and if it does I will repeat those steps until it says which program it's blocking it
- Anonimo_LLopi
- Posts: 96
- Joined: October 14, 2016 - 03:20
Ok, I've reset the computer and I've tried to install virtual midi synth with it open,
after closing all the processes it asked me to close it still asked me to reset the computer,
so then I pressed "reset later" and then I renamed all the files you asked without problems renaming them
then I installed it again and voilà, now the installer doesn't ask me to reset the computer
Here's the whole test recorded: https://youtu.be/r3FeGSthdqw
At least we have found a temporal way to avoid reseting the computer
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Thanks for the recording, it really eased bug analisys.
It seems that, if a program is blocking one of the file, the NSIS reboot flag is initially set to TRUE but then it's not cleared after all of the programs were closed.
Will investigate on it and report the bug on NSIS forum.
PS: in the video I see one of the blocking processes called "OriginWebHelperService", but can't see its bitness. Is it an x86 or x64 process?
Task manager "details" does not show this info anymore but you can still check it in "processes" view like "(32 bit)".
- Anonimo_LLopi
- Posts: 96
- Joined: October 14, 2016 - 03:20
coolsoft wrote:PS: in the video I see one of the blocking processes called "OriginWebHelperService", but can't see its bitness. Is it an x86 or x64 process?
Task manager "details" does not show this info anymore but you can still check it in "processes" view like "(32 bit)".
32 bit
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Found the (subtle) bug in the setup procedure.
It was caused by VirtualMIDISynth.exe file: the reboot flag was set not only if the file was in use but if it existed (so, pratically, always...).
Please check the attached fixed one and report if it works as expected.
UPDATE: released version 2.3.2, attachment removed.
- Anonimo_LLopi
- Posts: 96
- Joined: October 14, 2016 - 03:20
coolsoft wrote:Found the (subtle) bug in the setup procedure.
It was caused by VirtualMIDISynth.exe file: the reboot flag was set not only if the file was in use but if it existed (so, pratically, always...).
Please check the attached fixed one and report if it works as expected.
Thanks, now it works perfectly and it doesn't ask for reset anymore after I close the blocking processes it asks me to close
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
Thanks for your feedback (and initial bug report).
Will publish it ASAP.
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal