#MSCOMCTL OSX DOWNLOAD UPDATE#
There is now a forum entry Office 2019 Pro C2R monthly Update ships wrong MsComCtl.ocx Fileversion in Microsoft Answers. Note: Why the two ocx also have to be in the directory "C:\Program Files (x86)\Microsoft Office\root\vfs\SystemX86" I haven't found out yet.Īddendum: Since the beginning of 2019, Microsoft has been delivering these no longer suitable OCX versions with every Office update (2019).
#MSCOMCTL OSX DOWNLOAD PATCH#
In the list of patches (Office Patchday ) this worse patch is of course nowhere to be found. MS simply doesn't talk about it. Really annoying and weak. Since I am prepared for this case I simply copy the mscomctl.ocx from the directory "C:\Windows\SysWOW64" into the directory "C:\Program Files (x86)\Microsoft Office\root\vfs\SystemX86" (overwrite) and then the list views will work again (without re-registration via Regsvr32). He wroteĭirectory C:\Program Files (x86)\Microsoft Office\root\vfs\SystemX86 Sam left me a feedback to my German blog post, indicating, that FebruOffice updates are shipping also the wrong OCX version. Register the OCX by RegSvr32 "C:\Windows\SysWOW64\MSCOMCTL.ocx".Īfter a re-registration of the replaced.Place an earlier version of the OCX () into C:\Windows\SysWOW64.Delete the OCX file from C:\Windows\SysWOW64 folder.Unregister the OCX by RegSvr32 /u "C:\Windows\SysWOW64\MSCOMCTL.ocx" in C:\Windows\SysWOW64.Within this Technet thread similar issues with Microsoft Office 365 ProPlus Build 10730.20264 and MSCOMCT.ocx are discussed. Probably because about 2 years ago the same misery has already happended. With the other Office versions I found absolutely no hints at Microsoft which patch will deliver the wrong MS Common Controls file version in Dec 2018 or Jan 2019.
#MSCOMCTL OSX DOWNLOAD MANUAL#
A manual deinstallation of the respective update is not possible. With Office 2019 C2R this is especially stupid, because there is only a new build. I have noticed that Microsoft delivers another wrong file version of the MS Common Controls (mscomctl.ocx) with the Office January 2019 updates. Blog reader Sam sent me the following text. I guess something like that happened again. In the past, Microsoft has always 'managed' it to use such updates to accidentally kill office add-ins or VB programs. The problem is that if the version numbers of the TypeLibs are changed, all Visual Basic and VBA applications that use these TypeLibs will no longer run. Unfortunately this breaks the compatibility. Microsoft has once again annoyed developers with the MS16-004 update, as it incremented the version of the typelibs of MsComCtl.ocx. At that time I had received the following information from a blog reader. The MS16-004 from 2017 update obviously leads to considerable compatibility issues with VB6 and VBA applications. I had discussed this case in the 2017 within my German blog post Januar-Update MS16-004 bricht MSComCTL.ocx.
0 kommentar(er)
