[GUIDE] Catalina, Big Sur, Monterey, Ventura, Sonoma, Sequoia, Tahoe on HP EliteDesk 800 G4/G5 Mini - The perfect MacMini8,1 Hackintosh

[hiphopboy]

Sorry, the problem on USB install, creat new install usb then ok all

[PlutoDelic]

Looking forward to jump aboard with Tahoe soon. One last dance.

[-FiXER-]

Hi All,

I used the EFI folder from the first post in this topic to try installing macOS Sequoia on a ProDesk 400 G5 Mini and an EliteDesk 800 G5 Mini.

My issue is that as soon as an NVMe drive is installed in the M.2 slot, the USB Sequoia installer crashes and reboots.

To work around it, I removed the NVMe drive and installed macOS successfully by connecting it through a USB NVMe case. However, once I returned the drive to the internal M.2 slot, the system crashes again at boot.

Has anyone encountered (and hopefully solved) this NVMe boot issue with these HP Minis? Any suggestions would be greatly appreciated.

Thanks in advance!

[deeveedee]

Hi, @-FiXER- Please read the known issues here.  I have a feeling your answer is there.

[-FiXER-]

The NVME issue was fixed by just another drive as I figured out it could be compatibility issue.

 

Now there is another issue - the network (Ethernet) is unstable, it works for like 10 seconds, stops working and combing back after couple of minutes, and it is repeating again and again.

 

[deeveedee]

@-FiXER- This thread is for the HP EliteDesk 800 G4 / G5 Mini.  It is not for the ProDesk 400 G5.  If you are asking about your EliteDesk 800 G5 Mini, then be sure to configure your BIOS according to the BIOS document attached to Post #1, follow the install instructions posted here  and look for solutions to problems by exploring Known Issues here.  

 

If you have done all that and still have problems, please post your question and attach your compressed, full Open Core EFI folder to your post.

Edited September 15, 2025 by deeveedee

[deeveedee]

Very easy upgrade to Tahoe Release.  This hack continues to be just as good or better than a real MacMini8,1.

 

 

Software Update detected and applied incremental OTA upgrade with the EFI attached to Post #1.

Spoiler

 

[sgrunt12002]

I have an HP EliteDesk 800 G5 Mini, installed Tahoe with EFI in the first page and all is working.

I have a second disk with windows 11. When boot with opencore in the boot menu i see only tahoe without windows. So i cannot boot windows form opencore only changing order in the bios.

I haven't done any change in the config.plist. It is the same as in the first post, i add only serial etc in platforminfo.

In other my hackintosh multiboot with windows is immediate without any correction to the efi. How can I solve with this HP mini? Thanks

[sgrunt12002]

6 minutes ago, sgrunt12002 said:

I have an HP EliteDesk 800 G5 Mini, installed Tahoe with EFI in the first page and all is working.

I have a second disk with windows 11. When boot with opencore in the boot menu i see only tahoe without windows. So i cannot boot windows form opencore only changing order in the bios.

I haven't done any change in the config.plist. It is the same as in the first post, i add only serial etc in platforminfo.

In other my hackintosh multiboot with windows is immediate without any correction to the efi. How can I solve with this HP mini? Thanks

 

[deeveedee]

On 9/30/2025 at 12:02 PM, sgrunt12002 said:

In other my hackintosh multiboot with windows is immediate without any correction to the efi. How can I solve with this HP mini? Thanks

 

Glad you were able to use this thread to get macOS working on your EliteDesk Mini.  I don't boot Windows with Open Core.  I press F9 at boot to select my Windows disk when I want to boot Windows instead of macOS, so that Windows boots with the native system configuration (unmodified by Open Core).

 

A search for 'how to add Windows boot entry to Open Core' or something similar to that should help if you need to boot Windows via Open Core.

[Anto65]

On 9/30/2025 at 9:02 PM, sgrunt12002 said:

I have an HP EliteDesk 800 G5 Mini, installed Tahoe with EFI in the first page and all is working.

I have a second disk with windows 11. When boot with opencore in the boot menu i see only tahoe without windows. So i cannot boot windows form opencore only changing order in the bios.

I haven't done any change in the config.plist. It is the same as in the first post, i add only serial etc in platforminfo.

In other my hackintosh multiboot with windows is immediate without any correction to the efi. How can I solve with this HP mini? Thanks

 

Make sure that Misc -> Security -> ScanPolicy is set to 0.

 

Alternatively, you can add Windows as custom entries

https://www.insanelymac.com/forum/topic/348097-how-to-custom-entry-in-opencore-to-boot-windows/

 

[deeveedee]

Thanks.

 

@sgrunt12002 I was hoping you'd learn a little more, so if you still want to learn, perform the search which will return links including the Dortania explanation of ScanPolicy.

Edited October 8, 2025 by deeveedee

[sgrunt12002]

Thanks for your replies.

