Getting An "Framedyn.dll" Error. What Is This?

[HarleyRider]

Hello;

Every time I start Spybot 1.4 a window pops up that says:

"This application has failed to start because Framedyn.dll was not found. Re-installing the application may fix this problem".

(See Attachment)

I click OK then Spybot 1.4 starts up and seems to run normal. I have re-installed it but I still get the same pop-up at start-up. Does anyone know what's going on here and how to fix this? I'm lost. Any help would be greatly appreciated.

Cheers!!! :beerbeerb

Scott

[md usa spybot fan]

The problem is usually caused by a bad path. Please read the following Microsoft Knowledge base article:
"Application Has Failed to Start Because Framedyn.dll Was Not Found" Error Message When You Open the System Properties Dialog Box
http://support.microsoft.com/default...b;en-us;319114

There is also a lengthy discussion about the problem here:
Framedyn.dll Can't Be Found, Error when starting SB
http://net-integration.us/forums/ind...howtopic=20893

[JerseyD]

I just had the same problem on my PC and after reading the microsoft article I noticed one slight difference in my Path Variable. The W in wbem was a Capital W instead of lower case w. Simply changing the W to a w fixed the problem.


%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem = Problem
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\wbem = Problem Solved

[bitman]

Though you did 'fix' the problem, it wasn't the case, since system variables aren't case sensitive. You did, however, find a simpler way to fix the problem than we've used in the past.

The actual problem is that the 'Type' of registry value is incorrect, which leads to the failure of the Path variable even though it appears to be valid. Since the Type information is only visible in a registry editor, you can't see it in the Environment Variables view you were using. However, doing anything to change the Path variable will fix this, since the Type will be corrected when it is saved.

In the past we've recommended changing or removing one character and then changing it back, a two step process, but your idea of changing one character's case does it in one. In the future, I will suggest this method instead.

Thanks for the idea.
Bitman

[Lumaan]

Had the same problem :( but did some google and came by a website where some sayed "And I think you'll just put it into "%SystemRoot%\system32""

I did but it in to "%SystemRoot%\system32" and *Drums plz* and nomore "This application has failed to start because Framedyn.dll was not found. Re-installing the application may fix this problem"

[bitman]

The framedyn.dll file doesn't belong in the System32 folder, so this could create problems down the road. The reason this worked was that the System32 folder is in the path, so the file was found during initialization, avoiding the error message but not fixing the real problem.

If you want to truly fix the problem, delete the copy you placed in the System32 folder and follow the correct instructions above. Otherwise, if this file is ever updated you will have an outdated invalid version in the path and could have problems with System Restore, which framedyn.dll supports.

[stormybob]

I discovered this while tinkering one night. THIS IS FOR THE SPYBOT MISSING FRAMEDYN.DLL ONLY! THIS WILL NOT FIX UR SYSTEM PROPERTIES ISSUE! Anyway the fix is make sure its in ur wbem folder. Doesnt have to be in ur dllcache folder. Anyway copy and paste the framedyn.dll file into ur spybot folder. That should do it! CASE CLOSED!

[bitman]

No stormybob, that's incorrect. If you do that you will stop the message but still not fix the core issue, which is that your search Path is not operating correctly.

This is quite simple to fix as the earlier posts have discussed and will also fix other issues that exist on the PC that you are not aware of that are also related to the Path.

Bitman

[F-AVRO75]

Hi, I read all the "solutions" and tips, even from MS; the only solution to avoid this error message and it worked in my case is to add Framedyn.dll in the Spybot Programm !
That's the easiest way...
Kind regards and thanks to "Spybot" for this fantastic programm !

[bitman]

F-AVRO75,

That is not the correct way to fix the issue, though it does work.

The correct way is mentioned multiple times in this thread and requires that you fix the 'broken' entry in your Path variable. Though it may appear to be correct in some cases, it isn't and can be fixed by the method given in one of my earlier posts. The other possibility is that your WMI installation is damaged, which is even worse since it is then likely that Windows System Restore is non-functional.

The issue is that if the file is ever updated by Microsoft in the future, your older copy in the Spybot S&D folder will not be which might cause issues with the operation of your PC.

What you have done is a 'hack' that stops the message from displaying, but doesn't really fix anything.

Bitman