Search results

Quick update, it seems that this behaviour repet itself after every update. I perform the update, it reboot on a "failed update install" , then I manually select the partition, boot on OS, update went fine, and remove the entry in preboot.. Something happened, update are less seamless but at...

Finally updated for me! It was less smooth than usual: - Tried to update with clover r5109.. No succes (was rebooting in old version).. Tried F11 in clover, nothing - Rolled back to clover r5108! This time install boot option appear, update progessed, then ended on "could not be installed on...

Exactly the same for me

Same issue with me: reboot, no boot volume for update, boot on old os not performing update. I tried twice, no success, even checking hidden volume with F3 on clover.. Strange

Strange.. have you check in your / if you have a “macOS install data” folder? This was the first thing to do

Okay, I went with my balls, and it works ! I checked my Preboot partition on my real mac (macbook pro 13), and saw that there was only two folders (they are long chains of numbers and letters), and these two folder date way back to october 2019, and september 2017! I have way more folder on my...

Same here, don't see that I've also saw that, but this partition is complexe, and I'm super afraid to mess with it :D ! It has the feeling of "you'll break everything if you touch it" ahah

Yep.. I am at the moment trying to trace back where these ****ing entry came from, as there is no "macOS install data" folder anywhere. I must add I am using Filevault, are you also using filevault? Is there something hidden somewhere for the install file to be copy on when updating with filevault?

Even when manually selecting the correct entry, the install one stay there even after several reboot. I’d like to understand what happend, and also fix it as for me it means something dirty has happend

I see we are several in this case. Obviously something happend with update 10.5.4

Hey! I performed the update 10.15.4 earlier today. Before launching the update i made sure my kext where up to date, and updated clover to r5107. After some reboot (not sure how much I was doing other things), I ended on an error message: I rebooted, and try relaunching the install clover...

Update went fine, but install entry in Clover remains there for no reason :)

I guess I am not alone to had issue with last 10.15.4 update. Update is fine I guess, but there is the install entry remaining, quite annoying

SOLVED ! I just cleaned the cash from install here: sudo rm -rf /var/folders/zz/* And now shutdown is working back as normal again X). Definitely a simple fix for those who faced this! :D

I just checked my bios; it is okay. I also tried to re-install properly my Nvidia driver. Still the same! I checked my kexts; there are ok too. I am always super careful when updating my clover/kexts. I always install them, check if okay, and back up the all EFI folder. So it was working fine...

I tried with your config, still not working and still having this black screen and mouse on shutdown. Here is my actual config.plist attached. I am also linking a 'config_old.plist' which I was using before trying to fix this issue with the security update. It has been working fine for years...

I finally performed the update, no issue on this.. BUT STILL, when I reboot or shutdown, I am greeted by a black screen with mouse and it never goes off. I checked, and it is an issue that pops up now and then. I tried to add the "FixShutdown" to my config.plist, to move my "Darkwake=0" to just...

Anyone had an idea why I have this issue on shutdown.. It is pretty annoying :(. It still stuck on a black screen with mouse visible on shutdown (and possible to move) since the update. I have to force shutdown everytime

Strange.. Tried to update, it asked for a reboot, click yes and got stuck on a black screen with my mouse still visible (and i could move it).. Nothing happened.. I forced to reboot and I'm back up again, but the update did not apply. Tried a second time, the same issue.. Will wait I guess X)...

Just update, everything went fine. I patched the Nvidia driver for my 1080gtx with webdriver.sh (I'm running Nvidia 387.10.10.10.30.107 without any issue, glad they finally fix the lag on the last release!) :D