Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[canyondust]

I only use OC to boot macOS. For other OSes, I also just use F12 menu and use their native boot loader.

I learned this early on when I started using OC... Windows would crash upon boot. Perhaps it is fixed now and various SSDTs have been re-written to apply in the macOS context only, but like you, I just use F12. Also, I recently tried booting Win 11 with OC, and my Activation got disabled. So OC will be macOS only for me.

And that's it.

I'm the same. I don't want my PC appearing to Windows as an iMac, it's an unnecessary abstraction.

 

[CaseySJ]

I don't know how others are handling this, but I boot Windows from the F12 menu with BIOS F5. Its fast (faster than OC's boot), and I have no issues booting Windows 11 (or Linux).

All I do is as soon as I hear the boot speaker (if you don't have one, you can use the splash screen display), I press F12, select the Windows disk and boot. Fast, easy and no problem.

If i want to boot into Monterey, I just let the boot process go, and it loads macOS automatically.

I have booted into Windows from the OC open canopy menu, and it has booted, but its slower, only because there's more waiting.

Just something to consider for those who are having issues. This might work for you.

I only use OC to boot macOS, otherwise I just use F12 menu and use the native boot loader for other OSes. I learned this early on when I started using OC... Windows would crash upon boot. Perhaps the it is fixed now and various SSDTs have been re-written to apply in the macOS context only, but like you, I just use F12.

And that's it.

Windows boots properly through OpenCore on all 5 of my Hackintoshes. Recently we made these changes in order to be more Windows-friendly:

1. ACPI --> All SSDTs use conditional arguments for macOS
2. Kernel --> CustomSMBIOSGuid --> Enabled
3. PlatformInfo --> UpdateSMBIOSMode --> Custom
4. PlatformInfo --> DataHub --> AdviseFeatures --> Enabled

Items 2 and 3 prevent OpenCore from injecting macOS or Acidanthera properties into Windows.

Some folks are reporting problems booting Windows when AppleVTD is enabled, but they haven't tried to pin down the cause. Even with AppleVTD enabled, all of my Intel-based Hackintoshes can boot Windows through OpenCore.

 

[dehjomz]

Windows boots properly through OpenCore on all 5 of my Hackintoshes. Recently we made these changes in order to be more Windows-friendly:

1. ACPI --> All SSDTs use conditional arguments for macOS
2. Kernel --> CustomSMBIOSGuid --> Enabled
3. PlatformInfo --> UpdateSMBIOSMode --> Custom
4. PlatformInfo --> DataHub --> AdviseFeatures --> Enabled

View attachment 531004
Items 2 and 3 prevent OpenCore from injecting macOS or Acidanthera properties into Windows.

Some folks are reporting problems booting Windows when AppleVTD is enabled, but they haven't tried to pin down the cause. Even with AppleVTD enabled, all of my Intel-based Hackintoshes can boot Windows through OpenCore.

Very interesting. I might consider it.

 

[mm2margaret]

Well, @CaseySJ, as I said, I can boot Windows 11 through OC, and it seems fine, but its faster using F12. F12, one click and done (or one arrow move and enter and done).

To each his own.....

 

[canyondust]

Well, @CaseySJ, as I said, I can boot Windows 11 through OC, and it seems fine, but its faster using F12. F12, one click and done (or one arrow move and enter and done).

To each his own.....

I do the same and hide my Windows NVMe from OC by disabling RP09 via an SSDT. I like to keep those two worlds as separate as possible, if only for my own neuroses.

 

[jimbojingle]

Hi, both my Big Sur and Big Sur Backup SSDs are no longer visible to pick in the OpenCore 0.7.4 Picker. I have checked APFS Min Date & Min Version are set to 0 or -1 in APFS section of config.plist but still no luck.

Any ideas how to fix this?

 

[CaseySJ]

Hi, both my Big Sur and Big Sur Backup SSDs are no longer visible to pick in the OpenCore 0.7.4 Picker. I have checked APFS Min Date & Min Version are set to 0 or -1 in APFS section of config.plist but still no luck.

Any ideas how to fix this?

Try the following:

• At OpenCore Picker press spacebar, then select Reset NVRAM.
• When system reboots, click the Shutdown icon at the bottom of the OpenCore Picker.
• Then flip power switch on PSU to OFF for 10 seconds.
• Power back up.
• At OpenCore Picker, check if macOS boot options have returned.

 

[jimbojingle]

Try the following:

• At OpenCore Picker press spacebar, then select Reset NVRAM.
• When system reboots, click the Shutdown icon at the bottom of the OpenCore Picker.
• Then flip power switch on PSU to OFF for 10 seconds.
• Power back up.
• At OpenCore Picker, check if macOS boot options have returned.

Hi Casey, that didn’t work for me but I do get a Big Sur - Data icon appear.

 

[CaseySJ]

Hi Casey, that didn’t work for me but I do get a Big Sur - Data icon appear.

Oh no, I was afraid of that. The “system” volume on your SSD might be damaged. But before jumping to conclusions, is it possible for you to do the following?

• Option 1: At OpenCore Picker, press “spacebar”. Do you see an option to boot into Big Sur Recovery? If so, select that option.
• Option 2: If option 1 does not exist or does not work, remove the NVMe SSD and connect it to a working Mac or Hack if you have one. Then boot macOS and log in.
• Option 3: If you don’t have another working macOS system, no worries. Just install macOS to a spare SATA SSD. I always keep a couple of 128GB or 256GB SATA SSDs for such purposes. After this temporary installation is done, boot the system from this disk and log in.

Now:

• Launch “Terminal” and type:
• diskutil list and post the output.
• This will give us a good initial look into the state of all installed SSDs.

 

[deocder]

After 2 out of 4 passes. memtest is showing 0 errors.

Since replacing with the provided config.plist there have been no freezes in Big Sur after numerous hours of use and several sleep/wake cycles. Not sure if things are all good now so will keep monitoring.

Replacement RM850x PSU will be installed tonight in case the CX550m wasn't enough.

Thanks for all the assistance thus far.

This morning I found that the system had woken itself from a sleep state but appeared to be frozen. No monitor output. I forced shutdown with the power button but the internal LED's stayed illuminated (I have addressable RGB strips attached to each of the DLED_1 and DLED_2 headers). This is not the first time this has happened following a freeze. Previously frozen states have been while using the system and a hard shutdown has turned off the internal LED's.

The most significant change between my previous post and this one is that I plugged all of my external USB peripherals back in. All but 1 USB Type-A jacks are occupied, and I have no Type-C jacks occupied. These are the devices that were plugged back in:

• Logitech C615 webcam, Cable Matters USB card reader model 2020582, 2 Western Digital Passport 2 TB drives, 1 Elements 2 TB drive, 1 Elements 5 TB drive (externally powered), 1 Elements 8 TB drive (externally powered), 1 Seagate One Touch 5 TB drive
• All drives are Journaled HFS+ except for one which is Case-Sensitive Journaled HFS+

So I have observed 2 patterns for freeze states:

• Using the old config.plist and while using the system (all USB devices plugged in). Hard shutdown leaves the internal LED's off
• Using the old and new config.plist the system self-wakes from sleep (all USB devices plugged in). Hard shutdown leaves the internal LED's on

Here are my Energy Saver saver settings.