Post your current EFI for reference.
Perhaps the compression is preventing OpenCore from finding the kernel but I'm not sure. If Garuda only works through GRUB you could chainload OpenCore through GRUB and just use OC to load macOS. That's another option.
Is Garuda completely missing from the OC menu or won't it load when selected?
Then you should replace the Ext4Dxe.efi with btrfs_x64.efi from the OcBinaryData or rEFInd drivers.
Your EFI looks fine just change the drivers mentioned above and try again.
Hi @lookattosh22 I have the same model laptop with the same specs so I have some suggestions.
USB port injection with USBInjectAll.kext or USBPorts.kext requires the EH01 and EH02 renames.
The _OSI to XOSI rename must be used with SSDT-XOSI.aml to simulate a specific Windows version...
Which is to be expected since Windows will add itself to it's own boot manager when another version is already installed.
You'd have to install both versions on separate disks with all other drives disconnected so that no existing EFI partition with the Windows Boot Manager or anything else is...
OK, sounds good. Two things I can suggest right now.
It appears you have discrete and integrated graphics enabled on your system. I recall that Windows may hang - at least when booting through OC - in this configuration. You might want to disable the integrated video, if that's not your primary...
Understood, but that's not my question. Did Windows still boot through OC after you updated it but before the upgrade to Monterey?
I want to determine whether the OC update or the Monterey upgrade is responsible for the Windows issue.
Default or a specific model will provide a measure of security but it's up to you.
You should be fine and that's what I use on my Haswell machine to run Monterey. Power and CPU related issues should be avoidable as long as you don't do something like use a desktop SMBIOS on a laptop.
I believe you should get updates with it disabled as SIP is more relevant. You could set SecureBootModel to Default or one of the model and version specific values listed in the Dortania guide below. That enables OpenCore to verify boot.efi when loading it...
The ACPI files and config.plist look fine which isn't surprising since Windows was working previously. It appears you updated OC earlier today. If that was before the Monterey upgrade, did Windows still work after doing that? Did you clear the NVRAM? Any hardware changes at all?
Hi @eqcq let me ask a few questions for clarification. Is Windows on the same disk as macOS or a different disk? Were you able to boot Windows from OC before the upgrade?
I'd also suggest attaching a zip with your current EFI contents. Your ACPI patching may need adjusted for Windows compatibility.
@Henties regarding this issue, which we have spoken about on another forum, have you tried your previous fix from a few years ago? Given the previous situation a kext development issue seems unlikely.
I downloaded the manual for your motherboard but the BIOS section doesn't provide any detail on the settings at all. So that's not going to help us unfortunately.
You'll need to do the following. Power on your system and press the Delete key to access the BIOS setup when you see the MSI splash...
I assume that means that EFI partition was created automatically by Disk Utility when you formatted the drive as HFS. Correct?
Have you copied, moved, deleted or modified any files in the EFI partition and associated folders using the UEFI Shell? Anything other than the attrib command or the...