Why can't OC boot windows 10?

[calmesal]

I have a perfect running dual boot system on my HP EliteBook 820 G3. Windows 10 on M.2 HD and Monterey on SSD HD. When I try to boot windows from OC meny picker it spin the windows wheel and and restart.

I tried almost every tip and guide I have found but nothing helps.

 Is this possible? If yes, can some one try to figure out what is wrong with my config.plist.

Clover can boot windows without problem.

I chose botting disk by F9.

config.plist.zip

Edited November 26, 2021 by calmesal

[Allan]

OpenCore will injetc all the ACPI data in all OSes.

 

To avoid such problems, you can press F11 or any boot key to proper boot Windows.

 

But on Laptops, the best choice is Clover

[calmesal]

50 minutes ago, Allan said:

OpenCore will injetc all the ACPI data in all OSes.

 

To avoid such problems, you can press F11 or any boot key to proper boot Windows.

 

But on Laptops, the best choice is Clover

Yes it does. I wonder why the OC team can't do some setting to avoid this.

I have tried Clover but faced som random sleep & wake issues.

[Allan]

Yeah that's a pity, all of us want this feature. 🥲

 

But for fix these sleep issues, you can run this commands:

sudo pmset autopoweroff 0
sudo pmset powernap 0
sudo pmset standby 0
sudo pmset proximitywake 0
sudo pmset tcpkeepalive 0

 

[Baio77]

NOT good if you use Opencore, as for files you use in ACPI. Opencore does NOT like the same methods used with Clover. Opencore is very invasive with other systems and new ACPI patches are needed which avoid many Rename.

Edited November 27, 2021 by Baio77

[Avery B]

Device renames generally aren't needed. Renaming the EC especially is basically guaranteed to break windows.
Whatevergreen will do those automatically in macOS, and you can just create a fake EC device which macOS is fine with.
IRQ patches are generally fine with windows, same with battery patches (but many of those don't need to be done with ECEnabler since it will fix regions greater than 8 bits for you).

You can always use "If (_OSI ("Darwin"))" to change behavior in ACPI.
For reference, I run OpenCore on my Lenovo X1 Extreme, and am able to boot Windows, Linux, and macOS all from OpenCore.
Most of the SSDTs are derivatives of the examples in the OpenCore docs, which does check the OS if you want examples on how to do that.

 

[Baio77]

https://github.com/5T33Z0/OC-Little-Translated Here is everything you need to be able to manage OC in the best possible way. Obviously it is not a guide for beginners, also given the complexity of the IASL world.

EFI.zipTest this in USB if start ioreg .

This EFI is old it should be improved further by inserting ECEnable.Kext and removing the ACPI and config patches.
Try this in case we improve it further

Edited November 27, 2021 by Baio77

[Guest 5T33Z0]

In OpenCore, if you use renames which change method and device names or values used within these devices or methods, they need to be paired with additional SSDTs that pick up on these changes and limit them to macOS. Combine renames with "count" and "base" parameters to limit the reach of a rename to only specific devices or methods inside of a device.

 

Additional SSDTs need to scope into this device and/or method and define which parameters should be changed for macOS and what else to do if you are not using macOS by and if _OSI switch, as mentioned before.

 

In other words you need to correct all SSDTs which do not contain the "If (_OSI ("Darwin"))", ELSE construct.

 

Otherwise you need to use Clover, since it injects ACPI changes into macOS only.

 

 

[MaLd0n]

avoid opencore into windows with (_OSI ("Darwin")) or not

avoid a bunch of ssdts and acpi renames, u can use only one full patched DSDT and inject all devices, removed unused devices, etc, etc

clover and opencore have support to override tables

u can hide windows on boot picker and use bootkey to boot into windows

https://www.olarila.com/topic/13019-hackintosh-dual-boot-with-opencore-with-full-acpi-and-real-vanilla-solution/

[btwise]

We can modify the source code yourself and completely skip the ACPI injection for Windows. I have been using it