HQPlayer License Key Invalid for WS 2016 Core

[Darryl R]

Hello,

 

HQPlayer will not accept my valid Windows license key in WS 2016 core mode.  It installed fine in Windows 2016 Desktop Experience, but not not in core.  The license key is long, and I not only checked it many times but used Notepad to copy and paste without success.  Any ideas/help appreciated.

[Darryl R]

Jussi,

 

Thanks for the kind contact.  So the issue is not the player itself, but validation of the license key.  This works fine in WS 2012R2 and 2016 (Desktop Experience), but not in 2016 Core.  Unfortunately MS removed the ability to switch between Desktop and Core in 2016, so the installs must be done in Core directly.

[Darryl R]

All,

 

Forget about HQPlayer in WS 2016 Core.  The author refuses to support any WS edition.

[Darryl R]

For the record, I finally got the license key to validate.  I played around with some things, but in the end it may have been a glitch in the license validation service.  Either way, it's nice to have this in a server core -- much improved bass, quieter background.

[ms012873]

Darryl R:

Could you kindly describe what steps you took to get the license key to validate? I am experiencing a similar problem

with  JRiver Media Center running on Win Server 2016 in Core.

 

Thanks

[Darryl R]

I don't remember exactly what I did, but what I concluded was relevant was to restart the system and try again the next day.  Jussi has since told me he has had other problems with his third-party Windows licensing module, at the root of the problems with the Windows 10 "creator's update", and that he had plans to replace it with his own.  Hard to imagine the same thing is happening with JRMC.

[ms012873]

Thanks for your prompt reply; I agree that is unrelated to my problems with JRiver.  

[miguelito]

Windows os systems must be at least 5 yrs old for any non-microsoft license to work. You're stuck with 2012.

[Darryl R]

33 minutes ago, miguelito said:

Windows os systems must be at least 5 yrs old for any non-microsoft license to work. You're stuck with 2012.

 

This statement makes absolutely no sense.

[miguelito]

2 hours ago, Darryl R said:

3 hours ago, miguelito said:

Windows os systems must be at least 5 yrs old for any non-microsoft license to work. You're stuck with 2012.

 

This statement makes absolutely no sense.

It was meant as a joke.