Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Fresh install: „The version of macOS … needs to be reinstalled“

S

Sidetrax

macrumors newbie
Original poster
Apr 7, 2025
2
0
Hi,

Today I tried doing a fresh install of macOS 15.4 (had it installed before without problems) on my MacBook Pro M1.
First, I created a bootable USB drive via terminal, as I did before with all my fresh installs.
Then I went into recovery mode and erased the SSD („erase and restart“).
After restarting and activating the MacBook I installed via USB drive.

When restarting I get „Choose Startup Disk“ window, which I never had before.
Selecting the Macintosh HD as startup disk I get the error „The version of macOS on the selected disk needs to be reinstalled. Reinstall macOS or select another startup disk.“

I tried the same procedure without USB drive using the online recovery method. Same result.

As mentioned, this is not my first time, but maybe I missed something.

Thank you for your help.
 

Attachments

  • image.jpg
    image.jpg
    506.3 KB · Views: 111
Allot of users with m1 have KP updating to 15.4. The usb installing method experience the same issue. with DFU restore it update's directly to 15.4 without issues.
 
I had this issue and stumbled across this thread. @MobyOne thank you so much! I was able to revive my M1 Max with a 15.3.2 installer.

I wonder what is wrong with 15.4? I can't even update from 15.3.2 I receive the Installation failed an error occurred while installing the selected updates error. I'm just going to wait for 15.5 and see what happens.
 
Crickster said:
I had this issue and stumbled across this thread. MobyOne thank you so much! I was able to revive my M1 Max with a 15.3.2 installer.

I wonder what is wrong with 15.4? I can't even update from 15.3.2 I receive the Installation failed an error occurred while installing the selected updates error. I'm just going to wait for 15.5 and see what happens.
Click to expand...
Not sure. It maybe possible to update in safe mode. Can you check?. I have m4 air and restored my m1 mini in DFU. Otherwise wait for 15.5
 
Last edited:
MobyOne said:
Not sure. It maybe possible to update in safe mode. Can you check?. I have m4 air and restored my m1 mini in DFU. Otherwise wait for 15.5
Click to expand...
I tried it in safe mode with the same result. I might try with a 15.4 USB installer and see if that does it. I originally ran into this problem as I was doing a clean install and erased the HD, this time around would just be an upgrade. I also don't mind waiting for 15.5 as I've come across a lot of posts regarding issues with 15.4.
 
Crickster said:
I tried it in safe mode with the same result. I might try with a 15.4 USB installer and see if that does it. I originally ran into this problem as I was doing a clean install and erased the HD, this time around would just be an upgrade. I also don't mind waiting for 15.5 as I've come across a lot of posts regarding issues with 15.4.
Click to expand...
Right. Thats a shame. I don't think the 15.4 usb install over the current will work. Should result to the same error.
 
Last edited:
Just got a new M4 MacBook Pro, so I decided I would erase and then re-install 15.4 on the old M1 MacBook Pro. Now I am this loop of attempting to get an OS on it. I get the same error message. Had an older Mac I was able to make a USB with Monterrey installer, keep trying that, wind up with same issue. Also, it keeps asking me to "Activate" the Mac during this loop. Really need help figuring this out as I am trying to sell this M1 and right now it's DOA. I have the following at my disposal. New M4 MacBook Pro running 15.4, Mac mini M4 running 15.4. A 2016 MacBook Pro running Monterrey (which I used to make the USB installer). Thanks folks.
 
bd700pilot said:
Just got a new M4 MacBook Pro, so I decided I would erase and then re-install 15.4 on the old M1 MacBook Pro. Now I am this loop of attempting to get an OS on it. I get the same error message. Had an older Mac I was able to make a USB with Monterrey installer, keep trying that, wind up with same issue. Also, it keeps asking me to "Activate" the Mac during this loop. Really need help figuring this out as I am trying to sell this M1 and right now it's DOA. I have the following at my disposal. New M4 MacBook Pro running 15.4, Mac mini M4 running 15.4. A 2016 MacBook Pro running Monterrey (which I used to make the USB installer). Thanks folks.
Click to expand...
Sounds like you may have to do a DFU Restore, but what happens when you activate?…this is normal but doesn’t usually cause a problem.
 
When I activate it all goes normal. But then the 15.4 install always fails. I’m trying the MrMacintosh site now, downloading the 15.3.2 installer while booted into 12.7. Then I’ll try the DFU thing.
 
bd700pilot said:
So trying the 15.3.2 installer from the Finder did not work, booted back into Monterrey.
Click to expand...
Have seen this issue. You can't update to Sequoia directly from Monterrey with M1. Don't know why. Solution would be to update to Ventura or Sonoma before updating to Sequoia. Best solution is DFU restore.
 
Last edited:
  • Like
Reactions: bd700pilot
So I was able to perform the DFU restore of the M1 from my new M4 running 15.4. Followed the Apple instructions and it did the whole thing in about 15 minutes. Thanks all!

Next question, did the M4 store the downloaded install file from the DFU process somewhere that I need to delete somehow? Don't want disk space being wasted on the M4.
 
I bought "renewed" Mini M1 from Amazon. It came with 15.3 installed. During the setup process it told me to update to 15.4, which I did, and all went well. It's running great. I don't have much on it as I'm only using it as a picture and music server to my Apple TVs.
 
JUMA55 said:
I bought "renewed" Mini M1 from Amazon. It came with 15.3 installed. During the setup process it told me to update to 15.4, which I did, and all went well. It's running great. I don't have much on it as I'm only using it as a picture and music server to my Apple TVs.
Click to expand...
Yeah. It's crazy how some and not all m1 owners have this problem. I think it has to do with the recovery partition and something is left behind from previous installs or is unable to updated because disk access is denied
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back