Skip to main content

Windows 10 updates on client machines (no rhyme or reason as to which version or build of Windows 10 this occurs in are removing the comdlg32.ocx activeX file from the Windows system directory (Syswow64 on 64 bit systems) . To fix this, we need to gain admin access to the workstation – run an elevated command prompt and re-register the comdlg32.ocx after placing a copy of it back in the system folder.

Anyone know of a replacement I can use in RMCOBOL-WOW instead of the comdlg32.ocx? 

Windows 10 updates on client machines (no rhyme or reason as to which version or build of Windows 10 this occurs in are removing the comdlg32.ocx activeX file from the Windows system directory (Syswow64 on 64 bit systems) . To fix this, we need to gain admin access to the workstation – run an elevated command prompt and re-register the comdlg32.ocx after placing a copy of it back in the system folder.

Anyone know of a replacement I can use in RMCOBOL-WOW instead of the comdlg32.ocx? 

There isn't a replacement for comdlg32.ocx -- this is an ActiveX wrapper for the Windows common dialogs. I have no idea why Microsoft would remove this as part of a Windows update.  Replace, yes, but not remove.

I did find some reports from 2016 discussing the same problem in a specific Windows update package:

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/kb3139940-breaks-vb6-application-with-error-about/da4707bb-bdee-4f22-8d17-2b3924115bf3?page=1

https://social.technet.microsoft.com/Forums/windows/en-US/7fd4d8ff-aa02-4bb5-80c4-2851b9232b0f/kb3139940-breaks-vb6-application-with-error-about-mscomctlocx?forum=w7itproinstall&ppud=4

I'll check around a bit more just in case there are more recent reports. but I don't think this is a problem we can solve from our end.  As far as I can tell, none of our Windows 10 test machines are being damaged in this way.