-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PKDownloadError error 8. Screenshot attached. #166
Comments
@sjha967 - This error can be caused by an unstable internet connection or DNS issues. Have you tried from another location or a hotspot? Have you tried running the installer locally itself? Also, be sure you have the actual macOS Installer and not a stub file. |
Thank you. I will try to connect from another location. I am just assure that this is not stub file. This is actual 12gb file. Just a question here: Why it's looking for DNS etc. If the macOS installer is there it should execute & get it installed. Isn't it ? |
Apple has a lot of checks built-in to the installer which is why it requires an internet connection along with downloading any firmware or other updates needed before proceeding with the upgrade. |
Thanks for passing this info
Regards,
Sumit Jha
…________________________________
From: Joshua Roskos <[email protected]>
Sent: Tuesday, December 29, 2020 11:11 PM
To: kc9wwh/macOSUpgrade <[email protected]>
Cc: sjha967 <[email protected]>; Mention <[email protected]>
Subject: Re: [kc9wwh/macOSUpgrade] PKDownloadError error 8. Screenshot attached. (#166)
Apple has a lot of checks built-in to the installer which is why it requires an internet connection along with downloading any firmware or other updates needed before proceeding with the upgrade.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#166 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIHBAWBAPOYTN5VMI5PEFETSXIID5ANCNFSM4VNDYVWQ>.
|
Shows PKDownloadError error 8 at preparing stage 7.4%. .
The text was updated successfully, but these errors were encountered: