[SOLVED] 2.3.0 will not run at Windows10 x64 startup

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: 3
Joined: April 14, 2017 - 23:37
[SOLVED] 2.3.0 will not run at Windows10 x64 startup

(I love this program!)

OK, here's the problem...I am currently running Win10x64, version 1709, build 17093.1000, and I have noticed that the latest versions of CS VMS simply will not run when I boot Windows10 anymore--I *like* the Systray icon to run and appear when I boot Windows--that way I know the program is running and that I can change its config when I want.  It's always run in the Systray before (before the last couple of Win10x64 builds, that is)--and of course the option "start automatically at logon" is checked.  But in the last few Insider builds of Win10x64, this option no longer works. I don't know if it's because of a change in Win10x4 builds or a change in CS VMS (or maybe even both.)

I suspect it is something very simple because when I run CS VMS from a shortcut it runs fine, and the icon appears in the Systray, and all is well.  Just seems to be a problem when it boots with Windows10x64 now--in the last few builds--it simply won't run at startup as it has in the past.

Thanks!  Thought you should know.

Posts: 1536
Joined: March 25, 2012 - 01:19
Re: 2.3.0 will not run at Windows10 x64 startup

Well, just tested on my system (Win10 Pro x64 1709 build 16299.192) and it still works.
Sorry, I don't have a newer version like yours.

VMS adds a key in the registry here: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
please check if the key is present and its value is correct (must be the full path of VirtualMIDISynth.exe file, usually C:\Program files\VirtualMIDISynth\VirtualMIDISynth.exe).

While testing I've noticed one thing: the value of the above key is not wrapped into double quotes; this worked till now but, maybe, newer Win10 versions require it to be wrapped if the fullpath contains spaces.
To check if that's the difference, please try to wrap VMS value in double quotes and check if it works.

Posts: 3
Joined: April 14, 2017 - 23:37
Re: 2.3.0 will not run at Windows10 x64 startup
coolsoft wrote:

Well, just tested on my system (Win10 Pro x64 1709 build 16299.192) and it still works.
Sorry, I don't have a newer version like yours.

VMS adds a key in the registry here: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
please check if the key is present and its value is correct (must be the full path of VirtualMIDISynth.exe file, usually C:\Program files\VirtualMIDISynth\VirtualMIDISynth.exe).

While testing I've noticed one thing: the value of the above key is not wrapped into double quotes; this worked till now but, maybe, newer Win10 versions require it to be wrapped if the fullpath contains spaces.
To check if that's the difference, please try to wrap VMS value in double quotes and check if it works.

Wow...Thanks so much for answering so quickly!...;)  OK, it's a no-go, I'm afraid.  I noticed the lack of quotes for C:\Program files\VirtualMIDISynth\VirtualMIDISynth.exe and I added the "... "  as you suggested--made sense to me, too...But, no cigar...;)  Ah, well, It's not a major problem as the VMS is running like a clock in all other respects.  They will be releasing the official rs4 build for Win10x64 in a couple of months, I believe, so that hopefully will have this rectified.  Meanwhile, I will report this to Microsoft directly via their hub in all specifics.  Who knows...it could well be something to do with their newer AV stuff--which they are always tinkering with, it seems.  As of this build, for instance, the name has been changed officially from "Windows Defender" to "Windows Security" along with some other mostly cosmetic changes, it seems to me.  It's not that VMS is being picked up as a false positive or anything like that--it isn't--it's just that I wonder if something relative to "Windows security" is suppressing VMS at boot, now.  For whatever reason.  As I say, the program is perfect when run from the desktop shortcut, so I think it just about has to be something like that.

Thank you again for your response, and I cannot tell you how much I have enjoyed using your program!  Great stuff!  If I think of anything or discover anything relative I'll come back and let you know!  Have a great weekend--thanks again.

WaltC 

Posts: 1536
Joined: March 25, 2012 - 01:19
Re: 2.3.0 will not run at Windows10 x64 startup

As a workaround you could add a scheduled task and let it run at user logon; I know it's overcomplicated but it worths a try...

I'll leave the thread open, feel free to update it when you have any info.

Posts: 3
Joined: April 14, 2017 - 23:37
Re: 2.3.0 will not run at Windows10 x64 startup

SOLV-ED! (I would have edited my original post to place [Solved] at the end of my original title, but the site permissions here do not allow me to edit my original post!)

I'm very happy to say that this "issue" has been solv-ed, as my dear departed friend, Inspector Clouseau, would have no doubt put it...!

And so I was stumped until today when setting a mere file permission for something else reminded me of the unwillingness of Win10's latest beta builds to boot VMS.exe at startup!  Lo and behold, it was as simple as that!  Talk about the "obvious"...heh-heh...Captain Obvious, here, folks--that's me.    Or should I say, "Captain Oblivious"?  I wonder...And of course that was the very last thing that "dummy" here--that's me--thought about doing!  The very last thing...it should have been among the very first things I tried...(This seems ever the case, alas!)

Well, in my own pitiful defense I will only say that I had never before had to set file permissions for an executable to run at startup in a system in which I was already a principal administrator with all permissions bestowed.  Especially, this is the first time I've been required to do this for a VirtualMIDISynth.exe installation...;)     I suppose that Microsoft is simply tightening up the security chain in Win10 just a wee bit--which really can't be objectionable, imo!

All's well that ands well!

P.S. While I am thinking about it, my personal financial contribution to your endeavor is long overdue, so I will see if accomplishing that is something that is within my purview at the moment!...;) (Please remain patient as I stumble and bumble through.)  Additionally, I have been urging Microsoft to offer you a nice fat check for your program as they seem congenitally unable to see the very basic need inside Windows 10 for VirtualMIDISynth, and the company apparently cannot even summon the imagination to as much as conceive of the musical wonders that might come to be had Microsoft license to a program with the power and potential of VirtualMIDISynth!  But on second thought, after consideringing what Microsoft might actually do with VMS if they owned it--perhaps this marvelous program is already in the best possible hands--your own!...;)  Thanks again for your fine efforts!

Posts: 1536
Joined: March 25, 2012 - 01:19
Re: 2.3.0 will not run at Windows10 x64 startup
waltc wrote:
And so I was stumped until today when setting a mere file permission for something else reminded me of the unwillingness of Win10's latest beta builds to boot VMS.exe at startup!

Thanks for reporting it!

I've searched for official Microsoft documentation on it but haven't found anything (other than run as administrator issues).
If you have found this info on a forum, please post the relevant links here.

I'll keep an eye on this bug when next Windows 10 release will be released.