Security Settings Will Not Save

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello--

I have a new user that is using IE version 6.029 on Windows XP Pro with SP2.
He is set as the administrator both locally, and on our LAN.

When he tries to change the security settings on IE, they will not save. He
tries to lower them and then he hits OK, and when he opens it again, it is
back to where it was before. This happens in all groups--local intranet,
Internet, etc.

He tries hitting reset after OK, and not hitting reset after OK. No change.

Please help!

Thanks,
 
Yes, as a matter of fact it is. But since we have it installed on other
machines that do not have this issue, it didn't cross our minds that that
might be the issue.
 
What other anti-malware applications might be installed (e.g., WinPatrol,
Pest Patrol, MS Windows AntiSpyware)?

Does 'IE Tools > Reset web settings' make any difference?

Have you run a thorough check for hijackware?

Check for Hijackware
http://aumha.org/a/parasite.htm
http://aumha.org/a/quickfix.htm
http://mvps.org/winhelp2002/unwanted.htm
http://inetexplorer.mvps.org/Darnit.htm
http://www.mvps.org/sramesh2k/Malware_Defence.htm
http://defendingyourmachine.blogspot.com/

When all else fails, HijackThis
(http://aumha.net/downloads/hijackthis.zip) is the preferred tool to
use. It will help you to both identify and remove any hijackware/spyware.
**Post your files to http://forums.spywareinfo.com/,
http://castlecops.com/forum67.html or
http://aumha.net/viewforum.php?f=30 for expert analysis, not here.**
 
Thank you. This Windows OS was just installed on a newly reformatted hard
drive, and is all of 2-3 days old. We have gatekeeper software on our
Exchange server, so I don't think he had time to get anything malicious.
 
A newly installed yet not fully patched version of Windows can get infected
in less then 5 seconds if it's connected to the 'net. Best to rule
hijackware (including a Rootkit infection) /out/, razor, than assume it's
not the problem.

Repeat:

The above notwithstanding and as you've further detailed this machine's
environment, might a Group Policy be causing the problem?
 
Back
Top