Prev: Windows Update Error Code 646...
Next: ERROR 0X8DDD0004
From: Harry Johnston [MVP] on 9 Jun 2010 16:32
Hi,

Just a heads-up: it looks as if vSphere 4.0 (the VMWare client application used
to administer VMWare servers/clusters) stops working on Windows XP (and perhaps
other OSes) when this month's updates are installed. I haven't confirmed this
as the definite cause of the issue I'm having, but it's the most likely suspect.

Based on a KB article about a similar issue relating to Windows 7, I suspect
that vSphere 4.0 update 1 won't be affected. But if you use vSphere, and don't
have update 1 yet, you may want to hold off on this month's updates until you
can check whether this will affect you.

Harry.

--
Harry Johnston
http://harryjohnston.wordpress.com
From: Harry Johnston [MVP] on 23 Jun 2010 18:19
To follow up on this, we've just installed VMWare 4.0 update 1 at my site, and I
can confirm that the updated version of vSphere has resolved the problem I was
having. (I never did get a chance to run experiments to confirm that this
month's .NET updates triggered the issue, but it seems likely.)

Harry.

On 2010-06-10 8:32 a.m., Harry Johnston [MVP] wrote:

> Hi,
>
> Just a heads-up: it looks as if vSphere 4.0 (the VMWare client
> application used to administer VMWare servers/clusters) stops working on
> Windows XP (and perhaps other OSes) when this month's updates are
> installed. I haven't confirmed this as the definite cause of the issue
> I'm having, but it's the most likely suspect.
>
> Based on a KB article about a similar issue relating to Windows 7, I
> suspect that vSphere 4.0 update 1 won't be affected. But if you use
> vSphere, and don't have update 1 yet, you may want to hold off on this
> month's updates until you can check whether this will affect you.
>
> Harry.
>


--
Harry Johnston
http://harryjohnston.wordpress.com
 | 
Pages: 1
Prev: Windows Update Error Code 646...
Next: ERROR 0X8DDD0004