Long Boot Time after shutdown

gregrocker said:

System Recovery Options

I'd use the Repair CD if you have it because F8 Advanced Boot Tools run from the same disk as problem install, hence CD/DVD is a more stable platform for repair or reimaging.

Well, once again, I shutdown and restarted several times last night, no problems.

This morning, it took long to boot again, and Avast was turned off when windows came up, I had to turn it on manually.

I have a Repair Disk, that I manually created a few weeks ago; I suppose my next step is to try it, and if I experience the same problem tomorrow morning, I will do a full image restore with the 6 DVD's I created.

Even Event Viewer is taking a long time, and is there anywhere specific that will tell me what was taking so long this morning?

Check the Administrative View and Performance logs: Computer lags every couple seconds

There is a new startup manager http://soluto.com/ in beta that is coming along quite nicely and can map your entire startup with tips and buttons for what can be Delayed or Paused (turned off at startup until you open the program). I recommend trying it, then advancing if necessary to the tool the pro's use which I posted above.

gregrocker said:

Check the Administrative View and Performance logs: Computer lags every couple seconds

There is a new startup manager Soluto in beta that is coming along quite nicely and can map your entire startup with tips and buttons for what can be Delayed or Paused (turned off at startup until you open the program). I recommend trying it, then advancing if necessary to the tool the pro's use which I posted above.

7009: A timeout was reached (30000 milliseconds) while waiting for the avast! Antivirus service to connect.

7000,7009,7022,7009,7009,7009,7000,7001 follow, all related to the Service Control Manager

Solutions I have read is to increase the timeout period in registry, but that doesn't make senses to me?

how do i export to file as an attachment?

airahcaz said:

gregrocker said:

Check the Administrative View and Performance logs: Computer lags every couple seconds

There is a new startup manager Soluto in beta that is coming along quite nicely and can map your entire startup with tips and buttons for what can be Delayed or Paused (turned off at startup until you open the program). I recommend trying it, then advancing if necessary to the tool the pro's use which I posted above.

7009: A timeout was reached (30000 milliseconds) while waiting for the avast! Antivirus service to connect.

7000,7009,7022,7009,7009,7009,7000,7001 follow, all related to the Service Control Manager

Solutions I have read is to increase the timeout period in registry, but that doesn't make senses to me?

how do i export to file as an attachment?

could it also be my DHCP attempting to get a new internet connection in the morning? (ethernet connected)

DustSailor said:

Could your bios settings have been changed at all?

I wouldn't have changed the bios myself, should I look to reest or for an upgrade?

airahcaz said:

airahcaz said:

gregrocker said:

Check the Administrative View and Performance logs: Computer lags every couple seconds

There is a new startup manager Soluto in beta that is coming along quite nicely and can map your entire startup with tips and buttons for what can be Delayed or Paused (turned off at startup until you open the program). I recommend trying it, then advancing if necessary to the tool the pro's use which I posted above.

7009: A timeout was reached (30000 milliseconds) while waiting for the avast! Antivirus service to connect.

7000,7009,7022,7009,7009,7009,7000,7001 follow, all related to the Service Control Manager

Solutions I have read is to increase the timeout period in registry, but that doesn't make senses to me?

how do i export to file as an attachment?

could it also be my DHCP attempting to get a new internet connection in the morning? (ethernet connected)

HP support thinks it might be related to my wireless Canon MP495 printer and print spooler, so I deleted the printer altogether and will assess tomorrow morning.

They also suggested resetting the bios, which I will do, but I didn't touch the bios, so not sure what a reset will do (there is no current newer bios as well).

Uninstall Avast and try MS Security Essentials. They are pretty much interchangeable in terms of lightweight and effective. I often swap them if one is causing a snag.

gregrocker said:

Uninstall Avast and try MS Security Essentials. They are pretty much interchangeable in terms of lightweight and effective. I often swap them if one is causing a snag.

That's where I started! Deleted Norton Trial, installed MSE, deleted MSE, replaced with Avast per your earlier post :)

Now I'm told to run the HP Smart Drive Test from BIOS options which will run for 81 minutes...

I'd go along with HP as they decide whether to RMA parts or the whole machine. You will learn a lot about troubleshooting your computer and how these OEM's work.

Running a drive test means they are focusing on HD as a possible candidate for RMA. If this doesn't work to your liking, you can press them to RMA the entire machine at any point along the way.

A reasonable goal with this is to get the RMA returned and shaken out to know that you've got a keeper well before your one-year warranty runs out.

gregrocker said:

I'd go along with HP as they decide whether to RMA parts or the whole machine. You will learn a lot about troubleshooting your computer and how these OEM's work.

Running a drive test means they are focusing on HD as a possible candidate for RMA. If this doesn't work to your liking, you can press them to RMA the entire machine at any point along the way.

A reasonable goal with this is to get the RMA returned and shaken out to know that you've got a keeper well before your one-year warranty runs out.

I actually doubt it is a hardware issue. Memory tests passed. Hard Drive test passed, no issues. Avast full Boot Scan also passed, no issues.
Reset BIOS to default (even though I didn't change anything there before anyway)
Deleted Canon MP495 Wireless Printer.
Ran CCCleaner, and installed Soluto.

Not sure it makes sense to go back to MSE, but I can boot tomorrow morning, and if I experience the same problem, can try that, but would have to suspect it would be something else.