<< Solved >> Clover No longer Displays the Recovery Option.

I was compelled to use Time Machine to restore my Catalina installation to a previous configuration. (Switching BT devices corrupted TCP/IP.) Afterward, clover displayed only three boot options, macOS, the Win10 working partition, and the Win10 system partition. Previously there were five -- the three choices as above plus the Time Machine drive and Recovery. What caused this to happen? I've launched the Recovery option from Clover at least once on my High Sierra box to remove an update that broke Nvidia hardware acceleration without triggering such a change in the Clover configuration.

How should I fix this? Reinstall Clover using Multibeast?

Look in the Clover config.plist to see if the Recovery volume is listed among the 'Hide Volumes' entries. Here are a couple of screenshots from Clover Configurator the first showing the GUI tab, the second a close up of the Hide Volumes section.





If your GUI > Hide Volumes entries look like the ones above, simply highlight the Recovery entry and press the - sign to remove it. The Recovery icon will reappear on the Clover boot screen, as will the icon for any Windows recovery partition.

My Clover config is now the least of my problems. I was trying to solve a problem with Bluetooth. My IOGear dongle worked well under Catalina but very poorly under Win10. I tried changing to another brand, but that triggered something bizarre pertaining to Bluetooth PAN. Wired Ethernet began to oscillate between CONNECTED and NOT CONNECTED, about once every two seconds. The Network Panel under Systems Settings won't allow me to make any changes. The Status note says "Ethernet is currently active and has the IP address 192.168.1.69" then it refreshes and says "Either the cable for the Ethernet is unplugged or the device at the other end is not responding". This was the problem that compelled me to recover Catalina, but now the issue has returned.

I'm going to ask for help in the appropriate sub-forum.

Well. I think I've fixed my crazy network problem. First, I removed Bluetooth PAN from the device panel in Network. This did nothing. Then I checked my unmanaged switch. I noticed the activity LED was blinking in sync with the ON/OFF behavior I could see in Network. I swapped ports. Nothing. Then I tried a USB Ethernet adapter, which I was pretty sure would not work in any case, but what the hey! Nuthin' as expected. Then I plugged the cable back into the MB network port -- voila! Networking returned to normal, or at least apparently normal. I have no idea why it went bananas in the first place. Why Catalina didn't fix itself when I pulled the plug at the switch is a mystery.

Now back to my Clover problem. Here's my GUI panel. No Recovery partition displayed in "Hidden".

Only thing wrong with that screenshot is you have Legacy=First set under Scan > Custom. Your System is full UEFI and doesn't need the Legacy option set in any manner.

To clear this option, unselect First from the drop down box and then unselect the Legacy option.

You may need to clear the NVRAM for your macOS drive.
When you undertake a number of changes to the config.plist the old settings that have been absorbed in to the NVRAM can remain and still effect the system. Clearing the NVRAM will make if so your new settings are used.

In Clover the way to Clear the NVRAM is to highlight the macOS drive on the Clover boot screen and then press the F11 key. Then Reboot the system and the NVRAM should be reset/cleared of any old settings.

Clover now displays only two boot options: macOS and Windows 10. The Win10 system partition is no longer displayed.

Here's my latest screenshot:

Do you have any entries within the ’Custom Tool’ section?

No. I'm unsure about how to create entries there.

I was just checking because the custom tool section can be used to hide partitions on the boot screen.

I take it the Nvram reset from the clover boot screen didn’t help.

No, It didn't help. However, installing Security Update 2021-002 completely fixed Clover! The recovery boot option reappeared as soon as the update performed its required restart.

I'm baffled.