none
Black screen with only mouse cursor appears for long time after login in windows 7 as domain user.

    Question

  • 4 domain users in my office are facing an issue recently that users are getting black screen with only mouse cursor after loggin in win7 PC (after entering user name and password). ctrl+alt+del does not work at this time. and automatically after 5 to 10 minutes desktop icon appears without domain wall paper.

    There is no such problems when login locally to the system.

    Kindly advice


    Shanmugan KR
    Thursday, July 21, 2011 5:03 AM

Answers

  • Hi,

     

    Before moving on the troubleshooting, I want to confirm the following with you.

     

    1.       Does these users in the same OU?

    2.       Does these account works fine in another machine?

    3.       Did you install any third-party software recently?

     

    First, I suggest that you may try to rename their profile and try to repro the problem again. Then we can narrow down whether this problem is caused by the user profiles. Also you may logon another machine with these account to ensure whether this problem is server related issue or client related problem.

     

    As a test, you may create a new OU with an empty group policy options. Move these account to the new OU and try it again.

     

    If the issue persists, you may perform a Clean Boot to check whether this problem is caused by third party software:

     

    http://support.microsoft.com/kb/929135

     

    Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG.

     

    Actually, many issue may cause this kind of problem, I wondering whether you may find an Event log in “Computer management ->Event Viewer ->Windows log -> system” which Event ID is 100,such as:

     

    Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational

    Source:        Microsoft-Windows-Diagnostics-Performance

    Date:          7/12/2010 7:30:48 PM

    Event ID:      100

     

    You may post this log here, then we could check the detail boot time list.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Monday, July 25, 2011 9:46 AM

All replies

  • I restarted the server but issue is not resolved yet. Kindly help
    Shanmugan KR
    Monday, July 25, 2011 4:45 AM
  • Hi,

     

    Before moving on the troubleshooting, I want to confirm the following with you.

     

    1.       Does these users in the same OU?

    2.       Does these account works fine in another machine?

    3.       Did you install any third-party software recently?

     

    First, I suggest that you may try to rename their profile and try to repro the problem again. Then we can narrow down whether this problem is caused by the user profiles. Also you may logon another machine with these account to ensure whether this problem is server related issue or client related problem.

     

    As a test, you may create a new OU with an empty group policy options. Move these account to the new OU and try it again.

     

    If the issue persists, you may perform a Clean Boot to check whether this problem is caused by third party software:

     

    http://support.microsoft.com/kb/929135

     

    Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG.

     

    Actually, many issue may cause this kind of problem, I wondering whether you may find an Event log in “Computer management ->Event Viewer ->Windows log -> system” which Event ID is 100,such as:

     

    Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational

    Source:        Microsoft-Windows-Diagnostics-Performance

    Date:          7/12/2010 7:30:48 PM

    Event ID:      100

     

    You may post this log here, then we could check the detail boot time list.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Monday, July 25, 2011 9:46 AM
  • I had the same issue.  After troubleshooting for a while I figured it out.
    Windows 7 will not install printer drivers via group policy scripts.

    If on a domain then, on the same domain controller(s) that run active directory, there is group policy and probably group policy scripts.

    If scripts were written for new printers that add them and set them to default etc. and the drivers for those printers were never installed on that workstation then the gpscript.exe process on the workstation will get hung on start up of the domain user's profile with the offending group policy leaving you with a black screen and a mouse cursor.

    ctrl-alt-del does nothing. although if you have remote desktop software with command execute ability, such as "netsupport" you can issue the computer commands.

    notice just starting "explorer.exe" will load a dummy "systemprofile" desktop, although as if you are the user logging on, but with a default desktop. so just starting explorer is not the fix.

    you can start task manager "taskmgr.exe" if you have such remote software already installed and stop the "gpscript.exe" process. then watch your desktop load like magic.

    Then what you need to do is install the proper printer drivers for whatever printer the group policy script is attempting to install.

    In my case the user having the issue was physically in one department yet was contained in a department group for another different department in active directory. so when the other tech went around installing drivers for the new printers, he installed the drivers for the department he was physically in. So I added the other drivers; although I also moved his account (and others on that workstation) to the department in active directory that they were physically in. and whala all fixed and no future issues.

    If you have no remote software installed with command execute ability then restart and log in as some other user, or a local account, then install the drivers and then restart and try logging in as the domain user account that had the black screen.

    Tuesday, October 09, 2012 6:47 PM