Mixing
I can't install macOS Mojave because this copy of the Install macOS Mojave.app application is damaged
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I've been trying to upgrade my Mac from High Sierra to Mojave, but I keep getting the error below.
I rang Apple support and they told me to wait a while and try downloading it again from the App Store. I've now done this 2 times and continue to get the same error.
I spoke with Apple again and they said to wait a while and try installing it again. It's now been two days and I've rebooted my Mac a number of times, and have attempted installation many times.
I also tried installing all other software updates in case that was a factor. They all updated fine without any problem. The only thing I can't do is get the Mojave installer to run because it is apparently "damaged".
Maybe this is the universe telling me not to upgrade and I should give up, but now I'm here to ask you good folk.
Can someone kindly suggest other options for me?
mojave
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
3
down vote
favorite
I've been trying to upgrade my Mac from High Sierra to Mojave, but I keep getting the error below.
I rang Apple support and they told me to wait a while and try downloading it again from the App Store. I've now done this 2 times and continue to get the same error.
I spoke with Apple again and they said to wait a while and try installing it again. It's now been two days and I've rebooted my Mac a number of times, and have attempted installation many times.
I also tried installing all other software updates in case that was a factor. They all updated fine without any problem. The only thing I can't do is get the Mojave installer to run because it is apparently "damaged".
Maybe this is the universe telling me not to upgrade and I should give up, but now I'm here to ask you good folk.
Can someone kindly suggest other options for me?
mojave
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I've been trying to upgrade my Mac from High Sierra to Mojave, but I keep getting the error below.
I rang Apple support and they told me to wait a while and try downloading it again from the App Store. I've now done this 2 times and continue to get the same error.
I spoke with Apple again and they said to wait a while and try installing it again. It's now been two days and I've rebooted my Mac a number of times, and have attempted installation many times.
I also tried installing all other software updates in case that was a factor. They all updated fine without any problem. The only thing I can't do is get the Mojave installer to run because it is apparently "damaged".
Maybe this is the universe telling me not to upgrade and I should give up, but now I'm here to ask you good folk.
Can someone kindly suggest other options for me?
mojave
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I've been trying to upgrade my Mac from High Sierra to Mojave, but I keep getting the error below.
I rang Apple support and they told me to wait a while and try downloading it again from the App Store. I've now done this 2 times and continue to get the same error.
I spoke with Apple again and they said to wait a while and try installing it again. It's now been two days and I've rebooted my Mac a number of times, and have attempted installation many times.
I also tried installing all other software updates in case that was a factor. They all updated fine without any problem. The only thing I can't do is get the Mojave installer to run because it is apparently "damaged".
Maybe this is the universe telling me not to upgrade and I should give up, but now I'm here to ask you good folk.
Can someone kindly suggest other options for me?
mojave
mojave
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
user304149
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
user304149
162
asked 5 hours ago
user304149
162
162
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user304149 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago
add a comment |Â
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
The first thing I would try is resetting the System Management Controller (SMC) of your Mac.
Since you don't specify the model of Mac it's not easy for me to set out the steps you need to take, so I refer you instead to this Apple Knowledge Base article: How to reset the System Management Controller (SMC) on your Mac.
Make sure you read through the article and follow the steps for your Mac carefully.
answered 5 hours ago
Monomeeth♦
42.5k690131
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The first thing I would try is resetting the System Management Controller (SMC) of your Mac.
Since you don't specify the model of Mac it's not easy for me to set out the steps you need to take, so I refer you instead to this Apple Knowledge Base article: How to reset the System Management Controller (SMC) on your Mac.
Make sure you read through the article and follow the steps for your Mac carefully.
answered 5 hours ago
Monomeeth♦
42.5k690131
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
add a comment |Â
up vote
2
down vote
The first thing I would try is resetting the System Management Controller (SMC) of your Mac.
Since you don't specify the model of Mac it's not easy for me to set out the steps you need to take, so I refer you instead to this Apple Knowledge Base article: How to reset the System Management Controller (SMC) on your Mac.
Make sure you read through the article and follow the steps for your Mac carefully.
answered 5 hours ago
Monomeeth♦
42.5k690131
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The first thing I would try is resetting the System Management Controller (SMC) of your Mac.
Since you don't specify the model of Mac it's not easy for me to set out the steps you need to take, so I refer you instead to this Apple Knowledge Base article: How to reset the System Management Controller (SMC) on your Mac.
Make sure you read through the article and follow the steps for your Mac carefully.
answered 5 hours ago
Monomeeth♦
42.5k690131
The first thing I would try is resetting the System Management Controller (SMC) of your Mac.
Since you don't specify the model of Mac it's not easy for me to set out the steps you need to take, so I refer you instead to this Apple Knowledge Base article: How to reset the System Management Controller (SMC) on your Mac.
Make sure you read through the article and follow the steps for your Mac carefully.
answered 5 hours ago
Monomeeth♦
42.5k690131
answered 5 hours ago
Monomeeth♦
42.5k690131
answered 5 hours ago
Monomeeth♦
42.5k690131
answered 5 hours ago
Monomeeth♦
42.5k690131
42.5k690131
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
add a comment |Â
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
1
1
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
I am curious to know if this is resetting the SMC is just a general tip to fix things (akin to a reboot) or is there a specific "thing" that can be fixed by resetting SMC than can make the installer work?
– Nimesh Neema
4 hours ago
1
1
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
@NimeshNeema Well, resetting the SMC (like resetting the NVRAM) are both good general tips for fixing things, but in this case I've suggested this as I came across the exact same error three times in the past week (one on an iMac Pro, the other two were 2018 MacBook Pros), and after a process of elimination I found that resetting the SMC did the trick on all of them!
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
I admit on the face of it this solution doesn't make sense (as you probably know, the SMC is mainly about power, thermal, sensor and lighting management), so if anything resetting NVRAM would make more sense. However, my working theory is that all three Macs have T2 chips in them, so maybe resetting the SMC has something to do with that (far from proven obviously - 3 Macs is hardly a valid sample). But if I come across a few more examples I'll be letting Apple know (for what it's worth)! I hope the OP comes back and let's us know what Mac they have! :)
– Monomeeth♦
3 hours ago
add a comment |Â
user304149 is a new contributor. Be nice, and check out our Code of Conduct.
user304149 is a new contributor. Be nice, and check out our Code of Conduct.
user304149 is a new contributor. Be nice, and check out our Code of Conduct.
user304149 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f338008%2fi-cant-install-macos-mojave-because-this-copy-of-the-install-macos-mojave-app-a%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Firstly, welcome to Ask Different! :) I've added an answer for you, but if you get the chance it'd be good if you could clarify the exact model of Mac you're using - especially if my answer doesn't solve your problem.
– Monomeeth♦
5 hours ago