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.
My MacBookAir (Mid 2011) also hangs with the boot-bar at 100%.

Is ist possible to reinstall/downgrade to 10.15.3 with an older version of the patcher or should I wait for a new version of the patch? Will it be posible to install a newer version over the not-running 10.15.4? Furtunately I do have another mac to create a boot-device.
 
I download it and will try now.

@jackluke I will try your inappropriate method either.
Don't, it's still not working.
[automerge]1585161969[/automerge]
I know is not a proper method, but if the machines don't install the legacy video patch (the other post-install patches can be installed), 10.15.4 will boot and allow the welcome screen on a clean install unsupported mac, then from Catalina desktop if use the ASentientBot libraryvalidation.plist and after apply the legacy video patch it should work.

Anyway seems that apple on purpose added these security checks on SkyLight and CoreDisplay, because this AMFI check is mainly about "non-metal" frameworks.
The issue is that WindowServer now requires library validation, meaning it will not load libraries with different signatures. Modified frameworks lose their signature, so they will not load.
 
Did you install with a patched 10.15.4 installer created with Catalina Patcher 1.3.2? I installed on my MacPro 3,1 with GTX680 using Catalina Patcher 1.3.1 and Music runs just fine.

I used patcher 1.3.3. I was going to reinstall 10.15.3 with patcher 1.3.1 but unfortunately that's the ONE version I neglected to save.

I'm just working from Mojave right now...
 
Don't, it's still not working.
[automerge]1585161969[/automerge]

The issue is that WindowServer now requires library validation, meaning it will not load libraries with different signatures. Modified frameworks lose their signature, so they will not load.

And what if use the SkyLight's WindowServer from 10.15.3 ?

I tried to use the stock SkyLight, CoreDisplay, OpenGL and GPUSupport frameworks from 10.15.3 and they worked on 10.15.4 beta with AMFI enabled, of course using those no video acceleration.
 
  • Like
Reactions: Pinarek
just updated my MBP 5.3 from 10.15.3 to 10.15.4 with the Dosdude1 installer all went well and I'm very happy with it. Dosdude1 is the dude :cool: splendid work man ... only thing I have noticed is that cleanmymac is not working anymore it just crashes but I can live with that

rene
 
  • Like
Reactions: Balaur
Don't, it's still not working.
[automerge]1585161969[/automerge]

The issue is that WindowServer now requires library validation, meaning it will not load libraries with different signatures. Modified frameworks lose their signature, so they will not load.

Anyway, I tried and didn't work just like you said. Still getting the same verbose. o_O

I am waiting you from now on when you say ready I will try 👍
 
  • Like
Reactions: K two
Don't, it's still not working.
[automerge]1585161969[/automerge]

The issue is that WindowServer now requires library validation, meaning it will not load libraries with different signatures. Modified frameworks lose their signature, so they will not load.

So this is only an issue with non-Metal machines using the legacy video patches, right?
 
  • Like
Reactions: Dilli and jackluke
My MacBookAir (Mid 2011) also hangs with the boot-bar at 100%.

Is ist possible to reinstall/downgrade to 10.15.3 with an older version of the patcher or should I wait for a new version of the patch? Will it be posible to install a newer version over the not-running 10.15.4? Furtunately I do have another mac to create a boot-device.

You can re-install 10.15.3 over your 10.15.4 that currently has issues with some machines in booting the "legacy video patch", but before re-install, try this booting your 10.15.4 in single user mode:


After you set the nvram, boot again to the USB Catalina Patcher and re-apply the post-install patches and "force rebuild cache", then retry to boot 10.15.4 .
 
Last edited:
Anyway, I tried and didn't work just like you said. Still getting the same verbose. o_O

I am waiting you from now on when you say ready I will try 👍

If you re-install 10.15.4 , and during the post-patches you quickly de-select the "Legacy Video patch" it will work, without video acceleration of course.
[automerge]1585164517[/automerge]
I'm not sure if your problem is related to mine, but I have a fully metal supported machine and have issues as posted earlier.

If you delete the DisableLibraryValidation.kext Music.app will work without crashing.

