I had a problem in windows 2003 server .I logged in the server successfully but nothing comes on the display.I tried booting in last good known ,but same .But I am able to use the server in safe mode .I had uninstalled several programs ,but of no use .Still the problem persist.
I think some program is creating problem ,but I am not able to find it.could u please hel me.

Dani AI

Generated

Given that can log on but never gets the normal shell, and that already ruled out the display/driver angle after ’s suggestion, the fault is most likely in components that Safe Mode suppresses: the shell/Winlogon hooks, startup programs, or a corrupt profile. The checklist below is focused on those areas and is written for Windows Server 2003.

  1. Confirm whether the shell is starting. Press Ctrl+Alt+Del → Task Manager → File → New Task (Run...) and start explorer.exe. If the desktop appears, inspect the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell (should be explorer.exe) and Userinit (should be C:\Windows\system32\userinit.exe, — note the trailing comma). Export the keys before changing them.

  2. Check for a custom GINA/Winlogon hook. Look at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDll. If a third‑party value is present and not required, back up the registry and remove it to test whether normal logon returns. Exercise caution on domain controllers and production servers.

  3. Isolate startup items and services. From Safe Mode run msconfig: on the Services tab check “Hide Microsoft services” and disable the rest; on Startup disable nonessential entries. Reboot normally. If the shell appears, re-enable items in halves to find the culprit.

  4. Test for profile corruption. Create a new local administrator account (Computer Management → Local Users and Groups) and log on normally. If the new profile shows the desktop, migrate user data and recreate the profile.

  5. Inspect logs and run repairs. Check Event Viewer (System/Application) for Winlogon/explorer errors at logon. From Safe Mode command prompt run chkdsk /f and sfc /scannow (SFC may require install media). Back up data before any repair or registry edits.

Make a full registry/system backup before edits. On domain controllers or production servers, schedule a maintenance window or restore from a known good image if uncertainty remains.

Recommended Answers

All 2 Replies

Could your screen resolution be set higher than that of your monitor can handle.

Either boot in VGA mode and correct the display settings, or uninstall the graphics driver in safe mode, and reinstall once in full mode.

Just a thought.

Could your screen resolution be set higher than that of your monitor can handle.

Either boot in VGA mode and correct the display settings, or uninstall the graphics driver in safe mode, and reinstall once in full mode.

Just a thought.

the screen supports 1280x1024. at no point will windows 2000 set a screen res higher than that unless I tell it, which I have not. I have not changed the res, AND I have tried to change it whilst in both safe mode and vga mode.

I am curious if maybe not having the kvm swicth's focus on the computer while in setup has anything to do with it. That is another commonality that I had not immediately thought of.

Thanks for the reply though.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.