Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
On my side I always used Windows 10 Pro, properly activated. The issue that I'm dealing with is after boot picker selection, my screen gets stuck at Windows logo, which is known to be related to GPU drivers. The thing is, everything works for a while well and all of the sudden Windows goes dumb frozen. Everything was working fine for months, last time I accessed Windows was 3 weeks ago.
tried with the pro image. same stop code, it happens right after the accept the eula or whatever.
You may have to start Bootcamp assistant and install only Bootcamp drivers to the usb from BS because Bootcamp stopped working for the cMP after HS but it works again in BS.
Last edited:
Has anyone had any issues in updating betas in Big Sur. “MSU 1013” failures within the last few public betas but so far only with beta releases. OTA safely exits without changes made. Cannot find away around it with Opencore. “MSU 1013” could cause issues in future updates.
Last edited:
You need to find a way to replace the driver with the attached. It is found in 2 places:
Code:
/Volumes/<VolumeName>/Windows/System32/drivers/BCMWL63a.SYS
/Volumes/<VolumeName>/Windows/WinSxS/amd64_dual_netbc64.inf_31bf3856ad364e35_10.0.21301.1000_none_d5966702e569443d/BCMWL63a.SYSOr you can just delete the driver in both places so you are able to boot.
You can download this Windows PE iso and put it on a Ventoy USB disk and boot from it to have R/W access to that partition.
Try booting with RefindPlus it has Windows certificate protection as well (you have to enable it). That way you can confirm whether the issue is with the Windows drivers or OC.
Last edited:
What is the related OC setting? I want to make sure is set properly in my config.
I don't thing it will be in the settings, but rather in the code. But first you need to find out if there is any difference in the behavior.
i'm a bit confused by Ventoy. should i be installing something? does this replace windows iso USB i have already? this is just to edit my C drive?
If it works 3 weeks ago, you may downgrade OpenCore back to 0.6.5 to check if that make any difference.
If still can’t boot Windows, then it means not because OC 0.6.6 cause the issue
That's what I thought but was worth a try either way.
I've turned on debugging but can't seem to find the output log file in any of the EFI directories. I was hoping to generate this before uploading a bug report in GitHub. This is what I have set in OC config.plist:
For target, I used the following:
0x01 - enable logging
0x10 - enable UEFI variable logging
0x40 - enable logging to file
Converting to decimal gives me 81 but can't find the file anywhere. I even went to /var/log to see if perhaps it was placed there, but no luck.
OC boot log shows it's actually logging.
Last edited:
Setting the Target value to the wrong value can have bad implications.
Why muck around with manual changes when you are using MyBootMgr which comes with an app that will switch Debug Mode on, take care of changing all the files that need to be changed and set your OC config to the correct value?
Nothing wrong with doing it manually btw. Just that you need to make sure all the changes are in place.
There is a guide here: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html#file-swaps but do not go above 65 for "Target" on a real Mac as that is written for hackintosh.
Why muck around with manual changes when you are using MyBootMgr which comes with an app that will switch Debug Mode on, take care of changing all the files that need to be changed and set your OC config to the correct value?
Nothing wrong with doing it manually btw. Just that you need to make sure all the changes are in place.
There is a guide here: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html#file-swaps but do not go above 65 for "Target" on a real Mac as that is written for hackintosh.
Last edited:
Understood but even with debug mode on via MBM, I couldn't find the logs. Where are they supposed to be saved?
Ah, it's that log file which is saved as a text document. I was thinking it was going to be a different file or perhaps multiple files with a .log file extension.
From the manual: "This option will ensure GOP and UGA, if present, are available on the console handle."
Means if both are present. I suppose they could be clearer.
He doesn't have GOP present so the code would have returned early.
EDIT: Mix up with UGAPassThrough.
I see what you mean. Can't recollect exactly now without rechecking but it doesn't work as the docs imply there.
Implemented this in RefindPlus and was a source of some confusion at first. It is GOP specific IIRC.
Last edited:
Yes, the wording is ambiguous. Simply adding the word "both" would fix this...
@amstel78, is the 1st stage boot screen missing on a macOS Mojave installation as well? I wonder if it could be macOS-related. Certain versions behave strangely: On the Mac Pro 5,1, I've seen strange things with the 1st stage boot screen in Yosemite, and more recently in Big Sur.
Last edited:
This is just for creating Windows PE bootable USB so you can manipulate files on the Windows partition. I believe you can do that with a Linux live USB. The benefit of using Ventoy is that you don"t have to expand the ISO just drop it inside.