When ever Windows XP shuts down, the following message is displayed ...
(Title)Inetprotectorservice.exe Application Error
(Message) Exception unknown software application (0x0eedfade) occured at the application at location 0x7c812afb
The system is using iNet protector 3.5 on XP Pro Tablet edition
Any suggestions would be greatly appreciated.
Inetprotectorservice application error on shutdown
- Karlis
- Site Admin
- Posts: 3605
- Joined: Mon Jul 15, 2002 5:24 pm
- Location: Riga, Latvia, Europe
- Contact:
Re: Inetprotectorservice application error on shutdown
Does this alter the wey iNet Protector works on your computer? As you seem to be the first and so far only one user to have this problem, I suspect this is something related to your particular system (e.g. a conflict with some other non-standard or specific software you have installed). How long ago did this start to happen?
Re: Inetprotectorservice application error on shutdown
While the machine is running, iNet protector seems to work perfectly ... the error is only during system shutdown. My suspicion, at this point, is that the conflict is with webroot parental controls, but there is no easy way for me prove that.
Re: Inetprotectorservice application error on shutdown
I have always had the same problem with an error about inetprotector at shutdown of Windows XP, both on my old computer and my new computer. I don'thave webroot parentals controls installed.
I have a non-English version of XP.
kollo
I have a non-English version of XP.
kollo
- Karlis
- Site Admin
- Posts: 3605
- Joined: Mon Jul 15, 2002 5:24 pm
- Location: Riga, Latvia, Europe
- Contact:
Re: Inetprotectorservice application error on shutdown
I would hate to burdain you, but, if you happen to have an opprtunity, you could uninstall webroot temporarily to see if the problem persists ater a couple of shutdowns. There is no other way I believe. I did not manage to produce this problem.While the machine is running, iNet protector seems to work perfectly ... the error is only during system shutdown. My suspicion, at this point, is that the conflict is with webroot parental controls, but there is no easy way for me prove that.