Re: Problem with Windows Explorer on XP-Pro/SP2
From: Don Taylor (dont_at_agora.rdrop.com)
Date: 01/02/05
- Next message: Billjones85: "Can I change COA number on XP after installation?"
- Previous message: ~ FreeSpirit ~: "Re: Cannot Drag-n-Drop files... (!) The PATH"
- In reply to: Don Varnau: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Next in thread: Uncle John: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Reply: Uncle John: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 02 Jan 2005 03:00:10 -0600
"Don Varnau" <don_04[at]varnau[dot]org> writes:
>Hi Don,
>I've seen your posts. I agree that you've been thorough. I believe that
>malware is only one of many possible causes of the Windows Explorer problem.
I created that to list off every known thing to try for the hundreds of
people who found this problem minutes after they installed SP2. And it
doesn't really look like it did any good for anyone, with the exception
of three or four people out of the hundreds who did find that one of
the chanted platitudes actually did turn out to apply to their case.
>In Karl's case, if he has *only* used Ad-aware, NIS and an AV program, he
>hasn't done a complete and thorough check for malware. I helped someone with
>this recently and removing some adware/spyware files fixed Explorer.
So let's actually track down and really diagnose the causes. By
my count about 95% of the people reporting the Windows Explorer
problem never reported finding a solution. And from what I can
tell there has been ZERO progress on this after the first week or
so of people reporting the problem, not a single new method of
tracking this down, not a single discovery, nothing.
There is lots of finger pointing and chanting that it is spyware.
And absolutely zero diagnostic information has been presented.
There isn't even a list of file name/path/size/date that are known
to be problems. Nobody has a script that scans a system and points
out a list of files that are known to have caused SP2 problems.
Corrupted user profiles are blamed. There is no cute script for
XP that can catch errors generated by a corrupted profile, even
though there is apparently something like this for NT mentioned in
one of the Microsoft web pages.
Something that astonishes me, Microsoft likely spent billions
creating SP2 and from the tens of thousands of messages I've read
it doesn't contain a single line of code to prepare itself for being
installed on compromised machines WHEN THE REASON THEY SPENT THE
BILLIONS WAS BECAUSE THERE WERE MILLIONS OF COMPROMISED MACHINES
OUT THERE.
There is apparently not a single line of code to recognize a
machine compromise and put it into the log so that it can be
recognized and sterilized. Shortly after SP2 was released there
was a stream of messages posted by people about an error with
not being able to run a DOS program. Autoexec had been clobbered
and nothing in SP2 considered corrupting a system file as anything
that needed to be noted in the logs.
So as I said, let's settle it, let's diagnose a cause, or a few
dozen causes if you believe there are multiple causes.
>Don
>[MS MVP- IE/OE]
> "Don Taylor" <dont[at]agora.rdrop.com> wrote in message
>news:MtednYYPM5QOpErcRVn-2A@scnresearch.com...
>> "Don Varnau" <don_04[at]varnau[dot]org> writes:
>> >Karl,
>> >There is a lot of malware out there. Ad-aware is good but won't catch
>> >everything- neither will any anti-virus program.
>>
>> I've been dealing with "The Windows Explorer" problem that several
>> hundred people have reported showing up immediately after installing
>> SP. Of all those reports a single person did find a virus and that
>> removing it did appear to fix his problem.
>>
>> Now I realize that someone could report that flames were shooting
>> out of their computer and a dozen people would begin chanting that
>> it is obviously a malware problem.
>>
>> But lets you and I settle what this problem is in just my case.
>> I've been obediently followwing all the instructions for three
>> months with Microsoft support. Nothing they have asked me to do
>> has found any evidence of malware. Nothing they have done has
>> given any hint what the problem was. But let's settle it.
>> >This problem is probably being caused by another program- something
>> >interacting with Internet Explorer or Windows Explorer- possibly even a
>> >legitimate program.
>>
>> >I'd suggest that you work through the pre-cleaning steps at
>> >http://www.aumha.org/a/quickfix.htm then post a HijackThis log to the
>forum
>> >at http://forum.aumha.org/viewforum.php?f=30
>>
>> >Or, a legitimate program may be causing the problem. Disable any programs
>> >which might be interacting with IE. Look at privacy/security programs,
>> >ad-blockers, AV, etc. One of them may need to be reinstalled or may need
>an
>> >update to work with SP2.
>>
>> I've mailed them hijack logs, I've mailed them ntuser.dat, I've done
>> virus scans, I've done malware scans, I've disabled every shellextension
>> in the entire system, I've disabled EVERYTHING in msconfig before boot.
>>
>> And I and hundreds of others still find that everything which uses
>> Windows Explorer still just keeps demonstrating the exact same problem.
>>
>> Let's settle this.
>>
>> >This article may help:
>> >276393 - Understanding and Troubleshooting Unrecoverable Errors in
>Internet
>> >Explorer: http://support.microsoft.com/?kbid=276393
>>
>> >Don
>> >"Karl Jahr" <karl[at]jahr.us> wrote in message
>> >news:eAhyRQD8EHA.3616@TK2MSFTNGP11.phx.gbl...
>> >> Thanks. But I am sure, I never had a virus. Others had the same
>problem,
>> >and it wasn't virus related either.
- Next message: Billjones85: "Can I change COA number on XP after installation?"
- Previous message: ~ FreeSpirit ~: "Re: Cannot Drag-n-Drop files... (!) The PATH"
- In reply to: Don Varnau: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Next in thread: Uncle John: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Reply: Uncle John: "Re: Problem with Windows Explorer on XP-Pro/SP2"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
