OpenEdge 64 bit showcfg.exe shows 32-bit licenses instead of 64-bit OpenEdge 11.x licenses

64-bit 11.5.1 showcfg command shows 32-bit 11.5.1
64-bit 11.6.1 showcfg command shows 32-bit 11.6.1
64-bit 11.7.1 showcfg command shows 32-bit 11.7.1

32-bit and 64-bit OpenEdge Licenses are installed on the same Windows Server
32-bit showcfg command shows 32-bit licenses as expected

Not the issue described in the Article  OpenEdge 11.5 SP1 64-Bit overwrites 32-Bit registry 

OpenEdge 11.x 32-bit Registry Keys are correct and pointing to the correct %DLC%: OpenEdge 11.x 64-bit Registry Keys are correct and pointing to the correct %DLC%

When there is 32bit and 64bit co-exitence, 64bit showcfg reads the 32bit registry due to the 32-bit showcfg tool which is packaged in both the Windows OpenEdge 32bit and 64bit installer.

The 64 bit 11.5.1, 11.6.1 or 11.7.1  'showcfg' command is looking at the wrong "-bit" Registry Key: Instead of the 64-bit Registry Key:

This issue is only with the 'showcfg.exe' or 'showcfgd.exe' executable which has been inadvertently fixed since OpenEdge 11.7.2.

The %DLC%\progress.cfg can be explicitly referenced, the executable does not look in the registry or the progress.ini :
The progress.cfg can also be parsed with ABL code as detailed in Article:

•  How to read the progress.cfg file in ABL?   

While inadvisable, the relevant registry key for the Windows OpenEdge version in use can be deleted:

HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\<ver>\Startup\DLC

Not finding the HKCU entry, the HKLM Registry entry will be used instead:

HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\<ver>\Startup

Deleting the registry keys can be run from an elevated command line:

With the content of the file deleteDLCfromHCU.reg as follows:

Windows Registry Editor Version 5.00
REG EXPORT HKCU\Software\PSC\PROGRESS %TEMP%\HKUPRGS.REG
[-HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\11.5\Startup\DLC]
[-HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\11.6\Startup\DLC]
[-HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\11.7\Startup\DLC]

Progress Articles:

 How to identify which HKCU key is used by current session?  
 OpenEdge installation fails when logged on with a roaming profile