I checked the Event Viewer and it did not accurately record the true boot
time (i.e. it assumed the "boot" was finished before the 45 second pause
even though things continued to load after this delay). Therefore, no
suspect process was identified.
I started services.msc during this pause and determined that WORKSTATION
SERVICE was stuck on "Starting" this whole time (45s) before it finally
"Started".
Why does Workstation Service take so long to start? The only network
service on my computer is Intel certified 802.11b/g/n network card. It is
connecting fine to a D-link router (802.11g) using WPA/PSK.
If I disable Workstation Service during startup, the startup "pause"
disappears. However, I understand this service is important for Vista.
Any idea what is going on with Workstation service? Next step?
"Kerry Brown" <*a*m> wrote in message
news:B5536453-57E6-4088-AAE2-...
> "Sabian Smith" <> wrote in message
> news:...
>>I have a new Vaio SZ650 laptop running Vista Business edition 32bit. I
>>removed alot of bloatware that came with the system and put on some core
>>apps (Bluetooth, Fingerprint reader, Office 2007, PowerDVD, utorrent,
>>ashampoo burning, infranview, acronis trueimage, EndNote).
>>
>> Problem: Vista boots and desktop/sidebar come up... then.. PAUSE x 45
>> seconds (minimal CPU and HD activity).. then the rest of the startup
>> software loads (Kaspersky antivirus is the only thing that visibly loads
>> up after the pause).
>>
>> I tried uninstalling Kaspersky - no difference. Using MSCONFIG, I
>> disabled all non-microsoft processes from starting, as well as all
>> startup applications . I still noticed a similar pause followed by 5-10
>> seconds of disk activity / busy pointer.
>>
>> System scanned for spyware and viruses - nothing. Vista performance
>> event log does not list a suspect process holding things up.
>>
>> Here is my HijackThis startup log. Any ideas?? I notice a lot of
>> "undefined registry keys". Could this be the problem?
>>
>
>
> HijackThis log interpretation is a specialized field. You should only post
> the logs and take advice on what to do with the results in one of the many
> forums dedicated to it's use. Following the wrong advice could cause more
> problems. The dedicated forums are moderated with only known experts
> allowed to give advice.
>
> Vista monitors the boot process and writes in the event logs when
> something takes an unusual amount of time to load.
>
> http://blogs.zdnet.com/Bott/?p=246
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
>