At the same time, how
come there are many who experience this same problem?? From what you say,
suggest, there may be a number of reasons why this error msg appears. Thus
maybe not so easy to get rid of short of installing all from scratch.
The message, as you know, is just that, an annoyance and does not seem to
inhibit proper operation. Therefore, there is not just one solution to
wipe out the annoyance?
In the threads that I found, the message was not coming directly from
Windows.
In one instance, it was coming from programs installed into Windows (Office
programs) that needed attention. Probably a portion of an Office program
that was configured to load at startup but could not due to missing files
or incomplete settings.
Since the message occurs at every startup, this would be a logical area to
look at a little closer. Try using Start> Run> MSCONFIG and disable all
startup programs. Then restart. If the message is gone, re-enable one
startup item. Restart. Repeat until you get the message again. The last
item added before the error message appears, is the one that needs
repairing/reinstalling.
I see from your other post that you have checked for an autorun.inf.
Autorun are typically used on CDs and contain an execute command that
initiates a setup program. On occasion, an *.inf file is copied to the root
of C: and cannot autorun. This is not as common now as it once was but it
still happens now and then. No need to rename the one that you found for
Roxio. You only need to concern yourself with any that are in the root
folder of the boot drive.
For example, if your system boots from C: (most common), that is where you
need to look. Not in the subfolders - just in the loose files that show up
when C: is highlighted in Windows Explorer. You may want to set Folder
Options to show hidden files just in case there is a hidden autorun.inf
file in this location. If found, delete.
Another thing to check would be Event Viewer. Start> Run> eventvwr.msc will
bring up this tool. Check the Application and the System branches for a
more detailed message about the startup problem. Double click any item to
bring up a window with more details about each event. Perhaps a file name
will be mentioned in one of these descriptions that will help you to narrow
your search for the cause.