MacBook Pro (16″ 2019) Does Not Recognize Correct Resolution

displaymacbook proresolutionusb

I'm having a rather annoying issue with my MacBook Pro 16" 2019 device since upgrading to macOS Big Sur. Every time I plug my device to my 4K monitor into the device (via USB-C to USB-C, or USB-C to DisplayPort), macOS will show a maximum resolution of 1600×900 but my monitor's recommended resolution is 3840 x 2160.

Photo shows the Display setting screen, with resolution of 1080p selected

I currently have a workaround to resolve the issue which is the following:

  1. I switch from 1080p resolution to 1600×900
  2. Un-plug the cable, and plug it back in again
  3. Then switch to 3840×2160

This process can be tedious and take a while to complete (between switching resolutions). Is there any solutions which people are aware of?

These are the details of the device and monitor

  • macOS Version: 11.2.3
  • Model: MacBook Pro (16-inch, 2019)
  • Processor: 2.3 GHz 8-Core Intel Core i9
  • Graphics: AMD Radeon Pro 5500M 4GB
  • Monitor: BenQ EW327OU

These are the things which I've done to date

  • I can't pin the issue on the monitor, as I've been using a MacBook Pro (2017) with the monitor for a week or so without a single problem.
  • Used ColorSync to repair any issues with the monitor profiles
  • Used various other cables such as HDMI, USB-C to USB-C and USB-C to DisplayPort.
  • Reset NVRAM and SMC
  • Re-installed macOS
  • I can't reproduce the error in Windows via Bootcamp, so I'm confident it's OS related.

Best Answer

There is an ongoing bug with Big Sur 11.1 and 11.2 where

USB-C ports to fail to recognize external monitors, rendering external displays unusable and unable to connect. This appears to be affecting both DisplayPort and HDMI displays connected directly and through hubs and adapters.

and

The second issue results in resolution issues with external displays unable to work at a full 4K 60Hz resolution, instead locked at 30Hz. In some cases, a 4K monitor is only recognized as a 1080p monitor.

So far there doesn't seem to be a fix from Apple.

Related Question