Boot issue

G

Guest

Hello All,

I recently noticed, that while my computer is booting, "after" the Windows
splash screen, yet "before" the user login screen, I now get this MS XP blue
screen message that says the following:

(ssiefr.e program not found - skipping Auto Check)

After this message displays for several seconds, the message disappears, and
the typical login screen appears, I can login okay, and all systems and
software seem to work perfectly fine, no problems at all.

I did a search on my computer, and I did find a very similar file named:
ssiefr.exe it is located at the location of C:\Windows\System32

So, my question is , what the heck is going on, and how do I eliminate this
blue screen message at boot time?

All help, empahty, and support is deeply appreciated,

Robert S.
03/05/07 at 11:26am PST
 
D

db

not sure what that particular file
is for, but i would look it up
at microsoft.com and see if it
is a valid system file.

however, whether it is or not you
can use a freeware at microsoft.com
called autoruns.

one of the tabs will notate what
is launching during boot. It
is likely you will find a line item for
that file and you can then check it
and double click its filename to disable
the registry key for it.....

- db
Hello All,

I recently noticed, that while my computer is booting, "after" the Windows
splash screen, yet "before" the user login screen, I now get this MS XP blue
screen message that says the following:

(ssiefr.e program not found - skipping Auto Check)

After this message displays for several seconds, the message disappears, and
the typical login screen appears, I can login okay, and all systems and
software seem to work perfectly fine, no problems at all.

I did a search on my computer, and I did find a very similar file named:
ssiefr.exe it is located at the location of C:\Windows\System32

So, my question is , what the heck is going on, and how do I eliminate this
blue screen message at boot time?

All help, empahty, and support is deeply appreciated,

Robert S.
03/05/07 at 11:26am PST
 
G

Guest

Hello db,

Thanks so much for taking the time for support,

I'll try your advice, and report back.

I'm not much a pro on messing with the registry, however I'll run the
freeware you mention and see what I can find out.

Much appreciated.

Robert S.
03/05/07 at 12:41pm PST
 
D

db

ok, let us know what
you find out....

- db
Hello db,

Thanks so much for taking the time for support,

I'll try your advice, and report back.

I'm not much a pro on messing with the registry, however I'll run the
freeware you mention and see what I can find out.

Much appreciated.

Robert S.
03/05/07 at 12:41pm PST
 
G

Guest

Hello again db,

Well, the file named ssiefr.e that was showing up at my system boot, was in
fact from Webroot's SpySweeper program that I have installed on my machine.

I called Webroot, they provided a system uninstaller, I ran it, and "still"
the problem exists.

So, i re-contacted Webroot, and while I was waiting Webroot's response, I
took your advice and downloaded the "Autoruns for XP". I found it by typing
"autoruns" at google.

I downloaded it, ran it, and sure enough as you suggested, I found the
registry sting that was a problem.....I edited the string (actually deleted
this problem file ref), and voila, no more problems.

You saved the day db, when Webroot was still trying to figure out what to do.

Much appeciated,

Robert S.
03/05/07 at 3:05pm PST
 
G

Gerry Cornell

Robert

Have you been trying out Spysweeper?


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
D

db

you're welcome.
Hello again db,

Well, the file named ssiefr.e that was showing up at my system boot, was in
fact from Webroot's SpySweeper program that I have installed on my machine.

I called Webroot, they provided a system uninstaller, I ran it, and "still"
the problem exists.

So, i re-contacted Webroot, and while I was waiting Webroot's response, I
took your advice and downloaded the "Autoruns for XP". I found it by typing
"autoruns" at google.

I downloaded it, ran it, and sure enough as you suggested, I found the
registry sting that was a problem.....I edited the string (actually deleted
this problem file ref), and voila, no more problems.

You saved the day db, when Webroot was still trying to figure out what to do.

Much appeciated,

Robert S.
03/05/07 at 3:05pm PST
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top