You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
After upgrading a MacOS 15.4.0 guest to 15.4.1 with file vault enabled, the system reboots to the login screen. When I log in, the screen gets black, reboots and reverts to 15.4.0. After a successful login, it creates a problem report (see below) and offers again to install 15.4.1. Multiple tries result in the same problem. Upgrading via recovery re-install results in the same problem.
The only way to upgrade successfully seems to be disable File Vault before doing the upgrade.
PS
I already had a similar problem when upgrading to 15.4, but back then the system did not revert to 15.3.x, but instead just rebooted upon login every time. I solved the problem by booting into recovery mode and reinstall MacOS.
The text was updated successfully, but these errors were encountered:
sagischwarz
changed the title
Crash and revert to old version after update to MacOS 15.4.1
Crash and revert to old version after update to MacOS 15.4.1 with File Vault enabled
Apr 17, 2025
Describe the issue
After upgrading a MacOS 15.4.0 guest to 15.4.1 with file vault enabled, the system reboots to the login screen. When I log in, the screen gets black, reboots and reverts to 15.4.0. After a successful login, it creates a problem report (see below) and offers again to install 15.4.1. Multiple tries result in the same problem. Upgrading via recovery re-install results in the same problem.
The only way to upgrade successfully seems to be disable File Vault before doing the upgrade.
Configuration
MacOS Guest Problem Report
Expand
Upload VM
config.plist.zip
PS
I already had a similar problem when upgrading to 15.4, but back then the system did not revert to 15.3.x, but instead just rebooted upon login every time. I solved the problem by booting into recovery mode and reinstall MacOS.
The text was updated successfully, but these errors were encountered: