Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Every time I start up my computer, Windows XP Pro will hang at the welcome screen (I don't have any user accounts) for about 1 minute before showing the desktop.

Anyone encountered this issue before and know what's causing this problem?

share|improve this question

Odd as this might sound, try putting a disc in your DVD drive. Without one in my Windows XP system's drive during startup, there is a long pause that sounds similar to yours. Is it a long shot? Yes. Is it easy to try? Also yes.

share|improve this answer
Very interesting, but even if it solves the problem, it would be nice to know why. – soandos Aug 7 '11 at 3:50
I couldn't agree more. On the other hand, trying to understand why everything works the way it does in Windows seems like a ticket to crazyville. – boot13 Aug 7 '11 at 13:32

Most likely, you have either a disconnected printer or mapped network drive. Your computer is trying to locate one of these devices/machines and will get past the welcome screen once it times out.

Either that or you have way too many things loading at boot. Click on Start > Run and type MSCONFIG. You can disable a lot of items from starting up.

enter image description here

Under the Services Tab be sure to uncheck Show Microsoft Processes and you will see from your list of installed applications which ones have services starting at boot. Also under the Startup tab you can disable applications from booting.

share|improve this answer

It's a rather well-known DHCP issue/bug -- it happens to me all the time.

Unfortunately, there's no 100% foolproof fix.

You can avoid it if you can assign a permanent IP address to your adapter, so that your computer doesn't have to wait for the router to give it an IP address dynamically. Alternatively, turn off your network cards and reboot: you should see that it doesn't happen again.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .