![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |