If on Windows 7 and UAC is disabled, this should be an administrative command prompt-you can tell because the title of the window will start with “Administrator:” If on Windows XP this is already an administrative command prompt. Open an administrative command prompt by clicking start, then type cmd and press enter. Note: if you forget this step then the changes below will not work as they will be virtualized. Click Start, then type cmd in the search box, then right-click the command prompt and choose the Run as administrator option:
UPDATE (): You can avoid the UAC step above if you make sure you open the command prompt as an administrator. Step 1: Make sure you open the command prompt as administrator If the updates you make are virtualized, they will NOT work. The reason for this is that when UAC is enabled, the system will “virtualize” updates to system files that you make as an end user. Make sure the slider is set to Never Notify, and click OK. To disable UAC on a Windows Vista or Windows 7 click start, then in the search box type: uacĬlick on the Change User Account Control settings Pre-Requisite: The user making the changes described below must be logged in as an administrator, and if you are on a Windows Vista or Windows 7 computer, UAC must be temporarily disabled. Here are the steps: Step 1: Make sure you’re an admin and UAC is turned off: The new procedure involves un-registering the file, replacing it with a different version, registering that file, un-registering it, then putting back the original file and re-registering it. UPDATE: After many hours on the phone with many customers, I’ve found that the following procedure now works 100% of the time WITHOUT requiring a system restore and WITHOUT having to rollback the update:Īfter working with many customers on solving this issue, we now have a new procedure to follow that will allow you to fix the issue without the need for a system restore nor the need to un-install the update.
Presumably Microsoft will eventually ship a non-breaking version of these security updates that you can install later. The last step is to simply block the security updates from being applied by searching for updates, then right-clicking on these and choosing hide. Removing all the ones that do let you remove them, followed by a reboot, seems to allow you to remove the remaining ones. Note: Some of the updates don’t have a remove option however apparently due to a dependency of some sort. System Restore failed to replace the file _ with its original copy from the restore point.įor those customers we’ve then resorted to removing “Every” security update that is Microsoft Office related, regardless of version of Office, by going to the control panel add/remove programs / programs and features. So this solution sounds great and simple, only problem is that for my customers it hasn’t actually been working.Ī system restore, followed by blocking the update does work, but for many of my customers, the system restores have been failing with an error:
as Administrator or you’ll get a failure type of message such as: The module "mscomctl.ocx" was loaded but the call to DllRegisterServer failed with error code 0x8002801c). bat file, don’t forget that you have to run it with elevated privileges (i.e. %systemroot%\sysWOW64\regsvr32 mscomctl.ocx /s %systemroot%\sysWOW64\regsvr32 /u mscomctl.ocx /s %systemroot%\system32\regsvr32 mscomctl.ocx /s %systemroot%\system32\regsvr32 /u mscomctl.ocx /s If "%PROCESSOR_ARCHITECTURE%" = "AMD64" goto 圆4 bat file containing something like the following (below is my version of it that uses a better method to detect the bit-ness of the OffĮcho Re-Registering the MSCOMCTL.OCX file Rolling back the update / doing a system restore seems to solve the problem, but according to this Microsoft person’s blog entry, the problem is supposed to be fixable by just re-registering the. If this update is installed on a development computer, a new application created using it will exhibit the same error when delivered to a computer that DOES NOT contain the update. The issue is this KB if you’re running Office 2003: The issue is this KB if you’re running Office 2007: The issue is this KB if you’re running Office 2010: The cause is an update to the MSCOMCTL.OCX file (located in \Windows\System32\ on 32-bit machines or \Windows\SysWow64\ on 64-bit machines) has been made by the Microsoft Security update described in this bulletin: After the Windows Security Update, customers who open my app get errors such as: “Error: TheOpenForm action was cancelled.” My app uses MSComCtl.ocx to display a tree control.