I was able get my dual screen configuration with a 2018 MacBook Pro running 11.2.3 + clamshell closed working by uninstalling BigSur versions of displaylink and then installing 5.2.5 (https://www.displaylink.com/downloads/file?id=1636) again. Looking forward to getting the updated version when they support Intel Macs - this seems like a big miss, I assume most of the customer base is still Intel based. Amphetamine also worked for native but keeps the third screen going which causes trouble with going full screen in remote sessions (e.g. Citrix) for corporate environments.

Hi everybody - disappointed as the rest of you about the lack of clamshell support on Intel Macs. I read below about using the 5.2.5 driver (which I was using before a machine rebuild this week). It worked fine before (I was on Catalina and upgraded to Big Sur), but installing 5.2.5 straight onto Big Sur does not seem to work for me. Any ideas?

Jd's work around for big Sur intel Macs worked for me! Thanks! But I still would like to get this feature though. Don't like relying on third party applications. Please fix this.

Hi @Alban - what is the expected date of release?

Fix needed! Awaiting eagerly!

@Jason - you don't have to use triggers, but I feel that it makes the app more convenient. Try turning amphetamine on manually (App icon in Menu bar > Start a session) and make sure that "Allow display sleep" is checked and the other two checkboxes are unchecked.

@Alban Rampon, while we understand that development is ongoing, I think I speak for everyone when I say that we would like an update that is more comprehensive than a single sentence.

I tried downloading the Amphetamine app as JD (previous comment) suggested, but very little luck on that front. I spent 2 hours messing with the "triggers" in the preferences but it did not work out as expected - the screen would revert back to normal settings (pre-trigger) once I turned the webcam on. Im not sure if having a webcam connected triggered it to glitch. It would just flicker on and off every 15 seconds prompting me to log in to my mac.

I am running a MacBook Pro (late 2015) 15-inch i7 core (by no means a "slow" mac) and downloaded the latest display link driver (1.3) and did the complete install. The clamshell mode does not work in this mode. I have to have my MacBook open and it allows me to have 2 external monitors + the laptop monitor. The whole point I purchased this hub was for the easy of connectivity in clamshell mode. I am impatiently waiting for an update to this issue.

Any updates on this fix?

The workaround of Tycenjmccann unfortunately does not work for me.
While the cmd+alt trick indeed duplicates only one of the two external monitors, after closing the lid both monitors go black every 10-15 seconds for 5 seconds.

I did find another workaround which does work for me (mid 2015 MacBook Pro with macOS 11.2.2):

I uninstalled DisplayLink Manager 1.3 and installed legacy release 5.2.5. After a restart the MacBook can now stay in clamshell mode while my two DisplayLink monitors (Philips 241B) work without interruptions over USB.

Tycen workaround works for me bump

A decent workaround I have been using is to Mirror your main display (i.e. the book) to one of your monitors, then when you close you have a "mirrored" display and an extended display.

Not ideal but it does give the same feel as if clamshell was working properly.

To do this you go to the Arrangement tab, then cmd + option and drag the external display you want mirrored over the main display and drop.

Awaiting fix on this!! Any updates regarding the timeline?

JD's solution below works.

I am using a Plugable USB-C Dual 4K Display Adapter with Ethernet (USBC-6950UE) plugged into a USB-C port of my OWC 14-Port Thunderbolt 3 Dock with my 13" MacBook Pro M1 (macOS Big Sur 11.2.2). Clamshell mode works flawlessly. with DisplayLink manager v1.3 with both external monitors connected to the Plugable adapter..

Commenting on this to keep up with when this is fixed.

is that any update regards this isso?

Hey all, I just wanted to reiterate a fix for this on Intel-based Macs running Big Sur. Here's what you do:

1. With the latest DisplayLink software installed, download Amphetamine from the app store.
2. Once it's installed go to Amphetamine > Preferences > Triggers.
3. Check "Enable Triggers" and create a new trigger that launches when you have 1-2 external monitors attached, depending on your use case.
4. "Allow display sleep" should be CHECKED, and "Allow system sleep when display is closed," should be UNCHECKED
5. Connect your external monitors
6. If you have two monitors, use the DisplayLink software to set ONE to mirror your laptop display.
7. If you have one external monitor, just set it to mirror your laptop display.

This worked for me.

However, I'm wondering if anyone knows if this is bad for my laptop? I've checked and it seems that the display actually is not turned on when the lid is closed, but I'm not sure.

Thanks!

Any update about this issue ?

Hi, I have a 16" MacBook Pro 2019, I'm on Catalina 10.15.7. I've just installed DisplayLink Manager 1.3, and can confirm is still not working. When I close the lid, the built-in screen is still displayed in the Display arrangement options of the MBP. If I use it in this way, some windows still appear in that screen and it's kind of annoying. I was hoping that when closing the lid, there were just the external monitors displayed in the arrangement options.

Actually I've just recently bought this dock, so I'm not sure what would be the behavior when I'm on clamshell mode. Should I see only the external monitors I have connected to the Dock?

Currently when I close the lid, the two external monitors I have connected sill works along with all the connected USB peripherals, but also is the built-in screen of the MBP. If I move the mouse in the right direction, I still can reach the built-in screen, if I drag a window I still can put it there. I was hoping when I start the clamshell mode that the built in screen disappear entirely from the display arrangement so I can use only my two external monitors.

Also waiting for this to be addressed.