I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue. 

I have an odd problem.

I have 2 windows 10 machines running Windows 10 version 1803.

One has Pro 1803 and went through the 1709 fiasco, and the second one has home 1803.

On the home 1803 rm-cobol 7.0 runs like a champ, whereas on the Pro version 1803, RM 7.0  will not run. When I execute the batch to run the software the command line window appears, but the runtime does not appear as a process unless I 'X" the window.  The machine will run any program that does no screen i-o. Also the compiler will compile but will not open a window.  

I know this is odd, but any ideas?  I have been bashing my brains out on this for quite some time. Thanks in advance for any clues.

Let me add this: On the pro machine, the runtime will run (for a example a print-only program) if there is no screen i-o. As if it will not create a window. I should point out that this is a standard windows 10 machine with no special display options. The RM runtime ran perfectly until the introduction of build 1709 of Windows 10. This problem arose at that time and persists with build 1803.

Thanks again for any ideas regarding this bizarre issue.