One command to resolve Remote Desktop bug

Jan 25, 2019 12:54 GMT  ·  By

Microsoft recently rolled out Windows 10 version 1903 preview build 18323 and because we’re getting closer to the moment the next major OS feature update is finalized, the focus is mostly on refining bugs and improving performance.

While new features are still being added, do not expect too many breaking changes to be revealed in the next couple of months, as Microsoft absolutely needs to make sure Windows 10 version 1809 runs flawlessly.

Especially after the October 2018 Update blunder, that is, as this particular release turned out to be the buggiest Microsoft update in a long time.

But as every new build, Windows 10 build 18323 comes with some issues of its own, including black screens that could be experienced when trying to use certain features of the OS.

Basically, Microsoft acknowledged two different black screen issues in this new build.

First and foremost, there’s the one hitting Windows Sandbox. The company explains that some users may see a black screen when trying to launch the Sandbox, and because a workaround does not exist just yet, the only official solution is to wait until a full fix is issued.

However, I’ve seen users claiming that the Windows Sandbox black screen was resolved after turning this feature off and back on, so you could try this to see if it makes any difference.

For starters, Windows Sandbox is a new Windows 10 version coming to users with version 1903 that allows us to launch apps in a closed and secure environment. More like a native virtual machine solution, Windows Sandbox would block any malware from reaching your data, with all the content deleted when closing the protected environment.

Turning Windows Sandbox on and off

Then, there are black screens that could be experienced when using Remote Desktop, DisplayLink, or Miracast. Microsoft says this only happens if you are using an AMD or NVIDIA driver and that a fix is already in the works. However, a workaround does exist in this case, and it comes down to creating a new registry key that would resolve the problem.

While this typically involves launching the Registry Editor, you can do the whole thing from an elevated command prompt (click the Start menu > type cmd.exe > right-click > Run as administrator). In the new window, type the following command:

reg add HKLM\Software\Microsoft\Windows\Dwm /v EnableFrontBufferRenderChecks /t REG_DWORD /d 0 /f If you did this correctly, the black screens should no longer be experienced. You can create a backup to make sure that nothing bad happens, but given it all comes down to a registry key, you should be safe anyway.

Black screens have become quite a common problem in Windows 10, and some of those upgrading from older versions probably know this very well. Previous Windows 10 updates were hit by black screen issues that left them with little to no option, so it’s critical for Microsoft to make sure that everything is working as expected.

The command to resolve the black screen

This build itself corrects such a problem, with Microsoft explaining in the official release notes the following:

“We fixed an issue on certain devices that could sometimes result in the screen staying black on boot until CTRL + Alt + Del was pressed.”

Windows 10 version 1903 is projected to be finalized in March, and as it happens every time, the RTM build will be shipped to insiders first once it is signed off. The public rollout should then begin in April, but given the October update blunder, expect the company to adopt a more cautious approach and to take more time to make sure everything’s running correctly.

Photo Gallery (3 Images)

The new build is available for users in the Fast ring
Turning Windows Sandbox on and offThe command to resolve the black screen
Open gallery