2

Running a Win 7 x64 machine. About a week and a half ago it started stalling on the 'Please wait...' before login. I tried the hotfix https://support.microsoft.com/en-us/kb/2617858 to no avail. I am able to get past it once the screensaver kicks on and I wake it. Thoughts anyone?

Improve this question
9
  • 2
    capture a boot trace of the issue: pastebin.com/CYGqRZXE (the Win8.1 WPT also works fro WIn7) and share it
    – magicandre1981
    Sep 11, 2015 at 4:15
  • 2
    have you captured the boot trace?
    – magicandre1981
    Sep 16, 2015 at 19:04
  • 1
    I downloaded and installed the WPT. Executed the script. The trace appears to be running indefinitely and does so on each startup. Is this normal behavior?
    – Steve Salowitz
    Sep 29, 2015 at 12:34
  • 2
    after a boot you should see a timer which tick down from 120 seconds to 1.
    – magicandre1981
    Sep 29, 2015 at 16:07
  • 1
    That happened on the first run but I dont see that anymore but it appears to be running the trace on each startup. How can I unschedule or disable the trace?
    – Steve Salowitz
    Sep 30, 2015 at 12:48

5 Answers 5

Reset to default
1

before the screensaver (c:\windows\system32\morley.scr) kicks up, Windows Installers installs some software which is triggered by Kaspersky NetworkAgent (klnagent.exe). Look in Kaspersky logs to see what it does during boot.

This causes a lot of disk IO during boot and slows down boot a lot.

enter image description here

I checked the callstack of some disk activity and see that a Lenovo driver called DzHDD64.sys is involved. Look if this driver is really required and if not, remove it.

Improve this answer
2

Tested and verified in a domain environment. "Please wait" is not necessarily a computer problem especially in a enterprise environment. Rebooting DC helped resolve the problem which was likely caused by DNS caching. Hopefully will save someone time versus troubleshooting the computer in vain.

Improve this answer
2
  • 1
    I can't see any mention of a domain environment in the question ...
    – DavidPostill ♦
    Jan 16, 2016 at 22:08
  • 1
    @DavidPostill I can't see any mention that it is not in a domain environment either. Ryan B's post helped me.
    – localhost
    Mar 21, 2017 at 4:43
2

The "please wait" slows down once I add the computer to an OU with scripts. Long story short I went ahead and ran the https://support.microsoft.com/en-us/kb/3172605 and only had 2 spins of please wait. Special thanks to Andre to lead me towards the right direction. I've been researching this issue for 6 months.

Improve this answer
1

For testing purpose please try to disable the following services: Windows Error Reporting, Network Location Service, Network List service

  1. Power off the PC
  2. Power on and press repeadiatly F8 you see the Safe Mode screen
  3. Select Safe Mode with Networking
  4. Login to your PC
  5. Press Win+R and enter services.msc into the window followed by pressing return
  6. Locate above services (Windows Error Reporting, Network Location Service, Network List service)
  7. Double-click them (one by one) and change the startup type to Disabled
  8. Restart your computer gracefully! (Start -> Shutdown)

Those services aren't really necessary but might block your PC from booting.

If this doesn't help, please provide more info, like is your PC part of a domain?

Improve this answer
7
  • 1
    Will do @Andre stay tuned
    – Steve Salowitz
    Sep 10, 2015 at 20:49
  • 1
    I tried these and it didn't work. I didn't go into Safe Mode though, does that matter? Yes I am part of a domain. Its my work laptop. I suppose I could go through our tech support guys but I am a systems/programming guy and like fixing it myself
    – Steve Salowitz
    Sep 11, 2015 at 16:52
  • 1
    I guess your boot time is normal, when you are connected with a cable at work within your domain? An delayed boot time is normal outside of your domain. To confirm that theory I would suggest you to leave the domain for testing purpose and join a workgroup. If your boot time is normal we can think of a solution.
    – A1985
    Sep 11, 2015 at 17:07
  • 1
    What you could also check is, if the group policy for waiting until your mapped network drives are connected is set. This would delay your boot extremely. I have to check where the policy is located when I'm at home
    – A1985
    Sep 11, 2015 at 17:11
  • 1
    To check my last point: Win+R -> gpedit.msc -> Computer Config\Administrative Templates\System\Logon -> Always wait for the network at computer startup and logon set this to disbled
    – A1985
    Sep 11, 2015 at 20:45
1

Run Disk Cleanup and make sure Windows Updates Temporary files are checked, and restart.

There may be a broken Update somewhere.

Improve this answer
1
  • Tried this already to no avail
    – Steve Salowitz
    Sep 11, 2015 at 15:19

You must log in to answer this question.

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