VMware Cloud Community
oldmetalguy
Contributor
Contributor
Jump to solution

vsphere client 4.1 white console screen

I support ESX 3.5, 4.0 and now 4.1 hosts. When I installed the viclient 4.1 on my windows 7, (giving me all 3 versions of the client), now any host I connect to and try to open a console of a running vm gives just a white screen.

I really really really don't want to whack my machine and re-install it, so is there a magic fix out there?

0 Kudos
25 Replies
StoneFin
Contributor
Contributor
Jump to solution

Thank you Andreas - this worked prefectly for me:

I am running Windows 7 Ult. x64

After installing the 4.1 client, I was getting the white screen when trying to get to the consoles of the esx3i boxes.

I simply ran the command as you suggested from the command line to disable DEP for the client app

bcdedit.exe /set nx AlwaysOff

it gave me a success message.  It did not tell me to, but I had to REBOOT prior to it taking effect.

Thanks so much.

Carl

0 Kudos
lpc
Contributor
Contributor
Jump to solution

Installing client 2.5 U6 + 4.0U2 all OK

4.1 (259021) OK

4.1 U1 (345042) white console in vc2.5-U6 , other errors.

0 Kudos
CHDave
Contributor
Contributor
Jump to solution

Hi Andreas

I Recently switched to Win7 x64, and got the "white screen bug"

Disabling DEP did the trick!

Thank you

Dave

0 Kudos
lpc
Contributor
Contributor
Jump to solution

5.0 client solved all problems.

0 Kudos
jaymz87
Contributor
Contributor
Jump to solution

I know this thread is a bit old, but completely disabling DEP sounds like a really bad idea on machines connecting to management servers. I've found a solution which allows you to only exclude the vSphere client from DEP. It's a bit hacky, but much safer than the DEP solution, and a lot simpler than reinstalling everything.

Blog post with script and info.

0 Kudos
msgvb
Contributor
Contributor
Jump to solution

Neil, I know this is old, but I'm just getting around to playing with vSphere 5.0, and found myself with the white screen.

Found the KB article, but it was nice reading up on this in the Community for some feedback.

Uninstalled all versions of the client on my Win7x64 machine using Revo Uninstaller, advanced mode, Installed the 2.5 Client, did the old Launcher folder rename trick, then installed the vSphere 5.0 client.  Pulled a shortcut to VpxClient.exe from the Launcher.old folder - both clients work like a charm now.

Good info, thanks for posting.

Scott

-msg
0 Kudos