Open Catalina terminal and copy/paste:
Code:
sudo rm -r /Library/Extensions/DisableLibraryValidation.kext
sudo rm -r /System/Library/Extensions/DisableLibraryValidation.kext
sudo kextcache -i /
sudo reboot
 
  • Like
Reactions: Dilli and Pinarek
If you re-install 10.15.4 , and during the post-patches you quickly de-select the "Legacy Video patch" it will work, without video acceleration of course.
I tried with out applying the legacy video patch and the AMD metal emulator patch it still got stuck as I asked dosdude when we create a Catalina Patcher does the CoreDisplay get patched with Asentientbot's wrappers and he replied yes they do
 
  • Like
Reactions: Pinarek
Thanks, I'll give that a try...

Okay, that worked perfectly. How can I avoid that SNAFU in the future if I need to reinstall? Also, will anything else be affected?

Actually I was booted to Mojave when I deleted it. I only found one instance instead of two. I just rebooted into Catalina and it worked fine without any cache rebuilding. Should I leave it alone or run the terminal commands you just posted?
 
I tried with out applying the legacy video patch and the AMD metal emulator patch it still got stuck as I asked dosdude when we create a Catalina Patcher does the CoreDisplay get patched with Asentientbot's wrappers and he replied yes they do
Wrappers are part of the Legacy Video Card Patch, and are NOT installed unless that patch is installed..
 
I'm not sure if your problem is related to mine, but I have a fully metal supported machine and have issues as posted earlier.
I'm not having any problems at all on a MacPro 3,1 with metal supported GTX680 installed with Catalina Patcher 1.3.1.
 
Not sure if this helps or not, but I installed 15.4.4 over an existing 15.4.3 installation on an upgraded iMac 7,1. In verbose mode, it says "...CoreDisplay is adhoc signed" multiple times, and then just hangs.
 
Don't, it's still not working.

I never update in real time because I find out a few days later it's out, BUT, with all this time on my hands, I did my usual Dosdude routine and it went really quick! That's because it just went over 10.15.3 lol. Anyway, no issues going over it. Let us know when it will work good man and thanks for all you do. I contributed gladly a while ago.
 
Wrappers are part of the Legacy Video Card Patch, and are NOT installed unless that patch is installed..

Previously during the 10.15.4 beta , some downloaded the "full 10.15.4 beta installer" through "Mojave's Software Update" and created a "10.15.4 installer patcher" using your "10.15.3 Catalina patcher", adding the ASentientBot libraryvalidation.plist to disable AMFI, that worked.

But I am not sure if something is changed in this final release.
 
  • Like
Reactions: Pinarek and K two
Previously during the 10.15.4 beta , some downloaded the "full 10.15.4 beta installer" through "Mojave's Software Update" and created a "10.15.4 installer patcher" using your "10.15.3 Catalina patcher", adding the ASentientBot libraryvalidation.plist to disable AMFI, that worked.

But I am not sure if something is changed in this final release.
I am now trying to install OS to over mine and when finished I will boot and open Post installer with Opt key and install all patches except Legacy Video Patch. We will see what will happen! But I realize there is also Validate patcher on Post-installation should I install it or I must also deactivate it while installing other patches?
 
  • Like
Reactions: jackluke
After you set the nvram, boot again to the USB Catalina Patcher and re-apply the post-install patches and "force rebuild cache", then retry to boot 10.15.4 .
When rebooting to the USB Catalina Patcher, I'm not able to select my MacinthoshHD to re-apply the post-install patches. The volume does not appear in the volume selection. What to do?
 
The patch updater pref pane, in my case, crashes system preferences:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x000000010fd0a000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x2

kernel messages:

VM Regions Near 0x10fd0a000:
Image IO 000000010fcd4000-000000010fd0a000 [ 216K] r--/r-- SM=PRV
--> mapped file 000000010fd0a000-000000010fd0f000 [ 20K] r-x/rwx SM=COW Object_id=2b03f1d3
VM_ALLOCATE (reserved) 000000010fd0f000-000000010fd12000 [ 12K] rw-/rwx SM=NUL reserved VM address space (unallocated)

