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.
Looks like when we try to connect iCloud Sync log mention missing entitlement; I don't get it why is this work on 10.15.3 without any problem?

Code:
Tue Apr 28 18:58:41 2020| 70403002 [SYNC:(Secondary Thread 0x600003777e80):<OPCloudKitSyncer: 0x103b57e00>] E verifyCloudKitAvailableWithCompletionHandlerOnMain: | iCloud access not available: The application is missing required entitlement com.apple.developer.icloud-services
 
  • Like
Reactions: TimothyR734
Used Catalina Patcher (1.4.3) on my MacBookPro6,2 to install Catalina after I did fresh install of High Sierra and Catalina appears to be working great.

Installed Microsoft Office 2019 16.34 and I can't open any of the Office apps. I receive the "Code Signature Invalid" error whenever I try to open them. Does anyone know how to fix this?

I tried opening multiple times, tried running sudo killall taskgated and still no luck.
Any ideas on how to fix this? Thanks!
 
Used Catalina Patcher (1.4.3) on my MacBookPro6,2 to install Catalina after I did fresh install of High Sierra and Catalina appears to be working great.

Installed Microsoft Office 2019 16.34 and I can't open any of the Office apps. I receive the "Code Signature Invalid" error whenever I try to open them. Does anyone know how to fix this?

I tried opening multiple times, tried running sudo killall taskgated and still no luck.
Any ideas on how to fix this? Thanks!
Do you have the latest version of Microsoft Office installed, and in the terminal what does nvram -p show I think the sudo killall taskgated only works if you don't have amfi_get_out_of_my_way in your nvram
 
Do you have the latest version of Microsoft Office installed, and in the terminal what does nvram -p show I think the sudo killall taskgated only works if you don't have amfi_get_out_of_my_way in your nvram

