rundll wjview winstart errors

Howard,

Run a scan using Ad-Aware [www.lavasoftusa.com].

For the WJView error:
http://www.mvps.org/sramesh2k/WJViewError.htm

--
Ramesh - Microsoft MVP
http://www.mvps.org/sramesh2k
-------------------------------------------
Virus attachment claims to contain software updates from Microsoft
http://www.mvps.org/sramesh2k/VirusAlert.htm

How to guard against CoolWebSearch spyware:
http://www.mvps.org/sramesh2k/Defend_CWS.htm

How to prevent Blaster Worm attack:
http://www.mvps.org/sramesh2k/Blaster_Defence.htm
-------------------------------------------


"Howard J" <bikepathlesstaken@yahoo.com> wrote in message news:x7DNb.75806$xy6.133827@attbi_s02...
We're getting the following set of errors in at least a 'regular' permission
profile in WinXP Home edition. We might be getting them in one or more
profiles with Administrator permission level.

For example, here's what just happened:

1) Logged into the regular-permission profile.
2) First error dialog box
Title: RUNDLL
icon: white x on a red circle
button: "OK"
message:
Error loading C:\windows\System32\msiefr40.dll
Access is denied.

3) Second error message. (In this instance, the message arrived without my
having dismissed the first error.)
Titlebar's text: WinStart
WinStart has encountered a problem and needs to close. We are sorry for the
inconvenience.
If you were in the middle of something (well, the rest of the message is
Microsoft's standard offering to send an error report.)
Clicking on the message's link to see what data this error report contains
gets to this:

WinStart
Error signature
AppName winsta~1.exe
AppVer: 5.0.1.0
ModName: ntdll.dll
ModVer 5.1.2600.1217
Offset: 0000b2ab


Technical info--well, if you need me to post that, please let me know.


4) WJVIEW Error
titlebar text: WJView Error
text: ERROR: Could not execute Main: The system cannot find the file
specified.



Note: this PC has some adware that's not yet been deleted. (There are
about 15 files reported by Norton Systemworks 2004. The files are the ones
that, of about 29 files, couldn't be deleted by Systemsworks. Systemworks
provided links to documentation on how to remove the items manually, but
we've not gone at it yet, as the the instructions are lengthy and something
about the situation seems like if we don't do things in the right order--and
there might not be a right order--then one or more of the not-yet-deleted
bad files will recreate the others.

Thanks in advance for any sense you can make of this!