The event viewer shows the apparent problem - error message on bootup is "The DCOM Server Process Launcher service hung on starting", and after bootup, services.msc shows the process as "starting" not "started". However this is in fact incorrect - based on 2 facts: Process Explorer shows the service as running, with a few dependent .exe's running underneath it; and certain functions that will not work when I boot with DCOM server process launcher disabled (which by the way solves the speed-of-boot issue) such as my Creative sound card tools are working fine when this service shows as "starting" - as does Autoupdate, which needs this service as well. So the problem is not with the process but the way it is being incorrectly monitored. A search on this forum and via Google found nobody with the same identified problem.
I think this issue arises as an aftereffect of a rootkit virus infection which Gringo of the malware response team on this forum helped me to remove - my system now scans clean with several trojans etc removed and my log thread with him is finished, but he was stuck on this issue.
1. reinstall of SP3 (Gringo's suggestion)
2. ran SFC /SCANNOW - no problems reported.
Any other suggestions would be greatly appreciated.
Edited by DevonK, 08 October 2011 - 10:58 AM.