We are having issue with the View Client 3.2 (also 3.4).
To reduce the fat-client computer complexity, we launch vmware-view.exe with a vbs and there's no explorer.exe on the local user profile.
When launching the view client with a parameter(-serverurl and -desktopname), the process might remains in the task manager if the user disconnects or cancel before logging in.
The issue doesn't occur if the client is launched without any parameter.
The problem, the vbs script runs the vmware-view.exe and waits it up before launching it again if it's closed. With the issue, since there's no explorer.exe, the user might have a black screen. The user shutdowns the computer or can do a CTRL+AL+DELETE to log off the local profile.
I can patch it up to check the applications task with a powershell script at 10 seconds interval, but that's not the long-term fix.
Do you have the same issue when you launch the view client with -serverurl and -desktopname ? Try several times, and you might have bunch of vmware-view.exe processes even if there are no windows in the task bar...