Is there something in the system startup that's loading it? And is it in fact loaded as an actual service? Sounds more like it's an autostart program.
No - absolutely nothing in Startup folder or registry Run, RunOnce etc. keys related to this item.
Can you give us a hint on what the service or driver was? Or what hardware? One person's "ancient Dell" might be another's "newest stuff we got"...
One of our clients still has a stash of Gx1s, although I think they finally got rid of their 6300s. In fact we just junked a 2400, most of their plants are running with 2500s now (with a smattering of newer boxes). Cost avoidance is really big with some sectors of US manufacturing...
It is a Dell 1525 Inspiron latop running Vista SP2 Basic, 32-bit.
The service concerned is BCM42RLY - which is apparently related to an old Broadcom wifi driver which is no longer needed or relevant since Vista SP1. A new Broadcom driver has been installed and doesn't actually contain and BCM42xxx files.
I have found lots of references to the problem through Google - and a lot of frustrated users! I have not found a solution other than to change the registry Start key from 3 to 4 to prevent windows trying to load the service.
Sounds like a job for Process Explorer followed by Autoruns.
Process Monitor might help, too, especially with finding out what exactly keeps adding it back into the Registry. Might be able to watch it in real-time.
There doesn't seem to be any processes that I can see that are related.
SC DELETE BCM42RLY
confirms deletion, and looking in the registray a Delete Pending key is generate - but after restart the only thing removed is the delete pending flag!!
The service is not protected by odd permissions - I can backup and delete the Service entries in the registry and they are gone - and don't return after reboot.
Nevertheless - even though BCM42RLY is no long present any where in the registry as a string it still automatically attempts to start during start up.
Something distinctly odd is going on.
Having restored the registry entries and set Start to 4 the issue no longer appears (the setting is retained) but this is just a workaround which helps to stop pauses at boot time. I am intrigued as to what could be doing this?