by Onansboy » Fri May 24, 2019 1:33 am
Hello. In case others are having this problem I thought it best to post my solution. As I thought, Avast somehow caused the "script execution" error by taking ownership of (in my case) C:\Windows\SysWOW64\vbscript.dll and rewriting it to something akin to C:\\Program Files\Avast\vbscript.dll, thus stopping Mediamonkey from running addon scripts. I understand Avast's actions can also affect C:\Windows\system32\vbscript.dll, but this didn't happen in my case. So the solution for me was to reverse Avast's action. In other words to change C:\\Program Files\Avast\vbscript.dll back to C:\Windows\SysWOW64\vbscript.dll
The following link
http://www.mediamonkey.com/support/inde ... ipt-engine showed me how to use Regedit to find and alter the relevant entries. Using the search facility within Regedit for "InprocServer32" I found the three main registry keys I needed to fin in order to see if Avast had altered any of them: CLSID\{B54F3741, B54F3742, and CLSID\{B54F3743. Fortunately for me, only one of the keys had been altered.
I got stuck, however, when the system denied me permission to affect the necessary reversal. That's where the following link was helpful
https://www.maketecheasier.com/full-own ... stry-keys/. Then, having ticked the relevant boxes that gave me permission to take ownership of the relevant key, I rewrote it and closed Regedit. When I opened Mediamonkey the error was gone and my addons are now working like before.
A word of warning: making changes to the registry is done at your own risk. At the very least back it up before changing anything. And while this solution worked for me, I can't guarantee the same results for other users.
Anyway I hope this helps any others who just might have the same error...
Hello. In case others are having this problem I thought it best to post my solution. As I thought, Avast somehow caused the "script execution" error by taking ownership of (in my case) C:\Windows\SysWOW64\vbscript.dll and rewriting it to something akin to C:\\Program Files\Avast\vbscript.dll, thus stopping Mediamonkey from running addon scripts. I understand Avast's actions can also affect C:\Windows\system32\vbscript.dll, but this didn't happen in my case. So the solution for me was to reverse Avast's action. In other words to change C:\\Program Files\Avast\vbscript.dll back to C:\Windows\SysWOW64\vbscript.dll
The following link [url]http://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/143/0/error-message-cant-find-script-engine[/url] showed me how to use Regedit to find and alter the relevant entries. Using the search facility within Regedit for "InprocServer32" I found the three main registry keys I needed to fin in order to see if Avast had altered any of them: CLSID\{B54F3741, B54F3742, and CLSID\{B54F3743. Fortunately for me, only one of the keys had been altered.
I got stuck, however, when the system denied me permission to affect the necessary reversal. That's where the following link was helpful [url]https://www.maketecheasier.com/full-ownership-windows-registry-keys/[/url]. Then, having ticked the relevant boxes that gave me permission to take ownership of the relevant key, I rewrote it and closed Regedit. When I opened Mediamonkey the error was gone and my addons are now working like before.
A word of warning: making changes to the registry is done at your own risk. At the very least back it up before changing anything. And while this solution worked for me, I can't guarantee the same results for other users.
Anyway I hope this helps any others who just might have the same error...