Application Specific Information:
dyld3 mode
com.dosdude1.Patch-Updater-Prefpane v.1.0 (Patch Updater)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdyld.dylib 0x00007fff68baa053 dyld3::MachOFile::isMachO(Diagnostics&, unsigned long long) const + 9
1 libdyld.dylib 0x00007fff68bc0b5d invocation function for block in dyld3::Loader::mapImage(Diagnostics&, dyld3::LoadedImage&, bool) + 357
2 libdyld.dylib 0x00007fff68ba092c dyld3::closure::Image::forEachDiskSegment(void (unsigned int, unsigned int, unsigned int, long long, unsigned long long, unsigned char, bool, bool&) block_pointer) const + 284
3 libdyld.dylib 0x00007fff68bad952 dyld3::Loader::mapImage(Diagnostics&, dyld3::LoadedImage&, bool) + 1578
4 libdyld.dylib 0x00007fff68ba7edd dyld3::Loader::mapAndFixupAllImages(Diagnostics&, bool, bool) + 353
5 libdyld.dylib 0x00007fff68ba7580 dyld3::AllImages::loadImage(Diagnostics&, unsigned int, dyld3::closure::DlopenClosure const*, bool, bool, bool, bool) + 526
6 libdyld.dylib 0x00007fff68ba237b dyld3::AllImages::dlopen(Diagnostics&, char const*, bool, bool, bool, bool, bool, void const*) + 943
7 libdyld.dylib 0x00007fff68ba1e8b dyld3::dlopen_internal(char const*, int, void*) + 206
8 libdyld.dylib 0x00007fff68ba1d53 dlopen + 116
9 com.apple.CoreFoundation 0x00007fff2ed7dda0 _CFBundleDlfcnLoadBundle + 145
10 com.apple.CoreFoundation 0x00007fff2edf6b61 _CFBundleLoadExecutableAndReturnError + 482
11 com.apple.Foundation 0x00007fff3141091f -[NSBundle loadAndReturnError:] + 369
12 com.apple.Foundation 0x00007fff314430c6 -[NSBundle principalClass] + 23
13 com.apple.frameworks.preferencepanes 0x00007fff39eb9471 -[NSPrefPaneBundle isLinkedOnMacOS10_14_Or_Later] + 48
14 com.apple.frameworks.preferencepanes 0x00007fff39eb94d5 -[NSPrefPaneBundle supportedAppearance] + 47
15 com.apple.systempreferences 0x000000010bdc2aed 0x10bdbb000 + 31469
16 com.apple.systempreferences 0x000000010bdc203d 0x10bdbb000 + 28733
17 com.apple.systempreferences 0x000000010bdc1e98 0x10bdbb000 + 28312
18 com.apple.Foundation 0x00007fff314457c2 __NSFireDelayedPerform + 415
19 com.apple.CoreFoundation 0x00007fff2ed70628 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
20 com.apple.CoreFoundation 0x00007fff2ed7018e __CFRunLoopDoTimer + 872
21 com.apple.CoreFoundation 0x00007fff2ed6fc79 __CFRunLoopDoTimers + 322
22 com.apple.CoreFoundation 0x00007fff2ed548dd __CFRunLoopRun + 1885
23 com.apple.CoreFoundation 0x00007fff2ed53b23 CFRunLoopRunSpecific + 466
24 com.apple.HIToolbox 0x00007fff2d975abd RunCurrentEventLoopInMode + 292
25 com.apple.HIToolbox 0x00007fff2d9756f4 ReceiveNextEventCommon + 359
26 com.apple.HIToolbox 0x00007fff2d975579 _BlockUntilNextEventMatchingListInModeWithFilter + 64
27 com.apple.AppKit 0x00007fff2bfc0c99 _DPSNextEvent + 883
28 com.apple.AppKit 0x00007fff2bfbf4e0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
29 com.apple.AppKit 0x00007fff2bfb11ee -[NSApplication run] + 658
30 com.apple.AppKit 0x00007fff2bf82ff6 NSApplicationMain + 777
31 libdyld.dylib 0x00007fff68bb6cc9 start + 1

Any ideas?

Thanks
 
Just wanted to say that I´m running Catalina 10.15.4 on my Mac Pro 5.1, updated GPU and WIFI/BT module, just with the argument -no compat in nvram.

For the first time, everything is working like a charm. Even unlock apps and the Mac with Apple Watch.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.