INTERACT FORUM

More => Old Versions => JRiver Media Center 22 for Windows => Topic started by: richard-ec2 on August 15, 2016, 02:44:04 pm

Title: MC22 won't open on start-up - publisher unknown
Post by: richard-ec2 on August 15, 2016, 02:44:04 pm
MC22 works fine on one of my Windows PCs but not on another. I have MC22 set to fire up automatically whenever the PC boots. However, MC22 refuses to start automatically  - instead, I get a pop-up asking if I want to allow this program from an unknown publisher to make changes to my PC. It starts up after I've answered this question but this is no use to me because the PC is running headless and without a keyboard.

It doesn't make a difference if I right-click on the app and run as administrator  - I still get the pop-up. I've tried reinstalling but I still get the unverified publisher message. What I don't understand is why the publisher is unverified - I didn't have this problem with MC21 on this or any other PC, where the publisher was always given as JRiver.

Any thoughts?
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: richard-ec2 on August 15, 2016, 04:16:04 pm
Here are a couple of pictures. Instead of MC22 opening up, I get this prompt:

(https://www.dropbox.com/s/ajxwl2c05fp7mpn/Prompt%202.jpg?raw=1)

But here's the interesting thing. The shortcut to MC22 has a tiny Windows Defender logo on it. You have to look closely but here it is:

(https://www.dropbox.com/s/pw92c63bakabu4n/Icon%20snip.PNG?raw=1)

What's going on? Anyone know?

 
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: JimH on August 15, 2016, 05:00:59 pm
It might be a problem with certificates on that machine.

What is the full version of MC?
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: richard-ec2 on August 16, 2016, 04:39:09 am
Thanks for answering - as I said, it's MC22 if that's what you mean.

Here is some more info. When I download MC22, and it asks me for permission to download, it correctly states that the publisher of the software is JRiver and that the publisher is verified. So, no problem at all there. But when the download is finished and I then install the program, every time I try to run it, I get the "unknown publisher" pop-up shown in my OP and it won't run until I've given actively given my permission. And as you can see, the MC22 shortcut has that weird Windows Defender logo superimposed upon it.
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: Hendrik on August 16, 2016, 04:46:58 am
The windows defender icon indicates that windows thinks it needs to run MC22 with admin rights, which is not something we require, so somewhere along the line it got flagged for that erroneously.

You can try checking the options of that shortcut and see if a compatibility mode or run as administrator is checked, and disable them.
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: JimH on August 16, 2016, 06:44:25 am
Under Help > About, you can see the full version. 22.0.10,  for example.
Title: Re: MC22 won't open on start-up - publisher unknown
Post by: richard-ec2 on August 16, 2016, 09:24:19 am
The windows defender icon indicates that windows thinks it needs to run MC22 with admin rights, which is not something we require, so somewhere along the line it got flagged for that erroneously.

You can try checking the options of that shortcut and see if a compatibility mode or run as administrator is checked, and disable them.

This proved very troublesome - nothing to do with JRiver - but yes, this was the fix. The run as administrator box was greyed out but yes, it was checked, and I eventually found I could uncheck it by going to change settings for all users first. Even then the shortcut icon and the exe itself still had the blue and yellow shield even after a reboot and the only way I could get rid of it was by completely uninstalling and reinstalling MC22. Previously, I had already uninstalled and reinstalled several times so it seems that Windows 10 was remembering the erroneous administrator setting from previous installs and applying to the new install every time - very strange. Anyway all fixed now so thank you very much indeed for your help.