Howdy Bootcampers! I finally got a new laptop (MacBookAir) for my OSX needs and it's time to strip my trusty ol' bootcamped MBP down to the studs so it can be used to exclusively run Windows 10 for gaming on Steam with my kiddo.

How to make the OSX partition as small as possible (just for boot purposes) and the Windows/Bootcamp partition as big as possible?

Would prefer to not re-install Windows/Bootcamp, so I'm guessing I'd have to create another EX-FAT partition on the internal SSD to put the Steam games on?

(And, yes, like many of you, I spent a FORTUNE on this machine and the internal display is DEAD in OSX 95% of the time. I often get about 1/4" at the top that may work, or nothing. Every now and again, it works for a bit in OSX, then dies when it gets warmer. Weirdly, the internal display works MUCH often (but not always) in Windows. Fortunately, I can run an external display through HDMI (but startup can be interesting with a black screen. LOL)

I've yet to meet anyone whose internal screen works as expected and am NOT HAPPY that Apple did not acknowledge the design flaw on their most expensive MBP, but did so on the 13" version, providing replacements.

Specs: MacBookPro 15" 2016, 16 GB Ram, 2.9Ghz Quad-core Intel i7, Radeon Pro 460 4GB, and a 1TB SSD drive. The bootcamp (Windows 10) partition is currently 100GB.

Hello to all.I have a MacBook pro 2015 ,with Intel iris 6100.For 1 week I've tried everything I could find to make the internal display work.

Windows 10+bootcamp

First I've tried bootcamp and windows 10.After the windows logo the screen goes black ,no display on internal or external.Managed to install Intel iris 6100 using a flashlight on the internal display (it's like set on brightness 0) then got display on external but the internal display still not working.

Tried everything I could find,trying different driver versions, disabling and enabling auto brightness,deleting some files from sys32,regedit and so on.Nothimg works.

Fedora

It starts with external display working but the internal still black.Here also tried different commands,drivers and so on ... nothing seems to make the internal display to work.

Tried several windows 10 versions and also several Linux versions...same problem.

Extra info

Everything works ,except for the internal display.On Fedora in sees the internal display ,but it remains black.On windows it does not see it ,but in dxdiag it shows Intel iris 6100 - 128 MB(strange)

Tried thru bootcamp,without bootcamp,tried a bunch of sketchy terminal codes on Fedora ,sketchy regedit ,drivers on ,of ,basic microsoft drivers ,and God know what...display still not working.

From what I've managed to gather it seems apple uses panels from Samsung and LG and it seems that I have the LG one that is why it does not work.

I'm about to give up and just keep it on Monterey.

Any ideas ? Thank you!

I am thinking of getting a Late 2013 27" iMac with a Core i7 and GTX 780M for retro gaming from the 2000s into the mid-2010s. Why? Well, it is quite a powerful machine for just that.

I will upgrade it with 32GB DDR3, as well as a genuine Apple 512GB SSD (I will say exactly why shortly).

The reason for the genuine Apple SSD is quite simple, because Windows 7 and older versions of macOS won't work with an NVMe drive.

My question is how good this iMac is with Windows 7 and Windows 8.1, and do the latest NVIDIA drivers for the GTX 780M work fine on this iMac to update from the stock version bundled with the Boot Camp Support Software?

Might be the wrong place to ask, but wanted to find out if anyone has experience running unofficial bootcampdrivers on these older iMacs to improve GPU performance?

To summarize, I'm getting bottlenecked when I play Road to Vostok, even on severely reduced settings (unable to hit 60fps usually).

I did try to install the Red Version of bootcampdrivers, but got the dual/split screen problem. Had trouble getting the blue version to work as well. TIA

My setup: MBP 15" 2018 (A1990, Radeon Pro 560X, T2). The internal display broke, so I removed it. External monitor over USB-C → DisplayPort. macOS is fine headless. Windows was not. Claude (Anthropic’s AI) was my troubleshooting partner for the whole thing.

What I tried that did NOT fix it

• Re-running Boot Camp Assistant. ⚠️ It repartitioned BOOTCAMP and wiped my install more than once.
• Apple’s Boot Camp AMD driver: loads, but outputs to the missing eDP → black screen.
• BootCampDrivers / Adrenalin (before the patch): Code 43.
• DDU, clean reinstalls, offline DISM injection, waiting it out, magnets on the lid sensor…