It's the very latest updated version of Office 2019.
nvram-p shows:
Code:
efi-backup-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%f2%c8%1d%00%00%00%00y[%b0%ecPXaA%ad%97AF%abb~%16%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%dc%eb%00,U%f5J%8f&%bb%a0|I%83e%04%04%9a%00\%008%00A%005%00F%005%001%00C%002%00-%007%005%002%001%00-%003%009%003%001%00-%00B%00F%009%002%00-%008%007%005%009%00F%00D%00E%002%00B%00E%000%008%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
boot-gamma    %10%06%00%00%a4%9c%00%00%00%00%00%00n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8
boot-args    -no_compat_check
efi-backup-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>00EBDC4F-552C-4AF5-8F26-BBA07C498365</string></dict></dict><key>BLLastBSDName</key><string>disk21s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\8A5F51C2-7521-3931-BF92-8759FDE2BE08\System\Library\CoreServices\boot.efi</string></dict></array>%00
gpu-policy    %01
IONVRAM-SYNCNOW-PROPERTY    IONVRAM-SYNCNOW-PROPERTY
efi-apple-recovery-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00r%f9`%d2%b9%d6AB%a6%c1%ff%e9%e0%10%b0=%02%02%04%04T%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00M%00B%00P%006%001%00_%000%000%005%00D%00_%000%000%00B%00.%00s%00c%00a%00p%00%00%00%7f%ff%04%00
backlight-level    %db%00
bluetoothInternalControllerInfo    %18%82%ac%05%000%11%fa%c8%bc%c8%e7%e8P
prev-lang:kbd    en:0
SystemAudioVolumeDB    4
efi-apple-recovery    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>4CD9E393-B396-4ECC-BAB2-EEAA76C7FDCF</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\MBP61_0057_11B_LOCKED.scap</string></dict></array>%00
EFICapsule_Result    STAR
bluetoothActiveControllerInfo    %18%82%ac%05%00%00%000%11%fa%c8%bc%c8%e7%e8P
fmm-computer-name    User1%e2%80%99s MacBook Pro
efi-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%f2%c8%1d%00%00%00%00y[%b0%ecPXaA%ad%97AF%abb~%16%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%dc%eb%00,U%f5J%8f&%bb%a0|I%83e%04%04%9a%00\%005%001%003%005%003%008%00B%004%00-%00A%001%008%002%00-%004%005%00B%000%00-%008%00F%002%00D%00-%00B%005%004%00C%005%001%002%00A%00B%004%00F%006%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
efi-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>00EBDC4F-552C-4AF5-8F26-BBA07C498365</string></dict></dict><key>BLLastBSDName</key><string>disk1s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\513538B4-A182-45B0-8F2D-B54C512AB4F6\System\Library\CoreServices\boot.efi</string></dict></array>%00
SystemAudioVolume    %db
LocationServicesEnabled    %01
 
It's the very latest updated version of Office 2019.
nvram-p shows:
Code:
efi-backup-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%f2%c8%1d%00%00%00%00y[%b0%ecPXaA%ad%97AF%abb~%16%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%dc%eb%00,U%f5J%8f&%bb%a0|I%83e%04%04%9a%00\%008%00A%005%00F%005%001%00C%002%00-%007%005%002%001%00-%003%009%003%001%00-%00B%00F%009%002%00-%008%007%005%009%00F%00D%00E%002%00B%00E%000%008%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
boot-gamma    %10%06%00%00%a4%9c%00%00%00%00%00%00n%00%00%00%00%00%00%00%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8%07%00%04%04%db%05%0b%0b%b2%0e%1e%1e%95$66m>WWO`ww%09%80%a1%a1%87%a8
boot-args    -no_compat_check
efi-backup-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>00EBDC4F-552C-4AF5-8F26-BBA07C498365</string></dict></dict><key>BLLastBSDName</key><string>disk21s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\8A5F51C2-7521-3931-BF92-8759FDE2BE08\System\Library\CoreServices\boot.efi</string></dict></array>%00
gpu-policy    %01
IONVRAM-SYNCNOW-PROPERTY    IONVRAM-SYNCNOW-PROPERTY
efi-apple-recovery-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00r%f9`%d2%b9%d6AB%a6%c1%ff%e9%e0%10%b0=%02%02%04%04T%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00M%00B%00P%006%001%00_%000%000%005%00D%00_%000%000%00B%00.%00s%00c%00a%00p%00%00%00%7f%ff%04%00
backlight-level    %db%00
bluetoothInternalControllerInfo    %18%82%ac%05%000%11%fa%c8%bc%c8%e7%e8P
prev-lang:kbd    en:0
SystemAudioVolumeDB    4
efi-apple-recovery    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>4CD9E393-B396-4ECC-BAB2-EEAA76C7FDCF</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\MBP61_0057_11B_LOCKED.scap</string></dict></array>%00
EFICapsule_Result    STAR
bluetoothActiveControllerInfo    %18%82%ac%05%00%00%000%11%fa%c8%bc%c8%e7%e8P
fmm-computer-name    User1%e2%80%99s MacBook Pro
efi-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%f2%c8%1d%00%00%00%00y[%b0%ecPXaA%ad%97AF%abb~%16%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%dc%eb%00,U%f5J%8f&%bb%a0|I%83e%04%04%9a%00\%005%001%003%005%003%008%00B%004%00-%00A%001%008%002%00-%004%005%00B%000%00-%008%00F%002%00D%00-%00B%005%004%00C%005%001%002%00A%00B%004%00F%006%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
efi-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>00EBDC4F-552C-4AF5-8F26-BBA07C498365</string></dict></dict><key>BLLastBSDName</key><string>disk1s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\513538B4-A182-45B0-8F2D-B54C512AB4F6\System\Library\CoreServices\boot.efi</string></dict></array>%00
SystemAudioVolume    %db
LocationServicesEnabled    %01
Screen Shot 2020-04-28 at 11.23.27 AM.png
This is the version I have installed on mine
 
  • Like
Reactions: telepati
You should always keep one machine with high sierra. Since Mojave and Catalina requires some updates of high sierra.

if you install Mojave in your machines you can run 32bit apps which is the last of Mac OS to allow it. Also it requires afps format so does Catalina.

if you want the feel of all different OS then keep all 3 . one each in respective machines.
It is all matter of choice. Catalina is a bit troublesome but if you get all going then it works like a charm on unsupported machines. Except you may have to do away with airdrop or hands off depending upon what wifi/bluetooth card you have.It only works for broadcom cards.

Since you have photo library on external usb stick there should not be an issue opening it in any of system. You can just press option while clicking on photo app and selecting the library.

Rest since the choice of OS is subjective its best for you what you like. cheers
[automerge]1587966488[/automerge]

Thats wonderful @dosdude1 . Cheers
[automerge]1587966837[/automerge]
Tks @highvoltage12v . Wonderful for imac 2011 upgraded mxm cards such as we having these blank screen issue. Could you provide the link to the patched ktext file. Tks
These should be added separately, because I guess his changes won't work for non-metal acceleration on dual GPUs machine, because is using stock Catalina: AGPM, AMCCSControl and AGC kext with its stock Catalina AGC plugins as AGDP (with iMac board id added), Mux and so on .
In a PM with @dosdude1 I mentioned a separate checkbox should be added for "2011 MXM Metal iMac's", what i'm assuming would happen is when this checkbox is clicked it will install the some additional patches from a separate folder within the post installer. Some of the Kexts in his installer are redundant such as HD3000/SNBFramebuffer/plugins etc, IOSurface and MCCS. Yes a separate AppleGraphicsControl needs to be added to the installer and placed inside this presumed "MXM-Metal-iMac" folder.

When this "2011 MXM Metal iMac's" option is selected the following need to be installed from "video card patches" folder. These kexts already exist and a duplicate folder isn't needed.
  • AppleIntelHD3000Graphics.kext
  • AppleIntelHD3000GraphicsGA.plugin
  • AppleIntelHD3000GraphicsGLDriver.bundle
  • AppleIntelHD3000GraphicsVADriver.bundle
  • AppleIntelSNBGraphicsFB.kext
  • AppleIntelSNBVA.bundle
  • AppleMCCSControl.kext
  • IOSurface

A new folder (within video card patches) will need to be added such as "MXM-Metal-iMac" which contains the following to be installed
  • AppleGVA.framework to PrivateFrameworks (fixes Airplay/enables iGPU encoding)
  • AppleGraphicsControl.kext (a stock copy with added board ID's, fixes blank screen)
Hope this clears things up a bit.
 
Last edited:
This is the version I have installed on mine
Looks like you have 16.37 Office 365.

I have Office 2019 Professional VL (not 365). My Word version is 16.36 and is latest available from Microsoft Update.
I installed the same Office on my 2014 MacBook Air and it works without any issue.

I uninstalled Office 2019 and installed Office 365 and still has the same issue.
 
  • Like
Reactions: TimothyR734
Damn!
I just solved the problem!(At least for this session.I wonder if it works after a restart)
First you do (optionally) xattr -lr <path_to_app_bundle> to get the list of the files that cause the error.
Then you do xattr -cr <path_to_app_bundle>.
And now you are finally ready to change the code signature using sudo codesign -f -s - <path_to_app_bundle>.

For my case with chrome browser I used the following <path_to_app_bundle> :
/Applications/Google\ Chrome.app

Thanks! This fixed my Office Applications and Google Chrome.

Quick Question. Do I have to perform this after every single update?

Is this something only needed on 10.5.4 patched? Is this something that can be fixed in an update?
Thanks for the help!
 
I have install imac 2012 completly fresh without timemachine backup... But i have unchecked auto patcher .... A popup say after install you must set the patch manually.... Now in the end on the first desktop mirror i look patcher auto installed ...hä @dosdude1 its a bug or a feature :(....
 
  • Like
Reactions: TimothyR734
I have install imac 2012 completly fresh without timemachine backup... But i have unchecked auto patcher .... A popup say after install you must set the patch manually.... Now in the end on the first desktop mirror i look patcher auto installed ...hä @dosdude1 its a bug or a feature :(....
The iMac 2012 is a supported machine, isn't it?
 
Hi All
I am running Catalina on MBP early 2011 8,2 and have followed the guides to get airdrop working.
The MBP can see my devices (iPhones) but they can not see the MBP over airdrop.

have I missed something how can I get this iPhones to see the MBP via airdrop?
any help would be gratefully received.
cheers
Hi, I have the same system. Have you followed the proposed process by Jackluke (Go to post #18165 from @jackluke)? In any case you will need for 8,2 a BT 4.0 USB dongle in order to make Airdrop and handoff possible. Hope this helps. Cheers.
 
Last edited:
  • Like
Reactions: TimothyR734
What do you mean everyone? How? Is this just related to a specific version of MacOS or Safari? That seems like a huge deal.

It's a safari-bug for Catalina version >= v10.15.3

I suppose this flow could resolve the problem:
1. Install patched v10.15.2
2. Enable extensions in Safari (eg 1password critical for me)
3. Update Catalina to v10.15.4.02 (OTA or another method)

But I know how to install last version (patch v1.4.3 + OS X 10.15.4.02) only.
If described by me flow is ok, maybe anybody could suggest steps to achieve result with minimum troubles.
I'am ready for test it.

@dosdude1 thanks for your work
 
Last edited:
  • Like
Reactions: TimothyR734
[Cross-posting from Mojave on Unsupported, since I'd found more discussion of the Zoom rendering issue posted in this thread. Apologize for any inconvenience anyone might experience. Though if disorientation lasts more than an hour, consult with a doctor.]

Anxious with the release of Zoom 5.0 for Unsupported Mojave and Catalina users to try it and see if maybe, maybe Zoom added back non-Metal support for Unsupported macOS users.

(Way I figure, the app works fine on those older machines under macOS versions older than 10.14. So they have the code, and they're doing a simple version check to determine which rendering code to run. Seems all they really need to do is to check to see if Metal is actually –supported– at runtime when on 10.14 and later and fall-back to the older rendering code if not, rather than merely checking if they're running on 10.14 or later. If they'd not just assume… there is a chance.)

Alternatively: are there any injector methods in the Unsupported community to target SPECIFIC apps whereby if/when Zoom.app does a platform check we could make it THINK it is running on High Sierra (when running on Mojave or Catalina)?? As in, is there a way to "fool" Zoom into thinking it is running under 10.13 while actually running on 10.14/15?
 
  • Like
Reactions: TimothyR734
@dosdude1 @ASentientBot Just installed Catalina 10.5.4 on Seagate Z500CM10002 Internal SSD on my Mac mini 2010 and works fine! I really hope that also 10.6 will be patchable, waiting next generation macOS ARM A13 that will close all games...
I'm excited for 10.16 too, but my crappy graphics patches are not going to cut it. (@pkouame and @oliveira131 both had some promising ideas, but they seem to have disappeared. I've been playing with some stuff too, but it's a bit above my pay grade. Hopefully we can figure something out by June!)

We (and the Hackintosh folks) don't have to worry about A13 Macs for a while, since Apple is bound to support recent Intel machines like the 2019 Mac Pro for several more years. I do look forward to seeing what they do with ARM-based MacBooks though -- maybe an improved revival of the unsuccessful 12" MacBook?
 
I mean 2011 sry :)
While installing on the iMac mid 2011 you do not need to deselect the option "auto-apply post install patches" since the patcher will not install the legacy video patch on this machine by default. At least this is my experience. Only on the 2009/2010 models with a metal graphics you need this extra step.
 
Dear Guys,

I'd like to share with you my saga...

I got a 2011 MacBook Pro (8,1) running smoothly on Mojave 10.14.6. I was intending to move to Catalina 10.15.4, but due to Improvement UI matter, I've decided to go to 10.15.3. So, I was unable to install it with the latest patcher. For some reason the installation got stuck on Apple logo progress bar. I managed to do it with previous patcher version - 1.3.4 I think.

After that, everything set up, I've installed the latest version of Microsoft Office 2019. Everything seemed to be fine until I tried to present - fullscreen - a pptx file. If you use slide transition effects, Powerpoint shows only black screen. If you remove slide transition effects, everything else runs smoothly. This is kind of weird and disappointing. I have no idea how to even start to fix it.

It seems poor, but PowerPoint presentations play a important role in my daily job.

Does anybody can help me find out what is going on?

Thanks in advance.
 
While installing on the iMac mid 2011 you do not need to deselect the option "auto-apply post install patches" since the patcher will not install the legacy video patch on this machine by default. At least this is my experience. Only on the 2009/2010 models with a metal graphics you need this extra step.
One can always check what post-install patches will be applied, by booting from the USB installer and invoking post-install: the pre-selected patches for the Mac model are shown. One can change selection, skip or quit at that point.
 
One can always check what post-install patches will be applied, by booting from the USB installer and invoking post-install: the pre-selected patches for the Mac model are shown. One can change selection, skip or quit at that point.
Is such a change persistent when you directly start the installation or creation of a bootable USB stick/SD Card?
Or in other words: Can we preselect in that way which patches will be installed later by the (patched) installer automatically?
 
  • Like
Reactions: TimothyR734
Is such a change persistent when you directly start the installation or creation of a bootable USB stick/SD Card?
Or in other words: Can we preselect in that way which patches will be installed later by the (patched) installer automatically?
Changes are not persistent. The pre-selection is always done on basis of the Mac model (and for the APFS patch, depending on the option chosen when the patcher is started to produce a bootable USB installer or to "install to this machine").

I guess dosdude rightly wants to keep operation simple and less error prone than it would be with more hidden choice.
[automerge]1588193529[/automerge]
Just started installation of 10.15.5 Beta 3 (OTA, 2.97GB).
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.