EOS check still reporting XCOM 11.6 after upgrade to 12.0

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

After automatic upgrade of XCOM for Windows 11.6 SP02 to 12.0 our EOS (End Of Service) scanner still records this server as being EOS because it is listed with version 11.6.
What could be causing this?
The corresponding TEST server does not have the problem and it is only the PROD/DR servers that report it.

Resolution

Running "xcomqm -r" manually from the %XCOM_HOME% directory and checking registry key "HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\XCOM" confirms 12.0 is correctly installed and running on the PROD server.

An xcom* files list from the root of the C: drive (dir /s xcom* > C:\temp\xcom.out) showed a directory listed alphabetically before the current XCOM installation and XCOM_R120BACKUP directories. That directory contained old files from 2014 and earlier which includes an "xcomqm.exe".
If the EOS scanner is searching for "xcomqm.exe" and it finds it first in that old directory then if it runs that version the result may well be a "11.6" string.
That old directory had already been removed from the TEST server where the problem does not exist.
After the directory was removed from PROD/DR and the EOS scanner re-run it no longer highlighted the server as still being at EOS level 11.6