Users of macOS 11 alias Big Sur once again report problems restoring their computer. Were there with macOS 11. 0 recovery difficulties over a longer period of time on M1 Macs, for which Apple provided a whole list of workarounds, This time, Intel machines are specifically affected. A recovery can be useful if you have problems with your macOS installation.

This time it’s Intel Macs Like the blog Mr. Macintosh was the first to report, the so-called Internet Recovery is now on strike with Intel Macs. The latest version of macOS can be obtained via the network and installed immediately, as long as the machine can establish an Internet connection from recovery mode – via WLAN or Ethernet.

Instead of offering the latest operating system version macOS 10. 1 alias Big Sur for download, only macOS has been released for a few days 10. 15 aka Catalina if you look at the internet – Want to initiate recovery on Intel Macs. Why this is happening is not yet clear – Mr. Macintosh speculates that this is a server-side problem. According to information in the MacAdmins forum, Apple has even unofficially communicated this to the outside world and announced that it is “working” on the problem. However, a deadline for a fix was not given. As mentioned, M1-Macs are not affected by the error because the recovery process takes place in a different way here.

App- Store error under Mojave Another server-side problem affects the Mac App Store. MacOS users 10. 14 aka Mojave can no longer use this permanently. When trying to update an application, the message appears – sometimes for weeks – that the system cannot “complete the purchase”. Below is a simple “canceled” (canceled). Developer Jeff Johnson was able to prove that the server “osxapps.itunes.apple.com”, which is necessary for the updates, simply disconnects – why is unclear.

Johnson speculates that Apple is definitely on the error his side and no – unlikely – update for Mojave is necessary. Especially annoying for developers: customers who cannot update their apps due to the bug contact the developer – and not Apple, although the Concentrate is responsible for the current problem. (bsc)