Media Encoder fails to Launch - GPUSniffer, reinstallation also fails.

Adobe ME version 22.0 through 22.6.1

PC Platform,  Windows Server 2019

I've seen this in a couple of locations.  We have ME running both as a application, and as a service.  On specific hosts, ME fails to launch with GPUSniffer errors.  When I tried to uninstall and reinstall ME on these machines, the installer failed with:

Exit Code: 184
-------------------------------------- Summary --------------------------------------
 - 2 fatal error(s), 2 error(s), 5 warnings(s) 

FATAL: Error (Code = 184) executing in command 'MoveFileCommand' for package: 'AdobeMediaEncoder22AllTrial', version:22.1.1.25
FATAL: Error occurred in install of package (Name: AdobeMediaEncoder22AllTrial Version: 22.1.1.25). Error code: '184'
ERROR: CopyPrimitiveEx | GetAnyOperationsAborted failed with error: 0
ERROR: CopyPrimitiveEx | GetAnyOperationsAborted failed with error: 0
WARN: File C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol locked with Process GPUSniffer.exe
WARN: File C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol locked with Process GPUSniffer.exe
WARN: File C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol locked with Process GPUSniffer.exe
WARN: File C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol locked with Process GPUSniffer.exe
WARN: Unable to move file at "C:\adobeTemp\ETREA18.tmp\1\universal\App\typesupport\cmaps\WP-Symbol" to "C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol" Error 32 The process cannot access the file because it is being used by another process.. Try setting correct permissions to the specified file/folder or parent folder, so that admin has rights to modify it.
-------------------------------------------------------------------------------------

Based on these logs, I went through the C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport and noticed this directory was tagged as read-Only.  
I went ahead and removed the read-only flag and changed permissions to be completely open.  Even after these changes, the installer still fails with the same errors.