Ventura install errors. Log shows, "pkgdmg validation has failed", "pkgdmg checksum does not match"

Specs:

macbook 16-inch 2019 running fresh 10.15.7 (i9/64g ram)


Issue:

Ventura install and upgrade fails and isn't corrected via the standard troubleshooting steps. It will recover into Catalina but wont let me accept the user agreement with an icloud account provided so i need to skip that in order for it to install correctly. From there, when I try the ventura upgrade it fails and the logs show several errors. One chunk of the logs seem the most interesting however I can not find any information regarding whether this is normal. Here is a dump of those lines.


 osinstallersetupd[622]: : 047a2000 : Failed to create systemVersionDict
 osinstallersetupd[622]: : 047a2000 : Failed to get currentInstalledBuild. Assuming clean install
osinstallersetupd[622]: : 047a2000 : Failed to create systemVersionDict
 osinstallersetupd[622]: : 047a2000 : Failed to get currentInstalledBuild
 osinstallersetupd[622]: Forcing MSU springboard for target: disk1s1 (Error Domain=com.apple.OSInstallerSetup.error Code=275 "The target must run through the installer springboard." UserInfo={NSLocalizedDescription=The target must run through the installer springboard.})
 osinstallersetupd[622]: Verify calculated time estimate: 64.316766 for /Applications/Install macOS Ventura.app/Contents/SharedSupport/SharedSupport.dmg
 osinstallersetupd[622]: Forcing MSU springboard for target: disk1s1
 osinstallersetupd[622]: Verify calculated time estimate: 39.943364 for /Applications/Install macOS Ventura.app/Contents/SharedSupport/SharedSupport.dmg



The actual crash finally occurs with this error. The (seeming) smoking gun


 osinstallersetupd[622]: pkgdmg checksum does not match, possible corruption.
 osinstallersetupd[622]: pkgdmg validation has failed.
 osinstallersetupd[622]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=255 "Installation cannot proceed because the installer is damaged." UserInfo={NSLocalizedDescription=Installation cannot proceed because the installer is damaged., NSLocalizedRecoverySuggestion=Redownload the installer and try again.}