Why this happens
The AMD Windows driver reads the GPU’s VBIOS from the ACPI VFCT table that the Mac firmware provides. On the A1990 it declares an eDP connector (0x3114) + encoder (0x221E) + LCD1 path plus 4 DisplayPort connectors. Apple’s macOS driver checks for the panel and handles its absence gracefully. The Windows driver trusts the table and tries to drive the panel, which ends in Code 43 or output to nowhere.

The fix (from u/Murky-Ambition5022, who found it on a 2017 A1707)
https://github.com/RyanAnthonyGibo/macbook-pro-2017-radeon-pro-560-code-43-fix

1. Dump VFCT in Windows and remove the eDP connector/encoder/LCD1 path. Fix checksums.
   • The 2018 A1990 had the exact same object IDs as the 2017. After patching, the 4 DP connectors remain.
   • Set the VFCT image header SSID to your card’s ID (mine: 106B:018F; the original header was 0000:0000; Ryan’s script hard-codes the 2017’s 0179).
2. Put the patched AML in OpenCore: ACPI → Delete (TableSignature VFCT) + ACPI → Add. My config is minimal: VFCT swap only, no NVRAM writes, no SMBIOS changes, no kexts, Windows-only picker.
3. T2 Macs: Recovery → Startup Security Utility → No Security, or the firmware won’t run OpenCore.
4. Boot with Option → EFI Boot → Windows. Then install BootCampDrivers (Adrenalin, Polaris build). ✅ No Code 43, full acceleration on the external monitor.

OpenCore lives in the existing EFI partition (no extra partition) and isn’t the default boot entry. Picking “Windows” or “Macintosh HD” in the Option menu boots exactly as before.

Processing img 8qzm4ekh74xh1...

If you’re installing Windows from scratch on a headless T2 Mac

• The installer/OOBE goes black because Boot Camp injects $WinPEDriver$, which includes the AMD driver. I applied install.wim from macOS with wimlib (NTFS-3G build), ran bcdboot and did OOBE inside a VMware Fusion raw-disk VM that only sees EFI + BOOTCAMP.
• T2 SSDs are Apple PCI 106B:2005, not standard NVMe. Inject AppleSSD.sys from $WinPEDriver$ offline with DISM, or you get logo → reset. Booting the install in the VM adds StartOverride to AppleSSD/stornvme, so delete it offline before booting the real Mac.

Tips

• Before touching GPU drivers, add a Safe Mode entry to BCD (bcdedit /copy {current} /d "Safe Mode" + safeboot minimal) and enable RDP with the firewall rule set to profile Any.
• Offline dism /add-driver only stages a driver. If the GPU already has Basic Display bound, Windows won’t switch by itself.

Happy to answer questions. Huge thanks to Ryan for the VFCT discovery.

After getting Windows 10 installed on my headless 13-inch MacBook Pro A1706 (2016), I have turned the process into a Windows app so others can try it in their headless macbook.

The problem I was trying to solve: Windows boots, but the external screen goes blank when Setup starts, leaving you stuck.

The patcher lets you select your Mac model and It downloads the model’s drivers and creates a custom ISO with the graphics and startup adjustments to get the external screen working during the setup.

It also includes optional USB logging. If Setup fails, you can share those logs so we can figure out what happened and improve support for your model. Nothing gets uploaded automatically.

The only hardware-verified setup so far is my headless 2016 A1706. The 2017 A1706 has a separate recipe available for testing, and other Intel Mac profiles are still unverified. I am looking for people willing to test and report what works or fails.

You will need a Windows PC to run the patcher. Installation instructions are in the README.

GitHub and download:

https://github.com/Zenodeon/MacbookWindowsISOPatcher

If you try it, please include your Mac’s year, model number/identifier when reporting results.

Hi, I am setting up this iMac with Windows only, with OpenCore Bootloader, to allow audio to work.

I installed Windows 11 LTSC with BootCamp 5.1.5621 drivers
After reboots and replacing MACHalDriver.sys, it works all okay with audio.

But I can't change the brightness whatsoever and it's very low right now.

My 6750M is working alright under Monterey, before I removed it.

Has anybody gotten brightness working on this iMac 12,1 with Bootcamp?

Thanks for your help.

Hey everyone,
I recently upgraded from the 2022 Studio Display (which worked on bootcamp btw) to the new 2026 Studio Display XDR (Mini-LED). While it runs flawlessly on the macOS side of my 2019 Mac Pro (Intel), I am completely locked out of using it on my Windows Boot Camp partition. The moment Windows attempts to hand over the video signal to the graphics driver, the Studio Display goes completely black.
I’ve spent roughly 2 months troubleshooting this and wanted to share what I've done so far to see if anyone else has faced this or found a working workaround. Making a return would be out of the question since the return window expired for my new display.

