Macbook pro 2017 won't install Ventura

My Macbook pro 2017 (2,3 GHz Intel Core i5, 16 GB, 499 GB SSD, of which 439 GB free) runs actually under "High Sierra". I tried to install Ventura. The download from the App Store worked fine, the I launched the macos Ventura Installer. . . which took some time to finish; end when it was finished, the OS was ... "High Sierra".

What went wrong? Can somebody give me a hint what i did wrong, or what i should do ??

I add a few lines form the Installer Log; perhaps this gives a clue...

Thanks for every advice!

Here from the Installer Log :

Feb 21 23:11:17 Priscas-MBP-2 softwareupdate_notify_agent[587]: appstoreupdateagent notified

Feb 21 23:11:17 Priscas-MBP-2 softwareupdate_notify_agent[587]: AssertionMgr: Cancel com.apple.softwareupdate.NotifyAgentAssertion-LoginDone assertion for pid 587, id 0x80FB

Feb 21 23:11:37 Priscas-MBP-2 osinstallersetupd[478]: OSISPredicateUpdateProduct: Incompatible Apps List: No product found

Feb 21 23:11:37 Priscas-MBP-2 osinstallersetupd[478]: Failed to find incompatible apps list on software update catalog

Feb 21 23:13:09 Priscas-MBP-2 osinstallersetupd[478]: disk3s1 is not convertible to APFS: You may not install to this volume because it cannot be converted to Apple File System (APFS).

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdated[202]: BackgroundActivity: Starting Background Check Activity

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdated[202]: BackgroundActions: Automatic check parameters: autoDownload=YES, autoConfigData=YES, autoCriticalInstall=YES

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdated[202]: SoftwareUpdate: Fired early. Next check=22/02/2024 20:50 (interval=86280.000000, A/C=YES)

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdated[202]: BackgroundActivity: Finished Background Check Activity

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdate_notify_agent[587]: Handling notification event: UpdatesAvailable

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdate_notify_agent[587]: AssertionMgr: Take com.apple.softwareupdate.NotifyAgentAssertion-UpdatesAvailable assertion with type BackgroundTask for pid 587, id 0x815B

Feb 22 17:26:38 Priscas-MacBook-Pro-2 softwareupdate_notify_agent[587]: Waiting 60 seconds before sending the notification to App Store

Feb 22 17:27:40 Priscas-MBP-2 softwareupdate_notify_agent[587]: Notifying with params: {

SoftwareUpdateCount = 0;

SoftwareUpdatesAvailable = 0;

}

Feb 22 17:27:40 Priscas-MBP-2 softwareupdate_notify_agent[587]: appstoreupdateagent notified

Feb 22 17:27:40 Priscas-MBP-2 softwareupdate_notify_agent[587]: AssertionMgr: Cancel com.apple.softwareupdate.NotifyAgentAssertion-UpdatesAvailable assertion for pid 587, id 0x815B

Feb 22 18:00:43 Priscas-MBP-2 system_installd[636]: PackageKit: ----- Begin install -----

Feb 22 18:00:58 Priscas-MBP-2 system_installd[636]: PackageKit: ensureRecoveryBooter started.

Feb 22 18:01:02 Priscas-MBP-2 system_installd[636]: PackageKit: ensureRecoveryBooter succeeded

Feb 22 18:01:03 Priscas-MBP-2 system_installd[636]: PackageKit: ----- End install -----

MacBook Pro 13″

Posted on Feb 22, 2024 9:22 AM

Top-ranking reply

HWTech

Community+ 2026

Level 9

72,198 points

Posted on Feb 22, 2024 9:59 AM

Feb 21 23:13:09 Priscas-MBP-2 osinstallersetupd[478]: disk3s1 is not convertible to APFS: You may not install to this volume because it cannot be converted to Apple File System (APFS).

What file system is on the boot drive? According to this snippet of the log you posted, it is saying that the boot volume is not using APFS and it cannot be converted. The macOS installers used to automatically convert an HFS+ volume (aka MacOS Extended filesystem), but later installers stopped doing the conversion automatically.

If the boot volume is MacOS Extended (Journaled), then you can try to manually convert it to the APFS file system by using Disk Utility (there is a "Convert to APFS" option on one of Disk Utility's menus....not sure if you select the physical drive or the volume/partition...default name is "Macintosh HD"). I believe you may need to boot from either a Recovery Mode or a bootable macOS USB installer to attempt the conversion process. I highly recommend you create a bootable macOS 13.x Ventura USB installer now while you still can just in case you have issues using Internet Recovery Mode (Command + Option + R) so that you have more options available in case something goes wrong.

I also highly recommend to make sure you have good backups before doing anything else. While the conversion process should not destroy any data, if the process fails, then it could leave the internal drive in an unbootable state.

View in context

Macbook pro 2017 won't install Ventura

Similar questions