Hello all,
recently I have been having a problem after logging in, Windows 7 shows the welcome screen for over a MINUTE. Initially, it would load instantly and the welcome screen would only flash for about half a second. I don't know what could have changed this. Any input is appreciated.
Message edited by regimentaL on 09-19-2009 at 11:29:49 PM
If you don't know what changed it, chances are we don't. Any new program installations? Did it happen after a certain OS update? Is this the RC or the RTM we're talking about? Did you add any more users? Change hardware? Just try to think of anything to do with the PC that would have been different between the last time it worked fine and the first time you noticed the 1 minute login times.
I'm pretty sure it's not a virus, i have AVG actively protecting my computer and run Malwarebytes' scans regularly. It wouldn't be a rootkit would it? Does Malwarebytes' detect rootkits? EDIT: Actually there is one recent piece of software I haven't removed and that is Microsoft Office 2007, I wouldn't think that that is the reason for the slow login times though. Unless it is running some sort of startup service in the background but I have looked through the services and seen no such thing.
Message edited by regimentaL on 09-20-2009 at 12:09:30 AM
Actually, it does install one small startup service, but it doesn't do anything from what I've found out.
How old is this installation? After a while, Windows will just start to feel bloated, after software installs/removals and such, and may be fixed by running programs like CCleaner, although they don't always do the job, and a reinstallation will have to do.
Before the OS presents the desktop, it loads any start-up scripts, security configurations, additional drivers and services that you may require or have installed. My suggestion is add another user, log out and log in as the new user. If the problem goes away, then its something that your normal user account is loading, probably a start-up program or a massively big file in the Documents library.
If the problem persists with the new user, then its a computer or OS-related problem, most likely caused by a bug, glitch, or an update that switched on something that's not necessary and very memory-intensive (possibly a memory leak).
Thanks Snow_Patrol I'll give that a try. Right now I'm defragging with fingers crossed that that may be the problem, but I doubt it is since my computer schedules a defrag every week.
Thanks Snow_Patrol I'll give that a try. Right now I'm defragging with fingers crossed that that may be the problem, but I doubt it is since my computer schedules a defrag every week.
Defragging wont do anything for you, might as well cancel it. Since Vista, Windows has been defragging your hard drive in the background while your processor is idle, one of the many reasons why people complained about so-called disk thrashing, or unusual activity. Rather perform a disk cleanup, and go check msconfig to see what programs are starting up. If you find anything with the box ticked that doesn't have a name next to it, disable it from start-up immediately, because that's usually malware or an orphaned file.
I've already tried running msconfig, there was only a couple things there, maybe 4 or 5 and I recognized all of them. =/
I'll try your initial suggestion now i guess.
Okay, so I tried enabling the guest account and restarting my computer and logging into that first. It still takes just as long to log in. However, once logged into the guest account i could log off and log into my administrator account within a couple of seconds. So, do you have any suggestions of where I should go from here?
Message edited by regimentaL on 09-20-2009 at 01:49:17 AM
Just for a hoot, try unplugging your network cable and booting. I'm thinking that the OS may be trying to access a remote resource and waiting for a response that's not coming - unplugging the cable should short-circuit that if it's indeed the cause.
Well I tried disabling my wireless card and then rebooting - same problem.
Oh well. I have this nagging little thought floating in my head that I've read about something similar and it turned out to be Windows attempting to do something and having to wait until the operation timed out.
Have you checked your event log to see if there's anything noted there?
I did indeed check the event log and found something that was adding about 45 seconds to the boot time. I disabled the service that was doing that (it was HpCueDiscovery or something along those lines) but it still takes a good 30 seconds for windows to login due to this event:
Driver Management has concluded the process to add Service tunnel for Device Instance ID ROOT\*ISATAP\0000 with the following status: 0.
ISATAP is part of the IPv6 network stack. You might try turning off IPv6 support to see if that's really what's involved. You can do this as follows:
Start -> Control Panel -> Network and Sharing Center
Click the "Change Adapter Settings" in the left pane
Right-click on the network adapter and select "Properties"
Uncheck the "Internet Protocol Version 6" checkbox and click "OK"
If that speeds things up, then you might want to try re-enabling IPv6 and then resetting the protocol stack by typing the following into a Command Prompt window (will require a reboot):
I unbound the IPv6 protocol and didn't notice any difference in boot time. >_< I tried resetting the protocol as well and it says that there's no user specified settings to reset, I guess that's because I never setup a static-ip on this computer? Also where it says "Driver Management has concluded the process to add Service tunnel for Device Instance ID ROOT\*ISATAP\0000 with the following status: 0" i'm almost positive that the 0 means installation successful, so does that mean it's installing a driver every time i boot up my pc?
Message edited by regimentaL on 09-20-2009 at 06:34:53 PM
ISATAP is a tunneling protocol to allow IPv6 networking through an IPv4 network. So that message probably has nothing to do with drivers and is just indicating that the tunneling protocol has been successfully initialized.
If that's not what's causing your delays then I'm afraid I'm out of suggestions...