F5F Stay Refreshed Software Operating Systems Mac OS Catalina does not support updates or installing new apps/operating systems.

Mac OS Catalina does not support updates or installing new apps/operating systems.

Mac OS Catalina does not support updates or installing new apps/operating systems.

O
ovni1210
Junior Member
2
02-03-2016, 09:00 PM
#1
Hi. I encountered a software issue with my MacBook Pro 13" 2014 (A1502) on Catalina. The SSD upgrade from 256GB to a Corsair MP510 960GB used an adapter from Sintech. Installation of the OS went smoothly, but I needed to format the new drive via a live-boot Ubuntu installation before starting. Everything else worked except for updating the OS and installing apps that required the old installer. When I tried to update through Settings > Software Update, it would restart and show a slow progress bar, then return me to Mac OS. After refreshing, updates failed again. In Disk Utility, I noticed two inactive volumes, but activating them caused an error. Searching online didn’t help, and the App Store updates weren’t visible. When trying to install apps with the old installer, no drive appeared in the boot menu. The same issue occurred when checking settings > Boot Volume. I’m unable to resolve this and hope you can assist. Thanks ahead.
O
ovni1210
02-03-2016, 09:00 PM #1

Hi. I encountered a software issue with my MacBook Pro 13" 2014 (A1502) on Catalina. The SSD upgrade from 256GB to a Corsair MP510 960GB used an adapter from Sintech. Installation of the OS went smoothly, but I needed to format the new drive via a live-boot Ubuntu installation before starting. Everything else worked except for updating the OS and installing apps that required the old installer. When I tried to update through Settings > Software Update, it would restart and show a slow progress bar, then return me to Mac OS. After refreshing, updates failed again. In Disk Utility, I noticed two inactive volumes, but activating them caused an error. Searching online didn’t help, and the App Store updates weren’t visible. When trying to install apps with the old installer, no drive appeared in the boot menu. The same issue occurred when checking settings > Boot Volume. I’m unable to resolve this and hope you can assist. Thanks ahead.

K
56
02-20-2016, 01:35 AM
#2
This situation involves my A level German studies and setting my iPhone in German. Have you attempted using the partitioning tool in the macOS installer to completely erase the new drive to APFS, then also make sure the old drive wasn't listed at all? When you return to the installer, it should present a section where you can select the installed drive and format it to APFS (Apple File System). I believe this might be the cause of the "Aktivieren von AppleAPFSMedia ist fehlgeschlagen" error.
K
KinoahKrazyK31
02-20-2016, 01:35 AM #2

This situation involves my A level German studies and setting my iPhone in German. Have you attempted using the partitioning tool in the macOS installer to completely erase the new drive to APFS, then also make sure the old drive wasn't listed at all? When you return to the installer, it should present a section where you can select the installed drive and format it to APFS (Apple File System). I believe this might be the cause of the "Aktivieren von AppleAPFSMedia ist fehlgeschlagen" error.

L
Lily17
Junior Member
14
02-22-2016, 02:49 PM
#3
You meant to adjust the layout without removing any information. Before installing Mac OS, I formatted the drive to APFS, which is visible in the third screenshot labeled "APFS-Container." I didn’t intend to delete anything. Did I interpret your question correctly?
L
Lily17
02-22-2016, 02:49 PM #3

You meant to adjust the layout without removing any information. Before installing Mac OS, I formatted the drive to APFS, which is visible in the third screenshot labeled "APFS-Container." I didn’t intend to delete anything. Did I interpret your question correctly?

G
gymclo6
Member
187
02-22-2016, 04:36 PM
#4
Correct, I apologize—I missed the details. It looks like this problem is common with Catalina and external drives. I’ll check my results to see if there are any helpful solutions for an internal SSD.
G
gymclo6
02-22-2016, 04:36 PM #4

Correct, I apologize—I missed the details. It looks like this problem is common with Catalina and external drives. I’ll check my results to see if there are any helpful solutions for an internal SSD.

A
alejandrobo1
Posting Freak
877
02-22-2016, 07:55 PM
#5
It seems Mac OS might treat the drive as external, but when updating it tries to point to a non-existent internal one. This could mean external drives aren't supported for updates, which doesn’t really make sense. No need to look up anything—I appreciate the understanding, and I’d be glad to get a hint if you have one.
A
alejandrobo1
02-22-2016, 07:55 PM #5

It seems Mac OS might treat the drive as external, but when updating it tries to point to a non-existent internal one. This could mean external drives aren't supported for updates, which doesn’t really make sense. No need to look up anything—I appreciate the understanding, and I’d be glad to get a hint if you have one.

A
AJPlayzMC2
Member
64
02-23-2016, 02:29 AM
#6
It seems this might be related to a non-OEM drive that was recently added. Most users have relied on external drives instead of installing a new internal one, and likely any solution would address the problem. Don’t worry, I’m here to assist! Have you tried this before? [Link](https://discussions.apple.com/thread/250718774?page=3)
A
AJPlayzMC2
02-23-2016, 02:29 AM #6

It seems this might be related to a non-OEM drive that was recently added. Most users have relied on external drives instead of installing a new internal one, and likely any solution would address the problem. Don’t worry, I’m here to assist! Have you tried this before? [Link](https://discussions.apple.com/thread/250718774?page=3)

D
Dohe
Member
93
02-23-2016, 06:18 AM
#7
Thank you for your message. I attempted to run first aid on container 1, but it returned an error similar to the one described in the link. The output indicates a file system repair issue with exit code 65. It seems the system is reporting problems during verification or repair. I checked recovery mode and confirmed both volumes are active, though the boot selection window appears odd. I also tried installing Windows on a separate partition, and the BootCamp control panel now lists both volumes for Mac OS and Windows.
D
Dohe
02-23-2016, 06:18 AM #7

Thank you for your message. I attempted to run first aid on container 1, but it returned an error similar to the one described in the link. The output indicates a file system repair issue with exit code 65. It seems the system is reporting problems during verification or repair. I checked recovery mode and confirmed both volumes are active, though the boot selection window appears odd. I also tried installing Windows on a separate partition, and the BootCamp control panel now lists both volumes for Mac OS and Windows.