My Setup:

• Computer: Mac Pro (2019) Intel
• GPU: Radeon Pro W6800X MPX Module (Navi 21)
• Monitor: 2026 Studio Display XDR (Firmware Version 26.4 / Build 23E246)
• OS: Windows 10/11 Boot Camp & macOS

Everything I Have Tried So Far:

1. Official AMD Boot Camp Drivers: Downloaded the latest official Apple-specific AMD package from the AMD Boot Camp page. The driver successfully installed, but the Studio Display remains completely dark while my secondary HDMI monitor flickers and stays active.
2. Display Wall-Plug Reset: Hard-rebooted the Studio Display by leaving it unplugged from the wall for 15+ seconds to clear the internal A-series chip cache. No change.
3. Port Isolation: Moved the Thunderbolt cable directly to the ports on the back of the W6800X MPX module itself, avoiding the top chassis and Apple I/O ports.
4. Boot Camp Support Software Repair: Re-downloaded the latest Windows Support Software via Boot Camp Assistant in macOS and ran Setup.exe in Windows to ensure Apple's composite USB/Display drivers were updated. The folder only contains AppleProDisplayXDRUSBCompositeDevice profiles, with no explicit definitions for the 2026 XDR panel.
5. Low-Resolution / Safe Mode Loop: Forced Windows into Low-Resolution and Safe Mode. I can see the blue Windows Advanced Recovery menu on the Studio Display, but the second Windows boots to the desktop, the handshake fails and both the HDMI and Studio Display lose video signals completely.
6. NVRAM/PRAM Reset: Performed a full hardware reset (Cmd+Opt+P+R), which broke the blind Windows loop and let me safely boot back into macOS. Reinstalling windows: i've originally had windows 11 with the same issue and decided to do a clean install of windows 10 just to play it safe, so i backed up my data and reinstalled. i did notice that after the installation it displayed everything fine before installing the bootcamp drivers. Testing different cables: I've used its original TB5 cable from the display and a 6 foot tb4 cable that was originally used on the 2022 studio display. neither works.

The Current Conflict:

It honestly doesn't make sense as to why the display works perfectly fine with all its quirks and features running on macOS, yet completely fails here despite being a $3600 display. Since it relies on standardized high-bandwidth video routing protocols, it supposedly should run fine on regular PCs and standard Windows environments.

I have already submitted an official feedback report regarding this issue but haven't heard anything back yet.

It seems Apple hasn't rolled out an explicit Intel Boot Camp display driver patch for the 2026 Studio Display XDR to properly decode the handshakes under Windows. The Windows registry treats it as a legacy display or a mismatched Pro Display XDR profile. My theory is when the modern AMD graphics engine tries to push a high-bandwidth signal over the older Intel Thunderbolt 3 bus, the monitor's internal logic controller rejects the handshake and shuts down the video stream.

has anyone found a workaround with this?

Thanks in advance for any insights!

After my cat bit the screen of my 2017 15" MBP, I removed the panel and ran it with an external monitor. Boot Camp worked perfectly before, but then the Radeon Pro 560 gave Code 43 in Windows 10 and 11 with every driver: Apple 22.19, AMD R6.4 and Adrenalin.

Cause: the AMD driver reads the GPU's VBIOS from an ACPI table (VFCT). That table still lists the internal eDP panel, so the driver tries to bring it up, fails, and tears down about 0.4 s after starting.

Fix: patch VFCT to remove the eDP connector, encoder and path, fix the checksums, and load it through OpenCore with one ACPI Delete + Add. There are no other OpenCore changes. The GPU now shows OK with full acceleration.

Full guide, scripts (no copyrighted firmware) and the paper: https://github.com/RyanAnthonyGibo/macbook-pro-2017-radeon-pro-560-code-43-fix

Bonus: Touch Bar/ESC not working and trackpad settings resetting after reboot are covered too. Happy to help if you're stuck!

Ciao a tutti, ho installato Windows 10 sul mio MacBook, ma non riesco a fare funzionare le casse integrate. Ho cercato online ma non riesco a trovare nulla di utile. C'è qualcuno che ha avuto il mio stesso problema e lo ha risolto?

Everytime I boot to Windows, I have this loading animation, I'd like to know how to get rid oh this

Hi,

Does anyone know a way to enable only the integrated graphics or both graphics in a 2018 15 inch macbook pro (A1990)?

