View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011546 | MMW v4 | Install/Config | public | 2013-12-05 02:43 | 2013-12-10 16:28 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | feedback | Resolution | open | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | ||||
| Summary | 0011546: Uninstall: Sometimes deletes MSSCRIPT.OCX from system32 | ||||
| Description | Uninstall MMW from x64 System sometimes prompts for MSSCript.ocx Deletion and even user say NO, MSSCRIPT.OCX is still deleted from system32 folder. That makes known error issue http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=116 NOTE: MSSCRIPT.OCX is older than those in newer Windows Versions and should not be deleted from System32 at all, especially if it also exits in SysWOW64 and is newer version. There is workaround: 1. Restart System 2. Install MMW 3. Copy MSSCRIPT.OCX from System32 to SysWOW64 4. Follow steps from http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=116 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Peke, I cannot replicate at all on any of my system, but thinking about it and based on the info (that the same happened to me in the past when uninstalling J.River Media Center 0008930), I guess that is must do a third party app. Most probably MS itself when unstalling the COM server or any AV software as MSSCRIPT.OCX can be considered by virus by AV software: http://virus-com.com/viruscom/viruscom_86376.html But because it happens during uninstall then the former is more probable, but could you disable AV temporarily to see if this could be the cause? Could you do screenshot of the dialog that asks for removing the OCX, I guess it is a system dialog, right? I guess it will be definetly resolved in MM5 by 0002747 EDIT: I guess that the workaround should be to install MMW again, isn't it? It was the workaround in 0008930 |
