Unable to launch Openedge products or install Service Pack on Windows

Unable to start OpenEdge Architect, Debugger or install an OpenEdge Service Pack on Windows

Launching prowin32 Data Dictionary or Data Administration fails with promsgs error

Launching OpenEdge Architect gives error:
Installation of an OpenEdge Service Pack fails with:
Starting OpenEdge Architect errors out with:
Debugger fails to start on Vista with following error messages:
Can't find where the Java VM executable is to run debugger. (14529)

Not licensed to run OpenEdge Architect for version: <version>

AdminServer does not start and does not create any log files.

Fail to execute report engine report.

No errors occur during the initial installation

To confirm this issue is hit, verify the registry keys. Affected installations will have an incorrect version number,  preventing various components to determine the location and version of the OpenEdge installation.
The version numbers show up as 10.1CÀ, 10.1CA~, 10.2AA, 10.2Bv, 11.2u or similar instead of just 10.1C, 10.2A,10.2B or 11.2.

• HKEY_CURRENT_USER\Software\PSC\PROGRESS and
• HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS or
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\PROGRESS\ if running 32-bit OpenEdge on 64-bit Windows

Registry corruption associated with the OpenEdge installation. 

During the installation the name of the registry key is stored in a buffer in a way that does not add a terminator to the end of the string.  
The memory associated with the buffer is sometimes filled with zeros which leads to the string ending up with a terminator by default.  This was not always the case.  The defect occurs when the string is copied over memory that was not filled with zeros.
In that case, when the string is recalled, it is returned with whatever characters or garbage was in memory at the end of the string.

Upgrade to OpenEdge 11.3 or later where this issue has been addressed, by ensuring that the string being written to the buffer is always terminated.

If an upgrade is not possible at this time, then use workaround described below to address registry corruption.

To address this Registry Corruption use the instructions described in Article:   Is there a tool to fix registry corruption?