Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Plz re-check again that you use latest version of macOS Mojave Patcher.app
For example, I got problems when installing 10.14 Beta 4 bcoz (on this case) I'm still using prev. version (0.1b11). Thanks.
 

Attachments

  • Screenshot 12.png
    Screenshot 12.png
    106.6 KB · Views: 147
  • Like
Reactions: TimothyR734
I have the same Mojave unsupported mac model and got the same experience in upgrading to Dev Preview 4. Inorder for me to complete the install/upgrade successfully, I booted from my USB install drive containing @dosdude1's Mojave Patcher App and ran Post Install Utility. Selected MBP5,5 and rebuilt the cache and rebooted.

View attachment 772108

Good Luck.

Thank You! That totally worked. I feel dumb now :|
 
  • Like
Reactions: TimothyR734
So all I have to do is just try to install again, ignore the error and restart to post install tool and rebuilt the cache?

It worked for me. I just booted from the USB again, ran the post install tool&restarted. The mac booted right away - however, the install was kinda broken for me - all my apps were missing from /Applications folder. It turned out they were in a '/Recovered Items' folder, along with some stuff from /Library. After i moved the folders back where they belong, everything works as it should.
 
  • Like
Reactions: TimothyR734
I have tried installing the latest beta 4 on my iMac (late 2009); The iMac boots from the USB, the install process starts. About 75% into the install it crashes with error:

Code:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SMMigrationRequest addUserToTransfer:excludedPaths:overwriteTargetName:]: unrecognized selector sent to instance

Any idea what might be the cause? I have tried recreating the USB installer/different USB sticks, same error

You have to do a clean install not an upgrade.
 
  • Like
Reactions: TimothyR734
It worked for me. I just booted from the USB again, ran the post install tool&restarted. The mac booted right away - however, the install was kinda broken for me - all my apps were missing from /Applications folder. It turned out they were in a '/Recovered Items' folder, along with some stuff from /Library. After i moved the folders back where they belong, everything works as it should.
It didn’t work for me. I have run the install again, got the same error, then rebooted back to post install tool, rebuilt caches and rebooted, and then at restart it just hangs on loading. I’m trying to do an upgrade instead of a new installing, I wonder if this is the cause?
 
It didn’t work for me. I have run the install again, got the same error, then rebooted back to post install tool, rebuilt caches and rebooted, and then at restart it just hangs on loading. I’m trying to do an upgrade instead of a new installing, I wonder if this is the cause?

It is. I don’t know why I didn’t think of this before but that’s what the migration error is about.
 
  • Like
Reactions: TimothyR734
It didn’t work for me. I have run the install again, got the same error, then rebooted back to post install tool, rebuilt caches and rebooted, and then at restart it just hangs on loading. I’m trying to do an upgrade instead of a new installing, I wonder if this is the cause?
Yeah, you have to do a clean install, every thing should work fine.
 
Besides my MacMini 5.2 running fine exept acceleration -my Imac 11.2 with HD 4670 runs with Dp4 fine with full acceleration but App store crashes all the time.
 
  • Like
Reactions: Appleak
The UI glitches I am experiencing:

- Light mode: system wide transparency issues.
- Dark mode: There is a slight unsmoothed black frame around the windows (most visible at the corners, especially in front of light background - I checked this on a supported machine, it should look a bit more refined). Some built in apps have visible artifacts (like the left upper and lower left corners of the Messages app). Also, some non-native apps which use transparency but does not support dark mode (1Password 6 for example) will exhibit the transparency issues.

So neither light mode, nor dark mode is perfect. I'd say dark mode is absolutely usable, but there are constant subtle reminders here and there that the system is in fact not supported. :)
Perhaps someone can summarize the UI glitches in the original post, and list which are caused by unsupporting hardware and which are caused by the beta status of the OS? I make this comment because of parrotgeek's post saying UI glitches are gone, and then the subsequent responses by others confirming they aren't gone.

BTW, while I do prefer the overall aesthetics of dark mode, I find some dark mode text more difficult to look at, probably because the pixel density isn't high enough. On a non-Retina machine the white pixelated text on a dark background is bit less clean looking with (the current status of) dark mode. YMMV.
 
Perhaps someone can summarize the UI glitches in the original post, and list which are caused by unsupporting hardware and which are caused by the beta status of the OS?

BTW, this may be my own preference, but I find dark mode more difficult to look at probably because the pixel density isn't high enough. On a non-Retina machine the white pixelated text is bit less clean looking on (the current status of) dark mode.

As far as I know there are no other UI glitches caused by the patcher apart from the transparency glitches that are mainly in light mode but actually occur in dark mode as well albeit much less.
 
  • Like
Reactions: TimothyR734
Thread 1 Crashed:: Dispatch queue: com.apple.CoreAUC.monitorQueue

0 com.apple.CoreAUC 0x00007fff5272e676 0x7fff5272c000 + 9846

1 com.apple.CoreAUC 0x00007fff5272f3b7 0x7fff5272c000 + 13239

2 libdispatch.dylib 0x00007fff6bcc4897 _dispatch_call_block_and_release + 12

3 libdispatch.dylib 0x00007fff6bcc5961 _dispatch_client_callout + 8

4 libdispatch.dylib 0x00007fff6bccbdee _dispatch_lane_serial_drain + 618

5 libdispatch.dylib 0x00007fff6bccc8ae _dispatch_lane_invoke + 388

6 libdispatch.dylib 0x00007fff6bcd4e1d _dispatch_workloop_worker_thread + 603

7 libsystem_pthread.dylib 0x00007fff6bf034a0 _pthread_wqthread + 409

8 libsystem_pthread.dylib 0x00007fff6bf03299 start_wqthread + 13
 
Thread 1 Crashed:: Dispatch queue: com.apple.CoreAUC.monitorQueue

0 com.apple.CoreAUC 0x00007fff5272e676 0x7fff5272c000 + 9846

1 com.apple.CoreAUC 0x00007fff5272f3b7 0x7fff5272c000 + 13239

I have iMac 11,1 confirm AppStore crashes with beta3.

Any of you that having crashing with CoreUAC could try to replace a fresh copy or maybe replacing from a previous version /S/L/PrivateFrameworks/CoreAUC.framework

Perhaps yours is corrupted during install or installed into damaged disk sectors.

Do this test only if you have other working MacOS installation, this is only for test purpose, if you use it as your only main OS then don't do this test.


edit:

Anyway before use any device as your main booting system OS, you should make sure your internal/external spinning/ssd or usb device is in good healthy state, even one only damaged sector can produce these unwanted effects.

Rarely also a faulty RAM.
 
Last edited:
I did a clean install on a new HD with ext fw 800 drive.

In early posts some reported about a kind of incompatibility with Mojave installing/booting to/from IEEE 1394 port, if you could do this test this would be very useful to many: use the internal hard disk inside the firewire enclosure putting it into an external USB enclosure and boot from the same disk, checking if you get no more app crashes.

Or since you wrote it's a new hard disk, maybe in warranty, try this:

from Recovery disk utility clone your firewire 800 installed Mojave to another USB external hdd, and see if they have same behavior in app launch crashing.
 
Last edited:
Cool. I wouldn’t recommend it but you can probably run migration assistant to transfer your files.
I've done that with every "fresh Install" and it works pretty well, 1 more thing, let your Mac goes thru it's "thing" (Indexing Spotlight (mdworker, mds_stores, etc), IconServerAgent, WindowServer, & some kernel_task, to name a few processes) before really pressing it, mine took about 20 minutes.
Just my experience.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.