Installing Patch for Visual Basic 6 (MS12-046/Q2688865) fails. This is often seen to include the returned exit code: -2147023728.
This appears to be a problem with the patch itself (rather than with our product). The issue has been presented to the vendor for correction, though no corrections have been made available to date.
If a supported version of an Office product is installed (BOTH version and SP), MS12-046 should be indicated as missing for both the Office product and the operating system.
In this case, installing (e.g. deploying) the Office patch will succeed, and future scans will show the patch as installed for both the Office product and for the operating system.
If both patches are deployed, the operating system patch installation will fail, but the Office product patch installation will still succeed, and future scans will show the patch as installed for both the Office product and for the operating system (the affected DLL gets updated).
If an Office product is installed, but the patch is not indicated as missing for that Office product, then the Office product is likely an older, unsupported version. After upgrading the Office product (i.e. to a supported version or service pack level), you should be able to proceed as outlined above.
If no Office product is installed, a third-party product installed the affected DLL, and the third-party should supply the necessary patch.
Installing the operating system patch manually (e.g. as a logged in user) will usually succeed, but may not patch the affect program. See Frequently Asked Questions "I have applied the required Microsoft security updates, but I still have an affected version of the Visual Basic for Applications runtime (VBE6.dll) on my system. How do I update this DLL?" in http://technet.microsoft.com/en-us/security/bulletin/ms12-046
If this does not correct your issue please consider checking with our community of users at
If you would prefer you may also submit a ticket for Technical Support at