Link to home
Start Free TrialLog in
Avatar of benhogg01
benhogg01

asked on

Windows 7 Welcome Screen Freeze

Hi,

I'm getting this strange problem which I can't seem to find a solution for.

Randomly our users computers freeze up on the Welcome Screen when trying to login and the only way to fix it, is to reboot the machine unplug it from the network and then log in and reconnect to the network.

The Event log has so far been no help, it only happens when connected to network at work ,ie the domain, when connected to other networks no problems.

All machines are running Windows 7 Professional x64; DC’s are 2008 R2 Enterprise.

Thanks for your help.
ASKER CERTIFIED SOLUTION
Avatar of rockiroads
rockiroads
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of benhogg01
benhogg01

ASKER

Hi,

We don't have any login scripts, although we do have a few group policies and we do have mapped drives.

By welcome screen I mean, once a user has entered their username and password it says Welcome, it will sit there saying Welcome for hours, unless I reboot it.
have u checked the startup programs? registry/startup folder etc. easy way is to use a tool like CCleaner (or a tool I just heard of but not tried called Autoruns).

In ccleaner, you can see what programs start when logging in.

Have u tried disabling mapped drives?

Is it trying to update some s/w or windows updates and its eating up cpu ?

Might also be worth checking for virus and malware whilst your at it (perhaps run hijack this initially) just in case like.
try disabling the group policies on one computer and see if that fixes the issue..  we had an issue once where I added in a script to add a group of people to the local adminstrators group...well, for some reason one of our other techs modified that script and renamed it...well the computers just sit at welcome and dont do anyhting because they cant find that original file that the GPO references to.
They use local or roaming profile?
Hi, Thanks for help turns out it was a mapped drive via group policy preferences causing the problem I have now mapped the drive via a script and all is working well.

Thanks

Ben