Windows 7 displays black screen upon reboot

[bshubinsky]

I seem to be having a bit of an issue with VMware View, ESX and Windows 7. I am currently testing the feasibility of running Windows 7 through View in our environment. I'm running an ESXi 4.1 server with the newest version of VMware View. Windows 7 installs fine, I can do everything I need to do. The moment I reboot, Windows 7 boots up and lets me log in.

As soon as I log in, I get a black screen. It doesn't crash, it doesn't do anything, just a black screen. I can still normally reboot the machine without a problem. I have the 3D driver installed and even made sure that I had the latest version of the driver but it doesn't seem to make a difference. I set the VM to automatically select the amount of video RAM to give it as well.

Has anyone run into this issue before?

[mittim12]

You can try some of the KB articls listed below.    Are you using PCOIP or RDP to connect up? 

http://kb.vmware.com/kb/1011709

http://kb.vmware.com/kb/1028332

[bshubinsky]

Neither I'm trying to use the VMware console. It appears that the screen does eventually show up, but I have to wait about 5-10 minutes before it displays. It shows the same symptoms via RDP.

[mittim12]

I would try the first KB article then and see if that helps.

[bshubinsky]

Nope, same thing.

[gunnarb]

I've seen the black screen issue numerous times but never from the console.  If its happening on the console level then it can't be related to VMWare View.  Something is wrong with the VM itself, most likely whatever graphic driver you are using doesn't work.  I suggest opening a case with VMWare tech support.  I wouldn't even bother telling them this is for View, you just have a basic VM issue.

-Gunnar

[mittim12]

Are you able to duplicate it accross multiple VM's or just a single Windows 7 desktop?

[bshubinsky]

It ended up being an issue with the batch scripts that was run on first boot - it required administrator priviledge and just hung there until someone clicked it, which was impossible. Once I converted the batch scripts to vbs the problem went away.