Universal Media Server.app is damaged and can't be opened... 10.11.4

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
darkprinc
Posts: 4
Joined: Wed Mar 23, 2016 7:14 pm

Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by darkprinc »

"Universal Media Server.app is damaged and can't be opened. You should move it to the trash."

this is the error i'm receving since updating my mac to the latest update. 10.11.4
i've tried every version bacwards from 6.2.0-Java 7 and 8 to version UMS-5.5.0-Java8 that works(it is not showing "damaged" error)
Befour updating my mac i had UMS-6.0.0-Java8. It worked fine.

Any ideas what could be the problem here?
snakebyte
Posts: 67
Joined: Thu Oct 24, 2013 4:15 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by snakebyte »

Hi there,

there is no real problem except your Mac is giving this warning as the developers are not recognised as trustworthy by Apple and the use of the UMS is at your own risk regarding to them.

It's one of the very few things that is irritating me about Apple as I receive this message for a few years now , ever since the sandboxing has started.
I get this message everytime my Mac restarts and I have to restart UMS.
The first few times I also trashed UMS and re-downloaded and reinstalled it just to find out the same as you have that this does not do the trick.
Keeping the file and starting the UMS instead and ignoring the warning from my Mac does do the trick and UMS seems not to be broken at all and just works as we expect it to be.

As you fully trust the developers from this great program as I do, and up until now they have not give me a reason not to, you can keep using it.

Good luck,

Greetsssssssssss Snakebyte
darkprinc
Posts: 4
Joined: Wed Mar 23, 2016 7:14 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by darkprinc »

so how can I start it if it automaticaly call's it damaged?

how do you start it?
darkprinc
Posts: 4
Joined: Wed Mar 23, 2016 7:14 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by darkprinc »

Ok I just figured it out.
Thx for helping
snakebyte
Posts: 67
Joined: Thu Oct 24, 2013 4:15 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by snakebyte »

Your Welcome :D :D :D :D
[email protected]
Posts: 1
Joined: Wed Dec 21, 2016 3:13 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by [email protected] »

Having the same issue after upgrading to 10.12.2
I am happy that you figured it out, could you please list how you did it?
Thanks in Advance
amkaplan
Posts: 3
Joined: Thu Jul 25, 2013 5:57 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by amkaplan »

I'm running 10.12.2, and having this same issue with the new archive 6.5.3. I tried the control-click trick to bypass security to open the archive, but still get the same alert, and still can't open the archive.

Any help would be appreciated.

Allan
amkaplan
Posts: 3
Joined: Thu Jul 25, 2013 5:57 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by amkaplan »

Hi,

I'm still running into this problem. Again, using control-click to bypass the security to open the archive still elicits the warning "“Universal Media Server” is damaged and can’t be opened. You should move it to the Trash." My only options are to trash it or cancel.

Anyone out there have a top on how to get this to work?

Thanks,

Allan
kwinnevesj
Posts: 3
Joined: Fri Feb 20, 2015 9:26 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by kwinnevesj »

Hi

I have the same problem and no solution.

Anyone, knows what to do. I am using a macbook running sierra

Help, Peter
David Fredette
Posts: 1
Joined: Sun Feb 19, 2017 2:18 pm

Re: Universal Media Server.app is damaged and can't be opened... 10.11.4

Post by David Fredette »

I found a solution that works for me.

Open a Terminal session and write : sudo spctl --master-disable
Then reopen the app. Enjoy!
Post Reply