RDP Black Screen

RDP Black Screen KB ID 0001840

Problem

This problem has jumped up through various iterations of Windows operating systems. You attempt to RDP to a machine; it connects but you simply get a black screen.

 

RDP Black Screen Solution

Over the years various ‘hotfixes’ were known to cause this, but before proceeding make sure both the machine you are connecting FROM and the machine you are connected TO are fully patched and updated.

Common troubleshooting dictates that your first step is to see if you can replicate the same problem from another machine, and if possible, from a different OS. below I’m attempting the same from my MacBook and getting the same result.

 

If something is happening on the target that is simply preventing the desktop from showing press CTRL+ALT+END, or CTRL+ALF+Fn+END (depending on your keyboard). Hopefully you should be able to now launch Task Manager > New > Run New Task > Explorer.exe > OK.

You can also try disabling ‘Persistent Bitmap caching’. On the Experience tab of you rdp dialog.

In the same dialog on the Display tab also try some low resolutions in case the target machine is confused about what to display on your remote session.

If it’s still not working the next most likely culprit is a display driver, Either update it or roll it back to a known good one, try this n the source and target machines. Note: if you see something like this – then the target machine may just need its VMware tools updating.

Finally try using a different RDP client for windows there’s the Remote Desktop Connection Manager, and on a mac theres the Microsoft Remote Desktop app.

Did none of these work for you? or if you have a better solution post it below and Ill update the post accordingly.

Related Articles, References, Credits, or External Links

Remote Desktop Services – Connection Errors

Windows – Black Screen Of Death

 

Windows Server 2012 – Install Error

KB ID 0000618 

Problem

I thought I’d spin up Server 2012 today, and as usual with all new OS’s I run them up in VMware Workstation to take a look (I’m running Workstation 8.0.3 build-703057).

As soon as it started up I was greeted by this.

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D
Parameters:
0x000000000FEBFBFF
0×0000000020000800
0×0000000000000000
0×0000000000000000

Below is information for VMware Workstation and ESXi 5

Solution

For VMware Workstation

1. In my case it was simply a BIOS setting that needed to be enabled. Enter your system BIOS and locate a feature called Data Execution Prevention, (or No Execute Memory Protection).

2. Enable that setting, then ensure you shut the machine down then manually power it back on again.

Additional Points to Note when installing Server 2012

Make sure on the properties of the VM > Hardware > Processors > Tick Virtualize Intel VT-x/EPT or V/RVI (Note: Virtual support should also be enabled in the host machines BIOS).

VMware Workstation – Error – “Virtualized Intel VT-x/EPT is disabled”

VMware Workstation likes to automatically install VMware Tools, Sometimes Server 2012 does not like this and sits with a black screen that will flash blue when you click on it. So to Stop it Installing VMware Tools, Options Tab > VMware Tools > Select Manual. Note: you can always snapshot it and then manually install it later it you want to test. This has been a problem since the early releases of Windows 8.

Solution For ESXi5

1. Here’s the same problem on an ESXi 5 host.

2. Before you do anything you need to be at ESXi 5.0 U1 for Server 2012 to be supported (That’s build number 623860 or better).

3. However in this case the problem is the same as above, The server in question was an HP Proliant ML 350 G5. Boot the server and press F9 to enter the RBSU > Advanced Options.

4. Processor Options

5. Enable ‘No-Execute Memory Protection” > Exit and save settings.

6. And now we are good to go.

Follow up

04/07/12 Email from Simon Reindl:

I had to update my Bios as InsydeH2O does not offer any tweaking options, It is using Compal Bios (previous 9, now 10 – downloaded from Compal.com. It is using InsydeH20 BIOS on a Compal motherboard. It is a custom build.

 

Related Articles, References, Credits, or External Links

NA

Windows 8 (Server and Client) Black Screen (Post VMware Tools Install)

KB ID 0000587 

Problem

I’ve seen this on both the Windows 8 (Consumer Preview), and the Windows Server 8 (Beta), whilst running them in VMware Workstation 8. They install fine, but if you install the VMware tools all you get is a black screen.

This is because the SVGA Driver than VMware Tools installs Windows 8 does NOT Like.

Note: This does not hppen on ESXi 5.

Solution

I knew this was going to happen, so I took a snapshot before I installed VMware tools, Then I had the luxury of reverting back. If you are reading this you probably didn’t! If that IS the case, then press F8 as the Virtual Machine starts to boot to launch Automatic Repair (be quick on the keys).

Installing VMware Tools in Windows 8

1. To stop this happening, when you install VMware tools select > Custom > Remove the SVGA Driver > Next > Finish > Yes (to reboot).

2. You will notice that the display driver that is uses, is the “Microsoft Basic Display Adaptor”.

Related Articles, References, Credits, or External Links

Windows 8 -“Windows cannot read the <ProductKey> setting from the unattend answer file.”

Windows 8 Wont Run in VMware Workstation

Running Windows Server 8 in VMware ESXi