Windows Explorer "Error Loading Resource..."

  • Thread starter Thread starter Hoib
  • Start date Start date
H

Hoib

Hello. On WinXP Pro. Been working super but this prob
just showed up 2 days ago and I've been trying to fix
it. In Windows Explorer, I want to check the Properties
of the hard disks (checking on free space). Right click
and I get this pop-up: Error Loading Resources - (in the
box) The specified module could not be found (new line)
C:\Program
Files\IOMEGA\COMMON\IOMCOPYDISKSHELLEXT.enu.ilsr
(button) OK.
Pressing OK gets me 2 more similar (but slightly
different) popups. Pressing OK gets me to where I want
to be - the Properties sheet.

Under Win98SE, last year, I had this system loaded with
an IOMEGA tape backup. Way before upgrading to XP Pro, I
got rid of it AND uninstalled the software/drivers/etc.
Also use Norton WinDoctor regularly. Haven't heard hide
nor hair from that software until - two days ago when
this started magically appearing. None of the IOMEGA
software shows up under Control Panel/Add-Remove Progs.
Device mgr shows no ref to it either. I've searched the
entire disk to discover no reference to "IOMEGA"
anywhere. I've searched through AUTOEXEC, CONFIG.SYS,
WIN.INI and SYSTEM.INI for a stray ref - no luck. Is it
in the registry? I'm really leery of messing with the
reg.

Where else could this rogue entry, pointing to
an "IOMEGA" program, be hiding?

Now, at the same time this is going on, again about two
days ago, I started erratically getting (even when it's
just "idling"): Windows Explorer has encountered a
problem and needs to shut down. If you were working on
something, some data could be lost" (or words to that
effect). I think I need to solve the first problem first
before trying for the Win Explorer error. I think the
one may be causing the second.

Does anyone see a problem with my approach? Anyone ever
encountered something like this before that I can take
experience from?
 
Click Start, Run and enter REGEDIT Highlight the HKEY_CLASSES_ROOT branch,
click Edit, Find and search for

IOMCOPYDISKSHELLEXT

Where you find this value, right click the subkey that its found in and
select Export. This creates a backup of the subkey in question. Then right
click the value, or subkey if appropriate and select Delete. Repeat until
you've removed all occurrences. If you're unsure of what to remove, leave
it alone, and post back.
 
Hey! That wasn't so bad! I found a single instance of:
IOMCOPYDISKSHELLEXT (all caps) in a subkey consisting of
a lengthy hex string. I also searched two more times to
be sure I had all occurances. The reg is a HUGE place!
I did find IomCopyDiskShellExt in a few other spots but
decided to leave those be - they're NOT all caps so I
thought they were probably related but not to be messed
with. Found a couple more instances of
IomCopyDiskShellExt.IomCopyDiskShellExt.1 Left those
alone too.

Exported the subkey first, did the delete (turns out the
subkey stayed but "value not set" was substituted and
exited. (Hope I'm using the right terminology here...)

Opened up WE, right clicked on the drive and presto, no
error! So I won't call it complete victory yet - let's
wait a day or so and see if error no 2 shows up (Win Expl
has encountered an error and needs to shut down).

Thanks Doug and everyone here. Such a nice orderly place
to get things accomplished. I appreciate it.
 
You're welcome, Hoib. Just one note, rarely are Registry entries case
sensitive, so the lower case occurrences could be part of the problem, but
if its gone, then I'd say you solved it.
 
Excellent advice of course - If it ain't broke...
Have been running this as is for over a day. Right click
still works perfectly and Explorer hasn't announced and
unannounced closing either. I've kept a copy running
down on the task bar which I don't normally do just to
exercise it. Great fix and I learned something about the
reg too. Where would you send me to learn a bit more in
your experience?

Hoib
 
A lot of it is by trial and error. A good place to start for basic to
Advanced stuff is www.winguides.com Then check out some of the VB Scripts
on my site (below) and the tweaks and fixes on
www.kellys-korner-xp.com/xp_tweaks.htm to see some that you may not find on
winguides.

In your particular case, it had to be something that was hooked into the
Properties page, and that has to be done in the Registry. Sometimes its
fairly easy to find the culprit, others it isn't :)
 
Back
Top