blue desktop after login

[Guest xcoach]

I have approximately 1600 users running XP SP2 and approximately 3 months

ago, a user called up saying that after he logs in, he gets a blue screen

with no task bar or icons. I had him hit Ctrl-Alt-Del and logout then log

back in. Once he did that, everything came up fine, but sporadically he

still gets the same problem. Lately, this same issue has been cropping up on

other PC's as well. Having the user logout then back in resolves the issue

at the time, but unfortunately, a couple of the users have this issue every

time they login from a cold boot. After doing a lot of reading on the web, I

ran across an item that said the shdocvw.dll file is the culprit; renaming or

deleting it resolves the problem. I tried that and it appeared to work, but

now the same problems are back again.

 

There seems to be a lot of chatter in forums about this issue but no one

seems to have a solid answer. Has anyone come up with a solution for this

problem?

[Guest Holz]

Re: blue desktop after login

 

 

 

On Mon, 17 Mar 2008 10:31:04 -0700

xcoach <xcoach@discussions.microsoft.com> wrote:

>I have approximately 1600 users running XP SP2 and approximately 3

>months ago, a user called up saying that after he logs in, he gets a

>blue screen with no task bar or icons. I had him hit Ctrl-Alt-Del and

>logout then log back in. Once he did that, everything came up fine,

>but sporadically he still gets the same problem. Lately, this same

>issue has been cropping up on other PC's as well. Having the user

>logout then back in resolves the issue at the time, but unfortunately,

>a couple of the users have this issue every time they login from a

>cold boot. After doing a lot of reading on the web, I ran across an

>item that said the shdocvw.dll file is the culprit; renaming or

>deleting it resolves the problem. I tried that and it appeared to

>work, but now the same problems are back again.

>

>There seems to be a lot of chatter in forums about this issue but no

>one seems to have a solid answer. Has anyone come up with a solution

>for this problem?

>

>

 

Wrong group. Try the Windows server group.

 

--

Holz

:-)