Thought I would jump in and provide details on how I was able to correct the issue.
Temporarily turn off User Account Control (UAC) and reboot your computer.
Right-click the Start button, then select Apps and Features. Select and uninstall all Articulate applications from your list of apps.
Right-click the Start button and click Run. Type powerpnt.exe /regserver into the Run dialog box and click OK. This repairs the registry keys for PowerPoint.
When the PowerPoint repair process is complete, reboot your computer. (Takes a little while to run, approximately 5 min.)
Right click the res13Cleanup.bat file and select Run as administrator. (This deletes the Studio registry keys and prepares the computer for a clean re-installation. It should only take a few seconds.)
Reboot PC
Re-install Articulate 360 and all Apps
Return User Account Control (UAC) to previous setting.
Thank you Marie. Turns out on mine the anti-virus software we use had taken the file and quarantined it. My support guy was able to release it and the add-in works now.
I had started another discussion on the same issue before finding this one. I have an open support case and a ticket in with our AV vendor because the ppam file is being quarantined. Their partial response on this is:
"The reason behind us (and several others) flagging this is due partly to the PushToExe wrapper around it. Basically this is a PowerShell script wrapped around an executable...this is also what a lot of malware uses too. The PowerShell code does do some funky things as well, but all in all this is a legitimate application."
I am having the same problem with the same message as the one originally stated. However Marie's solution above is pretty intimidating and I don't have administrative control. Is there an easier solution that is now available?
Hi Kerry, The error occurred again a week after we fixed it. After further analysis - my IT was able to determine that the add-in was being quarantined by our security software. Once that add-in was deemed safe and the computer was restarted. Everything starting working fine. You might want to reach out to your IT to see if its the same issue.
10 Replies
same error occurring to my team starting today.
Thought I would jump in and provide details on how I was able to correct the issue.
I hope this helps.
Thank you Marie. Turns out on mine the anti-virus software we use had taken the file and quarantined it. My support guy was able to release it and the add-in works now.
Ok, I'll add that to my list just in case it comes up again!
Thanks for popping back in with an update, Claire. I did not see a support case for you, so I was curious if you were back up and running yet.
Thanks for sharing your findings as well, Marie :)
We have two PCs that are suffering this same issue. I'll try the steps listed above.
I had started another discussion on the same issue before finding this one. I have an open support case and a ticket in with our AV vendor because the ppam file is being quarantined. Their partial response on this is:
"The reason behind us (and several others) flagging this is due partly to the PushToExe wrapper around it. Basically this is a PowerShell script wrapped around an executable...this is also what a lot of malware uses too. The PowerShell code does do some funky things as well, but all in all this is a legitimate application."
Hi Leslie, Yes, we are back up and running with the help of our IT. No need for a support ticket.
Claire
I am having the same problem with the same message as the one originally stated. However Marie's solution above is pretty intimidating and I don't have administrative control. Is there an easier solution that is now available?
Hi Kerry, The error occurred again a week after we fixed it. After further analysis - my IT was able to determine that the add-in was being quarantined by our security software. Once that add-in was deemed safe and the computer was restarted. Everything starting working fine. You might want to reach out to your IT to see if its the same issue.