Software Explorer Error

[Guest]

I just downloaded the beta2 and test drove it. I had an error in the
Software Explorer as follows:
Software Explorers error 0x8007065d. Data supplied is of worng type.

I was unable to find any posts regarding this error. Any help will be
appreciated

 

[Bill Sanderson]

--

 

[Bill Sanderson]

Can you say anything about what you were doing when the error arose? Was
this just opening the software explorers page?

 

[Guest]

Yes, I was just opening the software explorers page. After I click OK, I
get to the correct screen with a red X and error loading view.

 

[Bill Sanderson]

Thanks--this is a unique report as far as I've been able to spot. Any
unusual features of your system?
--

 

[Guest]

I have the same problem.
It is a Dutch Windows XP Home system with
Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6
I do not know of any unusual features, only that I also have the "Banker.TX
found"
problem:
http://www.microsoft.com/athome/sec...&p=1&tid=c6bd175e-f590-496e-a882-7231c20c025e

It only shows up at the Category "Startup Programs". The other Categories
are shown correctly.

 

[Bill Sanderson]

On the Banker.TX issue--I should probably be posting this to the other
thread, but Mike Treit will probably make a parallel suggestion:

Some trojans can conceal their presence by tricking the registry editor.

It would be useful for you to export that registry key--just save it as a
..reg file to the desktop.

Now rename it to a .txt for safety. Do some sanity checks on it--how many
bytes long is it--what does it look like in notepad?

You may find that it is not as simple as it appears in the registry editor.

--

 

[Guest]

Thank you Bill,
I did what you suggested, however I do not see anything wrong in the
applicable
registry part. See my remark in the "Banker.TX" issue in the General part.

 

[Bill Sanderson]

Saw it, and I agree--it looks innocent. I've seen such keys which look
normal in the XP registry editor, but, in fact, when dumped are quite long
and contain a long string of characters which succeed in fooling that
application.

--

 

[Guest]

In the meantime Microsoft has identified the problem. It is a false positve
and it will be solved
after the next engine update later this month. The "Software Explorer Error"
should be solved
by the same update.

 

[Bill Sanderson]

Terrific--glad to hear it!
--

In the meantime Microsoft has identified the problem. It is a false
positve
and it will be solved
after the next engine update later this month. The "Software Explorer
Error"
should be solved
by the same update.

 

[Guest]

Bill,
The errors occur if the Registry "Shell" value in
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
is of type REG_EXPAND_SZ instead of REG_SZ.
So for you it should be easy to recreate the errors on your machine.

 

[Bill Sanderson]

Ah--thanks. I wonder what would have created that change?

--

 

[Guest]

Engine version 1.1.1303.0 does solve the Banker.TX problem, however the
Software Explorer error is still there!

 

[Bill Sanderson]

Sorry to hear that. Hmm--there were some XML-related errors in the beta1
product that arose on machines with non-English languages--I wonder if this
is some similar issue?

 

[Guest]

Solved by Windows Defender Version: 1.1.1347.0

Engine version 1.1.1303.0 does solve the Banker.TX problem, however the
Software Explorer error is still there!

 

[Bill Sanderson MVP]

Terrific--glad to hear it.
--

Solved by Windows Defender Version: 1.1.1347.0