Skip to main content
Hello guys. 
I again. 
I'm trying to install MicroFocus Cobol Personal Edition for Visual Studio 2019 on my notebook 
with Win 10 64 bits but I'm having the following problem: The installer just opens and closes
 without doing anything. the interesting thing is that I created a virtual machine also with
 Win 10 64 bits and in this case it installs. I've looked for any and all references that exist 
about MicroFocus Cobol in my notebook to try to locate the problem, but nothing. 
I don't know what else to do to install.
 Any suggestion? 
Just don't tell me to reinstall Windows because I won't. 
Thanks in Advanced.
Hello guys. 
I again. 
I'm trying to install MicroFocus Cobol Personal Edition for Visual Studio 2019 on my notebook 
with Win 10 64 bits but I'm having the following problem: The installer just opens and closes
 without doing anything. the interesting thing is that I created a virtual machine also with
 Win 10 64 bits and in this case it installs. I've looked for any and all references that exist 
about MicroFocus Cobol in my notebook to try to locate the problem, but nothing. 
I don't know what else to do to install.
 Any suggestion? 
Just don't tell me to reinstall Windows because I won't. 
Thanks in Advanced.

You could try to run the installer directly from an administrative command prompt. Then if a message is displayed you might be able to see what it is.

There should also be a log file produced in the %TEMP% folder.
You can find out what this folder name is by entering

echo %TEMP%

in the command prompt.

The log file name will begin with Micro_Focus_Visual_COBOL...

You could try to run the installer directly from an administrative command prompt. Then if a message is displayed you might be able to see what it is.

There should also be a log file produced in the %TEMP% folder.
You can find out what this folder name is by entering

echo %TEMP%

in the command prompt.

The log file name will begin with Micro_Focus_Visual_COBOL...

Ok. I will try this.

Thanks very much for your answer.

You could try to run the installer directly from an administrative command prompt. Then if a message is displayed you might be able to see what it is.

There should also be a log file produced in the %TEMP% folder.
You can find out what this folder name is by entering

echo %TEMP%

in the command prompt.

The log file name will begin with Micro_Focus_Visual_COBOL...

Hello. I removed and reinstalled java sdk and java rte but with no result.
Here is the installer log just like the other times.
[226C:2248][2022-05-31T14:40:36]i001: Burn v3.14.0.1703, Windows v10.0 (Build 19044: Service Pack 0), path: C:\\WINDOWS\\Temp\\{F7D0884F-9271-405B-8F43-431A9A1B68CB}\\.cr\\vcvs2019_60.exe
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'ProductRevision' to value '6.0.00245'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'InstallFolder' to value '[ProgramFilesFolder]Micro Focus\\Visual COBOL'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'RumbaCheckbox' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'RumbaCheckboxState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'RumbaLabelState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'EclipseLabelState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'FolderEditbox2State' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'BrowseButton2State' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'ignorechecks' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipsafenet' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipusagelogger' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'downloadmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'installmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'novsix' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'accepteula' to value 'no'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'VS2017ValidInstance' to value '1'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'VS2019ValidInstance' to value '1'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'DockerService' to value 'SYSTEM\\CurrentControlSet\\Services\\cexecsvc'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable '32BitOSEclipseMsgState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'VS2017HelpMsgState' to value 'enable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'VS2019ValidCheck' to value 'yes'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'UpgradeRegKey' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\4.0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'NucleusRegKey2' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\4.0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'NucleusRegKey' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\6.0'
[226C:2248][2022-05-31T14:40:36]i009: Command Line: '"-burn.clean.room=C:\\From VmWin10\\vcvs2019_60.exe" -burn.filehandle.attached=216 -burn.filehandle.self=220'
[226C:2248][2022-05-31T14:40:36]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\\From VmWin10\\vcvs2019_60.exe'
[226C:2248][2022-05-31T14:40:36]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\\From VmWin10\\'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleLog' to value 'C:\\Users\\juran\\AppData\\Local\\Temp\\Micro_Focus_Visual_COBOL_for_Visual_Studio_2019_20220531144037.log'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleName' to value 'Micro Focus Visual COBOL for Visual Studio 2019'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleManufacturer' to value 'Micro Focus'
[226C:338C][2022-05-31T14:40:37]i000: Running detect BA function
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable 'HFDetected' to value '0'
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable 'HFDetected' to value '1'
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable '32BitOSEclipseMsgState' to value 'disable'

