I am currently deploying Adobe Reader 10.1.3 MUI and I am seeing several machines fail the installation and report error 1321 (permissions issues). This is an issue because the installer removes the previous version of Reader and fails to install 10.1.3 which leaves the machine without Reader and results in impact to the end user. If I re-run the installation there is a good chance it will report a different file with permission issues, in other words its not always the same file it reports permission issues with. Regardless, I have manually confirmed the permissions and owner on the files and all parent folders are correct but the installer will still report permission issues. I see this on Windows 7 SP1 x64 and Windows XP SP3. The easiest way to get Reader to install succesfully is by running the installation over and over until it passes (you dont even have to make any changes to the machine, just kick it off until it installs succesfully). With all of this in mind I suspect the root cause to be Mcafee's real time scanning, my guess is that it is locking the file when its scanning and when Adobe's installer attempts to modify the file it fails because it is locked or in use by Mcafee. Usually, I would test this by disabling Mcafee and kicking off the installer however I am not able to do this due to security reasons. I have tried running procmon to see exactly whats accessing the files at that time but everytime I start procmon the installation will randomly pass and I cant reproduce the issue if procmon is running. Does anyone have any ideas on what I could do to help determine if it is in fact Mcafee causing the issue? Or possibly another suggestion as to what the root cause could be?
↧