Checklist before using Adobe Creative Cloud Cleaner Tool The tool will remove installation records for Adobe Creative Cloud or Adobe Creative Suite applications that may have become corrupted or may be causing problems with a new installation. It fixes problems files and issues in registry keys. It is used to clean up corrupted installations. The Adobe creative cloud cleaner tool is for users with more advanced computer knowledge. How to use Adobe Creative Cloud Cleaner Tool It can remove old Adobe software, clean corrupt installation files, and fix host files to establish a connection with the Adobe server. : Info: explorer.The Adobe Creative Cloud Cleaner Tool is for advanced computer users. : Info: explorer.killer: Process Restartable?: 0 (.337) : Info: explorer.killer: Process ID: 4572 (.336) : Info: explorer.killer: Process Name: Windows Explorer (.335) : Info: customhook: Couldn't elevate process privilege. When deployed via Configuration Manager Current Branch 1902 using the application model under system context you will see the above issue when the logged on user is a local admin. Instructions are provided at the same link." Your organization should discontinue usage of the unauthorized products shown at this link and update to the authorized versions. " IMPORTANT NOTICE: If you have not yet updated to the latest version of Creative Cloud, please note that you are no longer licensed to use certain older versions of the apps or to deploy packages containing these older versions. The original deadline to complete that was December 2019, that allowance has evidently now been removed and they are blacklisting nearly all previous versions of Adobe CC (from AdobeCC Admin website): I didn't save a copy of the 5 warning screenshots during the conversion process, but suffice it to say the conversion process seems to work. The process is relatively straightforward, but you will have to create all new packages and evidently manually uninstall previous versions. You only have 30 days to convert your entire organization over to the new scheme. Device Licensed machines with auto updates will upgrade to 2019 but not be able to activate (hence Trial Mode) You are required to migrate to Shared Device Licensing to continue using Adobe CC. Reposting the pertinent info that is now missing for people who are going into Trial Mode in 2019. Hmm, my replies disappeared and my last post got branched? : Info: explorer.killer: Initial Explorer restart SUCCESSFUL. : Info: explorer.killer: INFO: Restarted explorer processes in RestartManager session. : Info: explorer.killer: Process Restart Masked?: 0 (.349) : Info: explorer.killer: Process Shutdown Masked?: 0 (.348) : Info: explorer.killer: Process Error On Restart?: 0 (.347) : Info: explorer.killer: Process Error On Stop?: 0 (.346) : Info: explorer.killer: Process Restarted?: 0 (.345) : Info: explorer.killer: Process Stopped Other?: 0 (.344) : Info: explorer.killer: Process Stopped?: 0 (.343) : Info: explorer.killer: Process Running?: 1 (.342) : Info: explorer.killer: Process Status Unknown?: 1 (.341) : Info: explorer.killer: Process Restartable?: 1 (.337) : Info: explorer.killer: Process ID: 3148 (.336) : Info: explorer.killer: Process Name: Esplora risorse (.335) : Info: customhook: Attempting explorer restart as current user (.503) : Info: customhook: Running as admin (.502) : Info: registry.entries: Non essential registry entry setting: succeeded! (::SetCurrentUserEntries.335) : Info: customhook: Installing extension (.491) : Info: customhook: Successfully elevated process privilege (.159) : Info: customhook: Privilege does not exist elevating (.92) : Info: customhook: Value of Privilege0 (.86) : Info: customhook: Component given: CoreSyncExtension (.724) : Info: customhook: Invoked with args: '-install=C:\Program Files (x86)\Common Files\Adobe -component=CoreSyncExtension -mode=install' (.710) "C:\Program Files (x86)\Common Files\Adobe\Installers\CoreSyncInstall.log" Unfortunately I think it's "hard coded" inside the setup process so you can't modify it. If you try to execute that command you will see the exact behavior that happens during the installation! "C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension\customhook\CoreSyncCustomHook.exe" "-install=C:\Program Files (x86)\Common Files\Adobe" -component=CoreSyncExtension -mode=install It happens when the setup.exe tries to install CoreSyncCustomHook with the command: With Process Monitor I captured the command that close explorer.exe.
0 Comments
Leave a Reply. |