Gigabyte Z390 M Gaming build with working NVRAM

[bambony]

I've had issues with previous hackintoshes with Windows installs messing my EFIs. Try to diable all drives in BIOS other than the windows drive during windows installation as Chef says.

At some points I've had to disable the Windows install drive altogther in BIOS to boot MacOSX. This with a Windows 7, Snow Leopard and El Capitan triple boot machine. Frustrating but workable.

On this topic I've installed Windows 10 on my new machine which is now dual boot. I haven't used Windows 10 for a long time as first impressions were awful. It is SO MUCH BETTER now it has evolved and it runs super smooth on my machine. It's also free if you have an existing Windows 7 license from here: https://www.microsoft.com/en-gb/software-download/windows10 which worked for me.

I'd happily work on WIndows 7 and Snow Leopard forever. I've very little interest in OS bells and whistles. Unfortunately very little modern software works for Snow Leopard and Windows 7 is becoming increasingly less supported.

Tony

 

[LiveSorcerer]

Others have stated that disabling Serial Port (using BIOS F9k or F9j or F7) gets Apple Watch unlock working.

How did the apple watch work? I have the Apple S2 Watch, I enabled it to use to unlock MacOS, but even so it is not working.
I did the procedures informed by Apple.

 

[pastrychef]

How did the apple watch work? I have the Apple S2 Watch, I enabled it to use to unlock MacOS, but even so it is not working.
I did the procedures informed by Apple.

Did you disable serial port in BIOS?

 

[LiveSorcerer]

Did you disable serial port in BIOS?

I did, but I will check again.

 

[LiveSorcerer]

I just checked and the serial is disabled, but it still doesn't unlock.
Another thing I noticed, I am using OpenCore 0.6.0 and it is not enabling the sound of one of the monitors I left as the main one anymore, in this case the LG 32 "4K UK550, after entering MacOS, I have to disconnect and connect his Displayport to turn the sound back on.

 

[pastrychef]

I just checked and the serial is disabled, but it still doesn't unlock.
Another thing I noticed, I am using OpenCore 0.6.0 and it is not enabling the sound of one of the monitors I left as the main one anymore, in this case the LG 32 "4K UK550, after entering MacOS, I have to disconnect and connect his Displayport to turn the sound back on.

I don't know why Apple Watch unlock isn't working for you. I don't have an Apple Watch to test.

Make sure WhateverGreen is enabled in config.plist > Kernel > Add.

 

[neblackford]

It sounds like the Windows installer messed with your macOS EFI partition. I don't know why it did that... The times I've installed Windows, it didn't mess with my macOS EFI but it has been quite a long time since I've installed Windows and I've only done this a few times.

First, let's fix the macOS EFI partition.
Boot in to macOS.
Make a copy of your config.plist to your desktop.
Replace the EFI folder on your EFI partition with a clean copy from post #1.
Replace the config.plist that's in the EFI folder on your EFI partition with the one you copied to your desktop.
Done.

Next, to be safe, I suggest pulling the drive where you have macOS installed before installing Windows. What you want to end up with is to have the Windows Boot Manager on your Silicon Power SSD, not on the Samsung 970 EVO. Once the Windows installation is done, you can re-install the Samsung 970 EVO.

I don't remember if the option exists in BIOS, but, if it does, you can just disable the slot where your Samsung 970 EVO resides and you won't have to physically pull the SSD during the Windows installation.

As for the black screen, I don't know. I don't have enough experience with Windows or its installer to know what can cause that.

Yeah, I have enough experience with Windows MBR and it screwing up, or being screwed up by, other bootloaders. It was surprising to me that Windows took the liberty to mess with other physical drives during an installation. The next logical step for me was to physically remove the EVO 970 while installing Windows and see what happens.

Thanks for the assist in getting my macOS EFI back in order.

 

[pastrychef]

Yeah, I have enough experience with Windows MBR and it screwing up, or being screwed up by, other bootloaders. It was surprising to me that Windows took the liberty to mess with other physical drives during an installation. The next logical step for me was to physically remove the EVO 970 while installing Windows and see what happens.

Thanks for the assist in getting my macOS EFI back in order.

Make sure to do a UEFI Windows installation, not legacy.

 

[neblackford]

Make sure to do a UEFI Windows installation, not legacy.

My boot media was created by Windows' Media Creation utility. I didn't know I could execute a legacy installation from that medium?

At the very least I always attempt a custom (fresh) install of Windows, wherein I delete all partitions and then reformat using the in-built disk utility before installing Windows. I'll be able to mess with this again later today and will report back what happens.

 

[pastrychef]

My boot media was created by Windows' Media Creation utility. I didn't know I could execute a legacy installation from that medium?

At the very least I always attempt a custom (fresh) install of Windows, wherein I delete all partitions and then reformat using the in-built disk utility before installing Windows. I'll be able to mess with this again later today and will report back what happens.

The following guide should do the trick...

How to completely clean install Windows 10 on a UEFI PC

With Windows 10 I generally do recommend to simply upgrade which preserves your apps (modern and desktop), data and settings. In contrast to previous Windows versions the Win 10 upgrade is robust a…

petermeinl.wordpress.com