Legit Reviews

So I noticed that I'm getting a System Event log that says "The Intel(R) Quick Resume technology service hung on starting." each time I start my PC.

After poking around a bit, when I boot up the computer I can go immediatly to the Services screen and see that the Intel Quick Resume service is stuck on "Starting". About 2 minutes later, it suddenly switches to "Started" and that error line is added to the log. It would seem that it's hanging on the first startup attempt, and when the system tries again it works. And yes, it does appear to be working properly after that 2 minute delay.

Now the real problem is that my computer is not fully usable for those 2 minutes, since this appears to delay the starting of a wide number of other required services until that 2 minute period is up (their startup entries all appear in the log after the notice about the hung service).

For now I have uninstalled the Quick Resume drivers and disabled it in the BIOS - no more delay, everything is nice and snappy - but has anyone else come across this or know how to fix it?

imo this is only supported in the media center edition. so leave it disabled when using xp!

I also have mine disabled as this is more for Viiv Systems...

From Intel's Site:

Intel® Quick Resume Technology Driver (QRTD) allows the Intel® Viiv™ technology-based∇ PC to behave like a consumer electronic device with instant on/off (after initial boot, when activated) capability.

After looking around on the Intel site they only show setting it up on Windows XP Media Center Edition operating systems: example.

I suppose I should point out that I'm running XP Media Center Edition 2005.

is is set up like that link i posted to Intel?

Yeah, it was setup correctly... and *did* work, save for that annoying startup problem that automatically corrected itself after two minutes.

I configured Quick Resume a few months ago on an AOpen Mini PC that I'm using as a HTPC without issue, so having trouble on an Intel original board seems odd. I don't know if it's a driver issue, an XP issue, or a conflict with something else that's starting up at the same time (this PC is significantly more "loaded" than the Mini PC).