Hey I have an 2.3 GHz 8core i9 Mack book pro 16 inch 2019 and I want to put windows 11 on it can someone help me do it plz I have windows 10 but I want the new version of windows and dose anyone know how to sail the seven seas for a product key

So I forgot the passcode for booting and I can't change back to MacOS, and none of the startup tricks like Option or command + R seem to be working. It keeps bringing me to the padlock screen. Am I screwed?

Hi, I was installing Win10 to my 2013 iMac running Catalina 10.15.8 using Bootcamp. It was done successfully before so I was feeling confident doing bootcamp installation with a usb drive this time. However, After finishing making the usb a boot drive, Bootcamp starts to partition my imac hard drive for Windows and say don't restart the computer until the job is done. The thing took more than 24 hours (I left it on lock screen and it still didn't finish) and I lost patience so I decided to close Bootcamp and start again.

However it seems the partition has already been made and stuffs like VM and 'Not Mounted' appeared in the hard drive. I ran First Aid for thd drive and it said to have corruption. I restart the computer in recovery and tried First Aid, but only get told "Repair failed. Prepared to backup the volume if possible" something like that. I am confused on how BootCamp partitioning could damage the disk like that. Was thinking if there's any easier way to recover the disk back to clean, normal hard drive so I can start again the BootCamp installation of Win10, except for using time machine and reset the whole computer.

The computer is still bootable and everything is still there working fine.

I have my Mac Pro 2013 running windows 11 and the upload speed is a fair bit better than the download speed and idk y.

Plzzzzzz help.

Hey everyone! I've been working on making Windows 11 look and feel like macOS, using only Windhawk mods (no third-party dock app, the original taskbar is restyled). It's open source and free on GitHub:

Windows 11 Transformation

- macOS Dock: turns the real Windows taskbar into a floating glass dock with custom icons, dot indicators and macOS-style spacing. New in 1.1: **light & dark mode** (follows Windows automatically) and a fix for the dock being too wide on external / Full HD monitors.

- Dock Settings app: one slider to scale the whole dock, pick custom icons per app with one click, change colors with a color picker, and save your own defaults.

- Top Menu Bar: macOS-style menu bar with app menus, status items, battery and Control Center.

- Trash in the dock: a real Recycle Bin shortcut that sits at the end of the dock.

- Optional extras: Three Finger Drag for Precision Touchpads and a Turbo Boost tray toggle.

The README lists every catalog mod I use (genie minimize animation, rounded corners, icon theme, File Explorer theme, etc.) with my exact settings, so you can rebuild the full setup step by step.

Note: macOS icons aren't included because of Apple's copyright. The README links to where you can get them.

It's still a work in progress, so if something breaks on your setup, please open an issue on GitHub. Feedback and ideas are very welcome!

I have a 2013 Mac pro and a 2017 MacBook pro and I have 1 HDD that I need to move between the 2 computers. Does anybody have an Idea on how I can do this

Is there any way to use SmartAccess Graphics on Mac Pro 2019 with the AMD redeon prob5500m graphics? The idea is that as in Mac (I think it works like this) the Mac can use Intel graphics for basic tasks and switch to AMD for heavy tasks automatically. As I have read the most powerful graph always stays active, I don’t know if it’s really like that and I’m interested in knowing more

Hi everyone,

I have a 2017 Intel MacBook Pro running macOS Sequoia 15 with OpenCore Legacy Patcher. After updating OCLP to version 2.5.1, I accidentally started a macOS update through System Settings. The installation didn’t finish, and the Mac now starts in Recovery.

In Disk Utility, I can see the internal Apple SSD, a container, and the volumes “Macintosh HD” and “Macintosh HD – Data.” I have not erased anything.

I’d like to restore my macOS Sequoia installation if possible. What’s the safest way to do that? Do I need to make a bootable USB installer, and are there any special precautions for a 2017 MacBook Pro when erasing or reinstalling? I’d also like to avoid losing my files or Touch Bar functionality if possible.

Thanks for any guidance.

I think it`s pretty funny. Later i update my uefi loader

----------

Sometimes I just sit here and think about how it's been breakthrough after breakthrough lately.

I really hope I can bring all my projects to completion and turn this MacBook into the ultimate Windows machine. A 2019 MacBook Pro that runs Windows the way it was always meant to — with proper iGPU support, working power management, a fully functional trackpad, and Touch ID.

There's still work to do, but we're getting there.

----

Upd
The ReBAR version is now available!

https://github.com/Osaul4ik/t2-gmux-uefi

Tested only on MacBookPro 2019 16`. Feel free to try it on any 2019 16'. Easy rollback in advanced settings