What I've tried

  1. Boot into recovery mode, reinstalled via existing recovery UI.
  2. Removed all volumes and partitions on the internal SSD, reformatted GPT map with AFP.
  3. Used the network recovery mode to install the default system (catalina). This works fine. It also creates a "Data" partition in addition to the root disk.
  4. Preformed the automatic updates for a fresh install.
  • I have also repeated these steps and gone straight into a ventura install by way of the app store download (before it's had a chance to do the default updates)
  1. Booted into safe mode and attempted the update
  2. Using the softwareupdate cli, I have downloaded and created ventura install media and booted straight into that installer. This fails for an unknown reason as i haven't dumped the logs there (yet, this will be on my next attempt)
  3. I have reset the PRAM and attempted, both fresh and via the installer
  4. I have re-downloaded the installer and created a USB 3 times - and on different machines
  5. I have manually removed the automatic downloaded updated to have it pull a fresh Ventura installer.
  6. I have tried both logged into my icloud and without
  7. I have booted as a target and reformatted via a second mac.
  8. I have booted as a target and ran spinrite, and memtest. No issues.


Other info

I know that there can be issues with the signing certificates for updates, and i don't think there's a relation, but the error that the checksum doesn't match - while not a signing thing give me vibes of something along those lines for some reason... just an aside. Also, I am using a different account than was originally used when I received the machine (and had been used up until this reinstall), but I don't think this would matter once the drive has been reformatted, the "find my" security things disabled / machine removed from accounts devices. Again, thought i would mention it in case. I will log into that other account and try on one of the next iteration / attempt / last ditch efforts to reinstall but that seems so unlikely to be the issue... who knows though, we are talking about an apple product.


Finally, I do have a timemachine backup but I really don't want to use it. In the end I will try that. I reinstalled the system to wipe it clean and start fresh. I recognize that i can restore from backup and then reinstall and I will attempt to do that but I really would love to know why I'm not able to get a totally clean install downloaded and installed... I would just use catalina but there is software for work that wont run on Catalina.


If anyone might have any more information, suggestions for debugging, or resources that would be awesome.

Thanks ahead of time.

I can provide the complete error dump or any other info if that would be helpful.


MacBook Pro 16″

Posted on May 24, 2023 8:37 AM

Reply
Question marked as Top-ranking reply

Posted on May 26, 2023 10:07 AM

TLDR; Network / Firewall issue.


Thank you for that info @HWTech. I had no idea about the Firmware restore. Why this did not show up in a search over the literal days of troubleshooting, I have no clue.


I was finally able to figure out the issue. It ended up being related to my firewall. When I first ran into this issue the firewall was my first thought so i disabled it with the main kill switch to turn it into a router only. Maybe it was a rule blocking some server or it was manipulating packets so I disabled it completely... at least I thought. I marked it off my list of potential culprits and moved along. It wasn't until after I picked up my loaner laptop from work and experienced the same issue that it became crystal clear it was something on my end... The only thing that could possibly be in the way: my network. I removed my firewall from the equation entirely and plugged directly into the ISP's router. It worked. I then dug in further and discovered that disabling the firewall with the cli does not disable the firewall until you manually re-enable it. Any other change to the firewall (like being extra cautious and disabling services in addition to the whole thing) would re-enable it... SMH. I then found the rule that blocked the apple server that either the checksum comes from or i dont know... They use that same server for analytics and i'm not interested in them collecting who knows from me so it's on my naughty list. Anyway, i hope this helps someone else. Especially @HWTech's info! Thanks again for that. Cheers.



As an aside, I have been hacking on apple computers for decades, patching kernals to run open source systems on their hardware, and have reinstalled OS X prob 100 times. I have never (as far as i can recall) come across this feature of firmware restoration like this. I digress

Similar questions

2 replies
Question marked as Top-ranking reply

May 26, 2023 10:07 AM in response to HWTech

TLDR; Network / Firewall issue.


Thank you for that info @HWTech. I had no idea about the Firmware restore. Why this did not show up in a search over the literal days of troubleshooting, I have no clue.


I was finally able to figure out the issue. It ended up being related to my firewall. When I first ran into this issue the firewall was my first thought so i disabled it with the main kill switch to turn it into a router only. Maybe it was a rule blocking some server or it was manipulating packets so I disabled it completely... at least I thought. I marked it off my list of potential culprits and moved along. It wasn't until after I picked up my loaner laptop from work and experienced the same issue that it became crystal clear it was something on my end... The only thing that could possibly be in the way: my network. I removed my firewall from the equation entirely and plugged directly into the ISP's router. It worked. I then dug in further and discovered that disabling the firewall with the cli does not disable the firewall until you manually re-enable it. Any other change to the firewall (like being extra cautious and disabling services in addition to the whole thing) would re-enable it... SMH. I then found the rule that blocked the apple server that either the checksum comes from or i dont know... They use that same server for analytics and i'm not interested in them collecting who knows from me so it's on my naughty list. Anyway, i hope this helps someone else. Especially @HWTech's info! Thanks again for that. Cheers.



As an aside, I have been hacking on apple computers for decades, patching kernals to run open source systems on their hardware, and have reinstalled OS X prob 100 times. I have never (as far as i can recall) come across this feature of firmware restoration like this. I digress

May 25, 2023 8:42 PM in response to _rimraf

Sounds like a hardware failure with the Logic Board. The 2019 models seem to have a much higher rate of Logic Board failures than any other model, especially with the 16" 2019 model. The best you can do now is to try a firmware "Restore" which will reset the T2 chip & firmware & properly partition & format the internal SSD. Afterwards you will need to use Internet Recovery Mode to reinstall macOS since booting from USB won't be possible until you configure a macOS user on the new OS. I thought this "Restore" firmware process on some Intel Macs may have pushed a clean copy of macOS onto the internal SSD in a few cases, but I am not certain (Apple's documentation says that only occurs with Apple Silicon Macs, but I think I had a couple Intel Macs where this occurred since the process was very quick).


If a firmware "Restore" has the same issues with Ventura, then you will need to have the laptop repaired (most likely a Logic Board replacement).


I'm fairly certain the Logic Board will need to be replaced.


You can try running the Apple Diagnostics and hope the diagnostic fails with a memory related error, but it is rare for the diagnostics to actually report any issues. Since a clean install of macOS Ventura is failing to finish installing, then Apple may elect to replace the Logic Board, but a failing diagnostic error code would definitely help convince Apple of a hardware issue.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Ventura install errors. Log shows, "pkgdmg validation has failed", "pkgdmg checksum does not match"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.