INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Windows => Topic started by: dlptoo on July 01, 2019, 03:47:58 pm
-
I installed Media Center 25.0.71 a few minutes ago. When running Media Center for the first time, Norton Security indicated that the Media Center's digital signature wasn't valid. It did let me approve the program for access through the firewall, though, which I did, trusting that the executable really is from Media Center since it was downloaded from their site and they've always been trustworthy. :)
Is there truly something wrong with the executable? Should I uninstall what I installed and try redownloading and reinstalling?
Thanks!
-
By chance, is your system's clock set wrong?
-
I just checked the signature on the .71 files, and it seems fine to me. The clock being set wrong could possibly cause that, if its off by few days at least.
-
No, the computer's date/time are fine. They are set to update automatically to stay in sync, and that is working fine.
Looking in Program Files, what is the relationship between MC25.exe and Media Center 25.exe? MC25.exe has a digital signature; the other file doesn't.
I'll contact Norton tomorrow and see what they say. I noticed that the signature on MC25.exe uses SHA256. Perhaps Norton has problems with that for some reason (though, it shouldn't nowadays).
-
I have the 64 bit version of MC25.0.71 installed. I also run Norton Security, and have had no messages from it about JRiver.
Both executables you mentioned are signed, with a Date/Time stamp of "Saturday, 29 June 2019 1:15:xx AM", and they are signed using "Symantec Class 3 SHA256 Code Signing CA", so I don't think SHA256 would be a problem for Norton.
MC25.exe is a stub program used to pass commands to the real program, "Media Center 25.exe". See https://wiki.jriver.com/index.php/Media_Center_Core_Commands
You may have got a bad download, although it probably wouldn't work at all if you did. Download it again and re-install, and see if the files are now signed. Either that, or your Windows Region is unusual, so that the Date/Time is correct, but Windows is reporting something wrong.
Are you running the 64 or 32 bit version of MC?
-
I'm running the 32-bit version of the program. The Media Center 25.exe has no digital signature. So, it looks like the 64-bit file did get signed but the 32-bit file, at least in the package I downloaded, didn't get signed. The 32-bit Media Center 25.exe I have has a date/time stamp of 6/28/2019 8:14 AM.
I just uninstalled the 32-bit version and installed the 64-bit version instead. Both MC25.exe and Media Center 25.exe are now signed. Seems like the 32-bit download package needs to be updated with a signed Media Center 25.exe.
Thanks for your help! I'll go listen to music now... :)
-
There are actually complicated technical reasons why 32bit has some files not signed, however the lack of a signature should not cause your security applications to complain.
Most importantly the installer is always signed to ensure a proper clean version is being installed.
-
I'm not sure why Norton complained with the 32-bit version. It just said that the program was trying to go through the firewall and didn't have a valid digital signature. I can follow up with Norton if you want, but I don't know if it is worth it.
Norton has a tool named File Insight that tells the publisher of a file, a general idea of how many Norton users are using that file, and whether Norton thinks the file is "safe" or not. Norton gave both the 32-bit and 64-bit versions of the file a "Good" rating, apparently indicating that they trust that the file is from JRiver and that JRiver is trustworthy. File Insight said that hundreds of Norton users are using the latest version of the 64-bit file but only a few Norton users are using the 32-bit version. Perhaps nobody else ran into the issue (which would be odd; you'd think the experience with Norton would be the same across users) or just didn't decide to report it.
Anyway, I'm running fine with the 64-bit version. Unless you want me to follow up with Norton, I'll consider the issue resolved. It seems that most JRiver/Norton users are using the 64-bit version and wouldn't see the issue anyway.
Thanks for your help, everyone!