| Name | Description |
|---|
| Unable to open .docx file after applying 981715 | After you install any update to the Office Compatibility Pack, the file associations may change back to the Microsoft Office Compatibility Pack (MOC.exe).
http://support.microsoft.com/kb/972581 |
| Opening office documents is slow due to hptcpmon.dll | When certain HP printer drivers are installed, Office applications are very slow to open or close. This is caused by the presence of the HP Digital Imaging Monitor.
http://support.microsoft.com/kb/947477 |
| Office files may be missing | When you change an Office file from the Internet, the file may be saved to an unexpected location.
http://support.microsoft.com/kb/827099 |
| Office programs may seem to stop responding (hang) when you open or save from a network location | When you try to open a file from a network location, the Office program may run very slowly or seem to stop responding (hang).
http://support.microsoft.com/kb/833041 |
| Graphic Filters Settings Present After MS10-105 | After you apply MS10-105, users cannot insert certain images into Office applications.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2479871 |
| The spelling checker does not flag misspelled words in Microsoft Word | When you type a misspelled word in Microsoft Word, it is not flagged by the spelling checker.
http://support.microsoft.com/kb/970826 |
| Microsoft Office Document Imaging (MODI) will freeze when opening .mdi files if Desktop Experience is installed | After you install Desktop Experience for Windows Server 2008 on a 64-bit Edition, Microsoft Office Document Imaging (MODI) or similar third-party writing applications will not respond to mouse commands when the applications are opened. However, those applications will still respond to keyboard commands. This issue occurs because the Desktop Experience installs a second instance of wisptis.exe in the C:\Windows\SysWOW64 folder, and this instance interferes with the instance of wisptis.exe that is installed in the C:\Windows\System32 folder together with Microsoft Office.
http://support.microsoft.com/kb/2203203 |
| Word 2007 PostScript Printer configuration | If SP2 is applied, and the user does not apply KB977031 together with the registry key that is listed, the user will experience missing parts of text boxes when he or she prints to PostScript printers if Charts or other Escher 2.0 objects are present.
http://support.microsoft.com/kb/977031 |
| Cannot follow hyperlink to Office document | This checks whether the ForceShellExecute registry value is enabled.
http://support.microsoft.com/kb/280680 |
| The Desktop is being redirected to a nondefault location | Office assumes connectivity to the desktop, and if the desktop is redirected, users can face hangs and crashes in Word when they try to open or save documents.
http://support.microsoft.com/kb/257757 |
| Google Desktop | When Google Desktop is present, it caches user passwords without asking the user. This means that documents that would typically require a password to open can be opened without the user having to supply the password. |
| Word Convertor | When a file has a *.doc or *.docx file name extension but the content is a plain text file or another kind of file that is not a Microsoft Word binary file, and that file is opened in Microsoft Word, you may receive an error message.
http://support.microsoft.com/kb/973904 |
| You may be running an out-of-date version of Office | Office 2003 was detected on your computer. Check the Microsoft Product Lifecycle webpage for more information.
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=office+2003&Filter=FilterNO |
| Office 2010 Prerequisites Validation | Office 2010 requires Windows XP Service Pack 3 to be installed.
http://technet.microsoft.com/en-us/library/ee624351.aspx |
| Some settings for the Visual Basic Editor that were enabled previously are now disabled in Office 2010 | Visual Basic for Applications (VBA) is upgraded to version 7.0 in Microsoft Office 2010. Therefore, the registry entries that correspond to the settings for the Visual Basic Editor are located under a different subkey.
http://support.microsoft.com/kb/978753 |
| .lnk files in Office file locations | When .lnk files exist in default Office locations (for example, default documents and recent folders), users can experience delays in Office applications during open, save, and editing. |
| Incompatible Adobe PDFMaker add-in | Adobe PDFMaker X and later versions are recommended for use with Office 2010. Using legacy versions of PDFMaker could lead to known issues.
http://helpx.adobe.com/x-productkb/multi/known-issues-acrobat-9-pdfmaker.html |
| Check MAPI32 version for known MAPIAddress Regression | There is a known regression in Windows 7 and in Windows Server 2008 R2 that causes any application that uses the Simple MAPI functions, MAPIAddress or MAPIResolveName, to fail with the error MAPI_E_CALL_FAILED.
http://support.microsoft.com/kb/980681 |
| MS12-027 may cause third-party VBA forms not to load correctly | If you install this security update on a computer that has a third-party software solution installed, and the software solution is based on Microsoft Visual Basic for Applications (VBA), and the software solution creates an instance of the control directly through Microsoft Office, the control may not load in your solution.
http://support.microsoft.com/kb/2664258 |
| DFS configuration | If drives are mapped to DFS namespaces, but DFS is not configured on a file server, documents that are saved to the DFS mapped drive may not display within Windows Explorer after the documents are saved. |
| ACEOLEDB ClsId registration | The ClsId that is used with ACEOLDEB.dll has an incorrect path that is specified in the (default) value.
http://support.microsoft.com/KB/2459087 |
