Stop-Process -ProcessName explorer -Force Even though Explorer will immediately relaunch, just stopping it was enough for the installation to complete successfully. SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSIAE0A.tmp-\Ĭalling custom action CustomActions!_CleanNamespaceDLLSĪt (Int32 processId, Int32 access, Boolean throwIfExited)Īt (Int32 access, Boolean throwIfExited)Īt _CleanNamespaceDLLS(Session session)ĬustomAction CleanNamespaceDLLSCustomAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)įor those looking to do the same, the below PSADT code is what worked for me. DLL: C:\WINDOWS\Installer\MSIAE0A.tmp, Entrypoint: CustomAction_CleanNamespaceDLLS MSI (s) (F0:C8) : Invoking remote custom action. Thoughts? MSI (s) (F0:20) : Executing op: CustomActionSchedule(Action=CleanNamespaceDLLSCustomAction,ActionType=1025,Source=BinaryData,Target=CustomAction_CleanNamespaceDLLS,) The below is from the failed uninstall log - appears it is trying to kill explorer but is getting an "Access is denied". It is a PSADT script which works if I run it outside of Software Center with admin privs but fails when done via Software Center. As a general rule, if someone has flair, they almost definitely know what they're talking about.Īnyone get Autodesk Desktop Connector to uninstall using a script? All my attempts have led to failure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |