15 minute boot time...

Downloading.

Well, I will not have a chance to look deeply at this, but something is triggering an entire disk/filesystem check on boot, and it's taking almost 10 minutes to complete. Have you run a chkdsk /r lately? I'll look later tonight or tomorrow when I get finished with work and life, but this almost appears to be a driver issue (antivirus, antimalware, etc) or it could really be a filesystem or hard disk issue.

The first suggestions would be to update any chipset or RAID software (if any is installed) to the very latest supported versions. Second, remove all antivirus, antimalware, antispyware, firewall, disk defragmentation, and any other 3rd party software which would have a disk filter driver installed. Third, run a chkdsk /r on /C: (will require a reboot), and let the checkdisk finish and fix any issues found. Fourth, use defrag.exe /u /v against C:, and then reboot.

At that point, take another quick measurement of how long it takes to reboot - assuming my initial assumptions are at least headed in the right direction, your system should be MUCH faster.

Drips,

I'm similar to GregRocker in my approach to these problems.

Let's get a clean startup.

did you try running without any services except for the MS services?

Download, install, run CCleaner which is free (link in my sig)

AFter that please carry out following:
LIST OF STARTUP PROGRAMS USING CCLEANER


CCleaner | Tools icon | Startup tab | click on Save to text file button (bottom right side)

Using the PAPER CLIP icon in the top panel of a Message Reply window, attach the .txt file generated by CCleaner.
======================================

After that,
Control Panel | Programs and Features | uninstall any programs that you are no longer using. Uninstall any Nero programs. Uninstall any MagicIso or CloneDVD programs.

all of those programs can be good. They also can interfere and cause some wierd problems.

I'm not just firing the shotgun hoping that I hit the bird. All of these things I have encountered.

Of the two still checked, neither will cause the problem you are seeing.

Is this computer connected to a home network and/or to a router?

Pity that you don't have a restore point or a system image from immediately after the fresh install.

Some piece of hardware or some piece of software is really causing problems.

Have you checked for a bios update for your computer?

We can go at this backwards. Any extra exteranl hardware could be removed. Programs that have been installed that are not from Micorsoft could be slowly removed until the quilty party is located.

A badly fragmented disk can also cause delays. It won't hurt to run Micorosft's Disk Defragmenter.

Another experiment would be to complete disable Eset and see what happens. Eset likes to send/receive an unusual amount of info back and forth.

I forget, did you run MalwareBytes (link in my sig).

This program has helped others locate the source of their slow bootup. I make no promises. If you use it, then afterwards uninstall as it leaves itself via services still running.

Soluto

So there are three devices causing delays, according to the trace:
"USB\VID_064E&PID_A127\CN0316-S30C-OV10-VH-R02.01.00" - USB composite device
"USB\VID_064E&PID_A127&MI_00\7&1a444de9&0&0000" - HP WebCam
"Root\volmgr\0000" - Volume Manager mount point on Hard disk 0

I decided to break it down into 3 sections - you have about 33 seconds wasted even before the kernel finishes loading and passes off to smss.exe to begin the rest of the boot process, so that's the first phase. Your machine actually takes a LONG time loading the volsnap (VSS) driver as well, and enumerating volume snapshot mount points takes almost 50% of that time, so that would potentially point to disk or filesystem issues.

Second, it takes smss.exe 308 seconds (this is the splash screen delay you see) to finish getting everything up and running, and 148 seconds of that delay is actually caused by accesses (mostly reads) to the hard disk. From what I see here, it would appear that either the disk is failing, or the NTFS filesystem on it has become in some way screwed up.

The third section is actually the winlogon+explorer+postboot section, which takes 127 seconds. That delay is mostly down to your antivirus hammering the disk (scanning during boot) and the fact that the disk itself is actually quite fragmented and slow. That could also be due to the fact that your disk is a (very) large portion of cause in your boot delay, and given the other sections also show an inordinate time spent on disk, this seems just more evidence of a disk or filesystem issue.

At this point, I would strongly suggest you follow my previous advice (chkdsk c: /r, reboot, uninstall software, defragment, and reboot again), and unless you are able to do so you probably aren't going to make much headway. Also, it seems that your webcam driver has something to do with this, and note that this is NOT the first time I've seen HP's webcam driver cause boot delays! The last piece is it does seem something attached to the USB bus is also at fault, but I don't know for sure if the HP Webcam hangs off of the USB bus internally, but I'd bet it does (the driver is snp2uvc.sys, which is a USB webcam video driver - which is also responsible for the lion's share of disk I/O not related to metadata during boot). So, after careful review, my initial observations on this appear to be confirmed - you have a disk problem, and also a problem with the HP webcam driver.



As to your question about what to remove, I'd recommend the following:

• Speccy
• Soluto
• MalwareBytes
• ESet
• Conduit
• JMicron driver
• ENE driver
• LightScribe
• HP DriveGuard
• ValiditySensors
• HP WebCam
• Cyberlink software (all 4 items)

Those would all be initial culprits in the delays, although Speccy and Soluto are more "just in case" options rather than real problem areas.

Speccy will not influence his startup times. Malwarebytes only if he has it to set at startup time.

The Soluto program will help him find the guilty parties. AFter gleaning info from soluto, then the program should be deleted.

The WebCam software is a likely suspect.