We were able to get past the issue in one case by logging a test user into the affected machine (this created a fresh user profile) and starting Outlook (which created a fresh mail profile) and instead of getting the error dialog, we instead were prompted for the location of ProPlus.WW\propsww2.cab - and pointing to that cab fixed Outlook for both the test user and the original user on that machine.īased on what was approved on WSUS yesterday, it may have been one of this list of updates (by KB) - Or maybe this problem has nothing to do with any of these updates. We've also tried disabling all Outlook addins without success. The symptom is that Outlook 2010 fails to start on Win7 64 computers with a dialog complaining that the "Windows Installer couldn't be started". ProPrWW2.cab file errors can be caused by various factors, so its is beneficial to try to fix them using various methods. Most times when we see problems with a bad Microsoft Update, it's easy to find other folks talking about it online - but this time it seems to just be a small subset of our users.
0 Comments
Leave a Reply. |