m2wshlex.dll causes Explorer "Edit" function to cr
Posted: Mon Sep 28, 2009 4:34 pm
IN Win XP (SP3) on TWO machines (a Dell XPS desktop and Dell 820 laptop) IÔÇÖve been having issues with the Windows Explorer window crashing if I am on any folder that CONTAINS folders and try to use the menu item ÔÇ£EditÔÇØ so that I could do things like ÔÇ£Copy, or Paste, or Select all, etc.
It was a MINOR annoyance but lately it was really interfering with work flow and was a real issues SO I decided to run it to ground.
It seems I wasnÔÇÖt paying attention the pop up debug window when Exploder crashed it actually TOLD me exactly what was crashing. It turns out it is ÔÇ£m2wshlex.dllÔÇØ which is an Acoustic a installed DLL (MP3 to Wav Convertor plus) in any case when I disable it in the context menus (via EITHER regedit and or using NirSoftÔÇÖs ShellExView) I no longer have windows Explorer crashes when using the menu item ÔÇ£EditÔÇØ in the Explorer Window.
IÔÇÖve been able to consistently make Explorer crash, or not, as a function of having the that DLL active in the context shells or not.
ItÔÇÖs a completely repeatable and verifiable issue ÔÇô at least on these two machines in Win XP SP3. Any other reports? Any planned updates for this bug?
Thanks
Larry
It was a MINOR annoyance but lately it was really interfering with work flow and was a real issues SO I decided to run it to ground.
It seems I wasnÔÇÖt paying attention the pop up debug window when Exploder crashed it actually TOLD me exactly what was crashing. It turns out it is ÔÇ£m2wshlex.dllÔÇØ which is an Acoustic a installed DLL (MP3 to Wav Convertor plus) in any case when I disable it in the context menus (via EITHER regedit and or using NirSoftÔÇÖs ShellExView) I no longer have windows Explorer crashes when using the menu item ÔÇ£EditÔÇØ in the Explorer Window.
IÔÇÖve been able to consistently make Explorer crash, or not, as a function of having the that DLL active in the context shells or not.
ItÔÇÖs a completely repeatable and verifiable issue ÔÇô at least on these two machines in Win XP SP3. Any other reports? Any planned updates for this bug?
Thanks
Larry