BUG: after completing an update AdobeARM should not incorrectly warn user that a reboot is needed before starting Acrobat Reader DC
After I was finally able to complete a manual upgrade from v24.001.20629 to current v24.002.20687 I was informed that a reboot was needed before using Acrobat Reader. However after more investigations I did I found that only reason why Acrobat Reader told me so was that he found some of own components of previous version, still running even Acrobat Reader was not running. So here's list of such applications:
- AdobeCollabSync.exe,
- WCChromeNativeMessagingHost.exe.
In specific this last one could not be closed silently by Acrobat Reader manual upgrade during own installation and remained running even after end of successfully completed upgrade. After that he wrote inside C:\Windows\Temp\ArmReport.ini
"[SESSION]
PingFilesList=DownloadManifestSuccessBITS;UpdateInstallReboot
..." but after I manually forced WCChromeNativeMessagingHost.exe I also discovered that same application was anyway already updated properly into own path 'C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\Browser\WCChromeExtn\WCChromeNativeMessagingHost.exe' and same file was not even mentioned into HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations REGMULTISZ list typically used when files already in use can only be updated properly after a reboot took place.
So basically this also means that after completing an update AdobeARM should not incorrectly warn user that a reboot is needed before starting Acrobat Reader DC, and might have simply just informed me that before starting Acrobat Reader DC I'd just better have to manually close WCChromeNativeMessagingHost.exe still running component of previous version.
P.S. Please note that I'm unable to upload involved ArmReport.ini because upload of this file is not allowed.