Error Code 145 - problems updating Animate CC 2018
I am trying to update Animate CC 2018, partly in the hope of fixing another problem (Animate is not recognising my iPhone X since updating the firmware of that device, but will still see my iPhone 6 which I have not updated very recently) but also to stay on the latest version. The update is failing with the following messages:
Exit Code: 145
-------------------------------------- Summary --------------------------------------
- 2 fatal error(s), 0 error(s), 3 warnings(s)
FATAL: Error (Code = 145) executing in command 'MoveDirectoryCommand' for package: 'AdobeAnimate18.0-mul', version:18.0.1.115
FATAL: Error occurred in install of package (Name: AdobeAnimate18.0-mul Version: 18.0.1.115). Error code: '145'
WARN: target folder '/System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP/Adobe Animate CC 2018' does not exist, treating package 'AdobeAnimate18.0-en_US' as uninstalled
WARN: target folder '/System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP/Adobe Animate CC 2018' does not exist, treating package 'AIRforIOS_Animate18.0-mul' as uninstalled
WARN: Destination path is file or already used "/System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP/Adobe Animate CC 2018"
-------------------------------------------------------------------------------------
I have deleted and re-installed Creative Cloud and that makes no difference. I'd delete Animate CC but the files referenced in these messages are not in the Adobe folders but in general components section and I'm concerned that if I delete it without solving this issue I will only compound the problem. Also because I have re-installed CC it doesn't seem to recognise that I still have a version of Animate installed and (largely) working so would need to uninstall some other way which may not clean up the relevant folders and files. I can see as far down the path as AudioDSP but that seems to be an executable not a folder so can't see to the bottom of the path. But in any case the actual errors are to do with a MoveDiretoryCommand and I presume this initial failure is leading to everything else.
I did try to rename the folder temporarily but because it's owned by the system I don't seem to be able to make any changes.
Any thoughts on how to break the loop and update?
I am working on a Mac, OS High Sierra, version 10.13.2.
Thanks
Stephen
