To push out a corrected version of the affected OCX files ASAP. Our biggest issue is that no matter whether we're rolling back or copying a file, we're still having to deal with a very large volume of support calls and emails from customers that use our Excel add-in and have been impacted. You may want to temporarily disable automatic updates to prevent this. If you copy the file and it resolves the issue, keep in mind that if you have automatic updates enabled for Office, MS may push out anotherīad copy of the file and you'll have re-copy the file. osx files such as: TABCT元2.ocx, ssa3d30.ocx, COMCT元2.ocx, RICHTX32.ocx, comct232.ocx On average the system includes around 10,000 OCX files.These files are crucial program elements that are necessary for numerous functions or maintaining the program’s stability. That resolved the same issue we were having with MSCOMCTL.OCX and so it may also be a solution for TABCT元2.OCX. "C:\Program Files (x86)\Microsoft Office\root\VFS\SystemX86\"Īssuming that you still have the last good working copy stored under "C:\Windows\SysWow64", you can copy the file from that location into the above folder.ĬOPY "%systemroot%\SysWOW64\mscomctl.ocx" "%programfiles(x86)%\Microsoft Office\root\VFS\SystemX86\"
#TABCTL32.OCX ERROR REGISTRATION#
These TABCT元2.OCX registration problems are due to broken DLL file references. In rare occasions, TABCT元2.OCX errors with ActiveX are due to Windows registry faults. File corruption of TABCT元2.OCX loads it badly, leading to errors. Office keeps its own copy of the OCX file in the following folder: TABCT元2.OCX corruption, malware-infected ZoneAlarm Pro, and abnormal PC shutdowns can all lead to ActiveX errors. One solution is to roll back to 1706.Īnother solution may be possible by just copying the last good copy of the file. We don't use TABCT元2.OCX, so I wasn't aware that was also affected. We ran into the same problem with MSCOMCTL.OCX. With the 1707 release of Office 2016, MS is distributing some updated OCX files.