Is anyone else encountering this issue? If so, how are you handling it?
Some Windows updates are removing the registry settings for the COBOL programs. The screenshots attached are an example of how it looks when the settings are erased. The other image shows how it should look. The synonyms tab holds the path for the programs. Unfortunately, there is no way to determine which workstations will lose these settings. It does not seem to be associated with a particular version or build. In order to resolve, the ini2reg needs to be run and re associated with the runcobol.ini. |
This is not something we've seen and is concerning. There's no reason a Windows Update should be messing around with this part of the registry.
Do you have any idea whether this (and the OCX problem) is being caused by a recent update, or are the machines being updated really far behind, and applying a large number of updates?
This is not something we've seen and is concerning. There's no reason a Windows Update should be messing around with this part of the registry.
Do you have any idea whether this (and the OCX problem) is being caused by a recent update, or are the machines being updated really far behind, and applying a large number of updates?
According to my Support Rep that reported this:
"We really don’t know how far they are behind or the schedule or criteria they are using to apply the updates in each customers environment. All I can tell you is that it does not seem to be across the board or associated with any particular version or build of Windows 10."
Is anyone else encountering this issue? If so, how are you handling it?
Some Windows updates are removing the registry settings for the COBOL programs. The screenshots attached are an example of how it looks when the settings are erased. The other image shows how it should look. The synonyms tab holds the path for the programs. Unfortunately, there is no way to determine which workstations will lose these settings. It does not seem to be associated with a particular version or build. In order to resolve, the ini2reg needs to be run and re associated with the runcobol.ini. |
Hi, It's true. I had the same mistake on 2 pc but I don't know the reason. Both pc run Win10 PRO ........
