How to fix Surface Book 2 base docking problems

The Surface Book 2 is the best device I have ever owned. It's sleek, sexy, relentlessly powerful, and has impressive battery life. However, I have had my fair share of issues with some of its more unique features.

The Book 2, like its predecessor, has a detachable display, which comes with a few benefits. You can use the display separately as a tablet if you want to, but the most useful function here is the ability to reverse the screen, so you can rest it flat for inking, or set the laptop upright in tent mode.

When detached, the dedicated NVIDIA d-GPU becomes separated. The CPU and integrated GPU power the laptop from within the screen. It's this unique design that helps Microsoft get the different segments of the device so flat and so thin, but occasionally the Surface Book 2 will sometimes refuse to detect the d-GPU in the base, even when docked. Thankfully, it seems to be pretty easy to fix.

See Surface Book 2 at Microsoft (opens in new tab)

Check if your NVIDIA GPU is connected to Surface Book 2

If your Surface Book 2 has been struggling with graphics-intensive tasks such as games or certain types of editing, you might be suffering from phantom d-GPU syndrome. Here's how to check if your Book 2 is correctly seeing its d-GPU:

  1. Right click on the Start Menu.
  2. Click on Device Manager to open it.

  1. Scroll down and select Display Adaptors.

You should now be able to see both your Intel Graphics driver, and your NVIDIA GeForce d-GPU driver. If you can't see the NVIDIA d-GPU, you have a problem.

If you see the d-GPU but still think it's not providing juice to your games and apps, here's a separate article detailing how to force your programs to use the powerful NVIDIA d-GPU in your Surface Book.

Detaching, reattaching, and cleaning your Surface Book 2

The first thing to check is that your Book 2's display is properly docked with your PC, and that the connectors are adequately cleaned. Here's how:

  1. Disconnect all USB devices and power charging cables from your Surface Book.
  2. Close any programs you can find.
  3. Press the Surface Detach key. (See below.)

  1. Once it has turned green, and you hear a clicking sound, you can safely remove the display by gently pulling upwards.
  2. Locate the connectors as seen in the picture below.
  3. Use compressed air (opens in new tab) to gently remove any dust or lint from the sockets, or a soft cloth with a small amount of rubbing alcohol.

  1. Check to make sure no small magnetized metals or other small debris has become lodged in the socket.
  2. Gently place the display back on the connectors.
  3. Go back to Device Manager (detailed in above section) to see if your d-GPU drivers have reappeared.

Boot Surface Book 2 from the BIOS

Cleaning the connectors seemed to serve as a temporary fix for me, but what fixed it permanently was booting from the BIOS menu (thanks Joshua for the tip).

  1. Save all of your work, then press and hold down the power and volume up buttons on the top of the display for around 30 seconds. (After a few seconds, the Surface Book 2 will reboot.)

  1. Keep holding the buttons down until you see the Surface UEFI BIOS screen.
  2. You do not need to change any settings here. Simply click or tap Exit.

The Surface Book 2 will reboot, having refreshed some BIOS settings. Note that some login tokens for certain apps might expire as a result of this, but now your Surface Book 2 should be able to detect the d-GPU more reliably. You can also check the Device Manager to see if your d-GPU NVIDIA drivers have reappeared.

Surface Support

If none of these things fix your issue, you might need a replacement unit. Consult the guide below on how to get your Surface serviced by Microsoft.

How to get a Surface repair from Microsoft (opens in new tab)

More Windows 10 resources

For more helpful articles, coverage, and answers to common questions about Windows 10, visit the following resources:

Jez Corden
Co-Managing Editor

Jez Corden a Managing Editor at Windows Central, focusing primarily on all things Xbox and gaming. Jez is known for breaking exclusive news and analysis as relates to the Microsoft ecosystem while being powered by caffeine. Follow on Twitter @JezCorden and listen to his Xbox Two podcast, all about, you guessed it, Xbox!

  • My only issue with attaching my 13-inch SB2 is, on re-attach, it won't recognize the keyboard as the "Surface Keyboard". It reads as an unknown USB 3.0 device until I remove it from the device list, and reboot. The keyboard works for the most part, as does the trackpad, but I'm sure I'm missing some features while it's unrecognized. Once I reboot, and it's recognized, it normally stays recognized until detach, but sometimes it'll just randomly forget it again and I've got to go to settings, remove and reboot... Not a huge issue, but one that's there for the nit-picker in me...
  • Did you try the BIOS refresh method in the article? It might fix that too.
  • Ya know what? That may have done the trick! Put to sleep, woke up, still recognized the Surface Keyboard (usually did, but sometimes that would do it) 1st time detach, play around a bit, re-attach, still recognized the Surface Keyboard! That was the big test, now it's just a matter of time to make sure...thanks!
  • Thanks for finally posting about this. A little odd it took WC this long considering the issue goes back to at least January but better late than never. Can you check with your MS sources and get an official response? So far support has been next to useless and overall MS has been vague at best and legally negligent at worst. Check out the link below from the MS forums for the "full flavor". FWIW, the BIOS refresh has worked for me a couple times and each time it didn't occur again for a couple months. When it did, it was after a Windows Update, not after detaching the screen.
  • I tried all of these fixes. Only the last one worked for about a day then back to the disappearing gpu. So I took it to the Microsoft store to see what they could do and they replaced it for free. They said it’s a known issue with a first batch and nothing they could do to fix. My new one has been solid. Thing is, it never happened until the 1803 windows update.