When checking the C:\TMPatch.log, you found the following error:

• Access path denied

  An exception occurred
  Error code: 5 
  Message: Access to the path '<path\file_name.extension>' is denied.

• Used by another process

  [CopyFile] Copy file from ...
  [RollBackFiles] An exception occurred:
  Error code: 32
  Message: The process cannot access the file '<path\file_name.extension>' because it is being used by another process.
  

To resolve the issue:

1. On the Apex One server, stop the Apex One Master Service via services.msc.
2. Open C:\TMPatch.log using text editor
3. Search for the error codes or messages from the above reference. You may also use "fail" or "failed" keyword for file copy errors.
4. Go to <path> from the error message
5. Rename the affected file by appending .bak to the file name. As an example:
   perfLWCSPerfMonMgr.dll toperfLWCSPerfMonMgr.dll.bak.
6. Rename C:\TMPatch.log to TMPatch.log.bak.
7. Restart the Apex One Master Service.
8. Re-run the patch.

• Access denied

  [KillProcessByName] Found (1) process Name: (<process_name>).
  [KillProcessByName] Image Path: (<path\file_name.extension>)
  [KillProcessByName] Process ID: (<PID>)
  [KillProcessByName]An exception occurred:
  Error code: 16389
  Message: Access Denied.

To resolve the issue:

1. On the Apex One server, stop the Apex One Master Service via services.msc.
2. Open C:\TMPatch.log using text editor
3. Search for the error code or messages from the above reference.
4. Stop the <process_name> via Task Manager.
5. Rename C:\TMPatch.log to TMPatch.log.bak.
6. Restart the Apex One Master Service.
7. Re-run the patch.

If it still fails to complete the installation, a check of the newly generated TMPatch.log is required.

In some instances, a second attempt still fails and is observed. The procedure to rename the file or stop the process is similar to the instructions above, just make sure that the correct path to rename the file is followed.
 

If further assistance is needed, please contact Trend Micro Technical Support.