This is the first time I've used multiboot with Windows on this PC. Until now, I've only had Windows. On my other computers, however, I can easily multiboot, as you can see from my signature, without adding anything in custom entries, .
Scan Policy is set to 0 in Misc -> Security -> ScanPolicy.
There's probably a problem with the BIOS settings because after installed opencore using the bios settings in the first post, other than not being able to multiboot,  another problem has appeared. Every time I boot in windows it say  a kind of PIN error and I must recreate the PIN with a lot of steps. Now I've removed the second drive with Tahoe and reset the BIOS, and Windows works fine. So I don't know what to do. I'd like to use Tahoe, but I need Windows 11 to be up and running. Maybe I haven't figured out exactly what the problem is, and it has nothing to do with the BIOS settings. I don't know what to do. 

 

[sgrunt12002]

I did a test. I tried booting with the Tahoe USB installer, which I had previously made when installing Tahoe the first time, to install on another drive, without making any changes to the BIOS. Even though I set USB as the first boot option, when I turned it on, the USB doesn't start at all, but after a few seconds, Windows boots. Obviously, I should set the BIOS to make it compatible with Mac, but I don't know which option I shouldn't change, in the BIOS setting recommended in the first post, for not to give problems booting into Windows, especially with the PIN.

[deeveedee]

@sgrunt12002 Did you try booting Windows with F9?  I don't boot Windows with Open Core, so my EFI is not designed to do that.  My ACPI patches include the appropriate 'If (_OSI("Darwin"))' conditions, but that's about it.

 

EDIT: note that I have Windows 11 installed on one NVME SSD and multiple versions of macOS installed on the other NVME SSD (with Open Core EFI).  My default boot disk is macOS, so when I boot without pressing any keys, the Open Core boot menu appears.  When I want to boot Windows, I press F9 at boot and select the Windows disk.  My BIOS is configured according to my BIOS configuration instructions with TPM enabled.

Edited October 11, 2025 by deeveedee

[sgrunt12002]

Yes when I press F9 I can select UEFI Windows and it boot

[deeveedee]

@sgrunt12002 Then your hack is working as I intended. If you can't press F9 and you need to boot Windows with Open Core, perform the search that I recommended to learn how. When you figure it out, please post your instructions to help others.

[sgrunt12002]

I inserted the Tahoe disk, after change bios settings according to guide in the first post, and now I'm choosing the OS to boot with F9.
Unfortunately, the "PIN isn't available" Windows boot problem sometimes recurs, but reading the forums, it seems to be a Windows problem with the TMP, although resetting the BIOS to default settings makes Windows work fine. In the meantime, I'll definitely do some research and figure out how to boot Windows 11 with Opencore.

[deeveedee]

@sgrunt12002 My posted EFI includes the ACPI patch TPM._STA -> XSTA coupled with SSDT-TPM-Off.aml.  The ACPI patch is intended to hide TPM from macOS, but leave it visible for Windows (the patch has an 'If (_OSI("Darwin"))' condition.  Since I don't boot Windows with my EFI, I am not certain that the ACPI patch is working correctly in Windows (I only verified by inspection).  If you want to test it for me, replace the config.plist in your EFI/OC folder with the attached config.plist (with changes listed below).  Let me know if Open Core boots Windows reliably with this config.plist.

 

Remember to add your PlatformInfo (MLB, ROM, SystemSerialNumber, SystemUUID) to this revised config.plist before you copy it to your EFI/OC folder.  It would also be a good idea to backup your original config.plist before replacing it with the attached version.

 

Changes

• Disable ACPI > Patch > Item0 (TPM._STA -> XSTA)
• Disable ACPI > Add > Item 0 (SSDT-TPM-Off)
• Misc > Security > ScanPolicy = 0

 

config.plist.zip

Edited October 12, 2025 by deeveedee

[sgrunt12002]

Thanks. I'll try it.

[sgrunt12002]

I humbly apologize. I checked my config.plist and scanpolicy wasn't 0. Very strange because I had modified it myself, I probably forgot to save. @Anto65 was right. Now multibooting with Windows works.
I also thank @deeveedee for the suggestions.
Before making the changes deeveedee mentioned, I installed OpenCore 1.0.6 dev from here https://github.com/wjz304/OpenCore_NO_ACPI_Build and it doesn't seem to cause any problems with Windows. Let's see if it still works, otherwise I'll try the changes deeveedee mentioned.
If all goes well, I'll also put Linux on the third disk.
Thanks everyone

Edited October 12, 2025 by sgrunt12002

[deeveedee]

@sgrunt12002 My suggested ACPI patch changes for TPM don't matter if the problem was ScanPolicy; however, ScanPolicy doesn't explain your reported "PIN isn't available" errors.

[sgrunt12002]

ScanPolicy set to 0 solve my multiboot problem.

I'll wait a few days to see if OpenCore Mod NO-ACPI helps the Windows PIN solution otherwise I'll make your suggested changes to the config.plist.

For now several boot and no PIN problem

Thanks

[deeveedee]

@sgrunt12002 At the time of this post, commits to OC 1.0.6 don't do anything that would change behavior on virtually all modern Intel hacks.  If anyone advises an upgrade to OC 1.0.6 or claims that OC 1.0.6 fixed their problems on an Intel hack, ask them what they are smoking ... and then ask them if you can have some of it 

 

EDIT: I missed your "OC-Mod" / "No-ACPI" comment.  That would definitely help if my ACPI patches are not cooperating with Windows.

Edited October 12, 2025 by deeveedee

[sgrunt12002]

😀