I'm about to give up.
Tks again.
Hello. I removed and reinstalled java sdk and java rte but with no result.
Here is the installer log just like the other times.
[226C:2248][2022-05-31T14:40:36]i001: Burn v3.14.0.1703, Windows v10.0 (Build 19044: Service Pack 0), path: C:\\WINDOWS\\Temp\\{F7D0884F-9271-405B-8F43-431A9A1B68CB}\\.cr\\vcvs2019_60.exe
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'ProductRevision' to value '6.0.00245'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'InstallFolder' to value '[ProgramFilesFolder]Micro Focus\\Visual COBOL'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'RumbaCheckbox' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'RumbaCheckboxState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'RumbaLabelState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'EclipseLabelState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'FolderEditbox2State' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'BrowseButton2State' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'ignorechecks' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipsafenet' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipusagelogger' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'skipmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'downloadmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'installmstools' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'novsix' to value '0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'accepteula' to value 'no'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'VS2017ValidInstance' to value '1'
[226C:2248][2022-05-31T14:40:36]i000: Initializing numeric variable 'VS2019ValidInstance' to value '1'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'DockerService' to value 'SYSTEM\\CurrentControlSet\\Services\\cexecsvc'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable '32BitOSEclipseMsgState' to value 'disable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'VS2017HelpMsgState' to value 'enable'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'VS2019ValidCheck' to value 'yes'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'UpgradeRegKey' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\4.0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'NucleusRegKey2' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\4.0'
[226C:2248][2022-05-31T14:40:36]i000: Initializing string variable 'NucleusRegKey' to value 'SOFTWARE\\Micro Focus\\Visual COBOL\\6.0'
[226C:2248][2022-05-31T14:40:36]i009: Command Line: '"-burn.clean.room=C:\\From VmWin10\\vcvs2019_60.exe" -burn.filehandle.attached=216 -burn.filehandle.self=220'
[226C:2248][2022-05-31T14:40:36]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\\From VmWin10\\vcvs2019_60.exe'
[226C:2248][2022-05-31T14:40:36]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\\From VmWin10\\'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleLog' to value 'C:\\Users\\juran\\AppData\\Local\\Temp\\Micro_Focus_Visual_COBOL_for_Visual_Studio_2019_20220531144037.log'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleName' to value 'Micro Focus Visual COBOL for Visual Studio 2019'
[226C:2248][2022-05-31T14:40:37]i000: Setting string variable 'WixBundleManufacturer' to value 'Micro Focus'
[226C:338C][2022-05-31T14:40:37]i000: Running detect BA function
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable 'HFDetected' to value '0'
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable 'HFDetected' to value '1'
[226C:338C][2022-05-31T14:40:37]i000: Setting string variable '32BitOSEclipseMsgState' to value 'disable'

I'm about to give up.
Tks again.

Do you have a previous version of Visual COBOL installed on this system? It appears to be finding a V4.0 in the Windows Registry.

Does Windows Control Panel ->Programs and Features show any Visual COBOL products either in the main list or under View Installed Updates?

Do you have a previous version of Visual COBOL installed on this system? It appears to be finding a V4.0 in the Windows Registry.

Does Windows Control Panel ->Programs and Features show any Visual COBOL products either in the main list or under View Installed Updates?

Hi Chris. 
In fact some time ago I had a version installed on my computer but I had already removed it.
I searched the registry and program files and found some references to it. 
I removed them all. 
I reinstalled java.
I tried to install visual cobol again but unfortunately it didn't work.
I appreciate the help.
 Greetings

You could try to run the installer directly from an administrative command prompt. Then if a message is displayed you might be able to see what it is.

There should also be a log file produced in the %TEMP% folder.
You can find out what this folder name is by entering

echo %TEMP%

in the command prompt.

The log file name will begin with Micro_Focus_Visual_COBOL...

Hello Chris.
I was able to install Visual Cobol Personal Edition.
In a stroke of luck I changed the compatibility of the installer to windows 8 and everything worked.
I think that as originally windows was version 8 and was updated to version 10 it gave this problem
Thanks for your help.
Terms & ConditionsAccessibility statement