Business Graphics Products - Support Blog

What is BGP? Stands for Business Graphics Products. We are the Commercial Technical Support team at Microsoft that supports PowerPoint, Publisher, and Visio.

New Security Update MS11-022

New Security Update MS11-022

  • Comments 46
  • Likes

Hotfix for Security Update MS11-022 released publicly as MS11-036


MS11-036: Description of the security update for PowerPoint 2002: May 10, 2011

Security Update for Microsoft PowerPoint 2002 (KB2535802)

MS11-036: Description of the security update for PowerPoint 2003: May 10, 2011

Security Update for Microsoft Office PowerPoint 2003 (KB2535812)


MS11-036: Description of the security update for PowerPoint 2007: May 10, 2011

Security Update for Microsoft Office PowerPoint 2007 (KB2535818) -


Please review the ‘Known issues with this security update’ section of any of the KBs.


Hot Fix for Security Update MS11-022 Now Available



The hot fix is now available for the PowerPoint 2003 Security Update MS11-022. If you had previously removed the security update MS11-022, you do not need to reinstall it. Since the hot fix is cumulative, just install the hot fix and you should be secure.


The hotfix for PowerPoint 2002 -


For deployment, the security team that produced the hotfix suggests:

“Once the PowerPoint hotfix becomes available, we suggest applying the hotfix via normal means of hotfix deployment. This would include installing it manually or by using tools such as SCCM/SMS or other 3rd party tools.”


The following blog entry offers some resources on how to publish MSP’s to internal WSUS deployments:

·         Adding Cumulative Updates to display in Windows Server Update Services Console:



For the latest on this issue see Office Sustained Engineering blog post

After applying MS11-022 you may receive the following error when attempting to open a PowerPoint presentation in PowerPoint 2003:

“PowerPoint was unable to display some of the text, images, or objects on slides in the file, "filename", because they  have become corrupted. Affected slides have been replaced by blank slides in the presentation and it not possible to recover the lost information. To ensure that the file can be opened in previous versions of PowerPoint, use the Save As command (File menu) and save the file with either the same or a new name.”

For more information, please see KB2464588 MS11-022: Description of the security update for PowerPoint 2003: April 12, 2011


  • Save a copy of the file, edit, and save.
    • Open presentation in PowerPoint 2003, after receiving the prompt click OK. File/Save As to save a copy of the file, make a minor modification (delete one character, insert it back), save the file.
  • Remove backgrounds and delete images from slide master.
  • Open file in 2007, make small change, and save.
  • Open file in 2007 and remove backgrounds and images in slide master.
  • Open file in 2010 and save as PPTX.
  • Open file in 2007 and save as Web Page (*.htm; *.html), then save back as ppt.
  • Please note that KB2464588 (4/12/2011) does not fix this problem.

  • Thanks Aaron! (and a Big Thanks! to Susan Bradley!)

    It was a nightmare yesterday!

    Uninstalling "Security update for PowerPoint 2003 (KB2464588): POWERPNT" has worked for me. I've not been prompted to insert the disc that contains Microsoft Office PowerPoint 2003. Had made it two times, using W7 and using Windows XP.

    Thanks! (Again)

  • Yes, I had the same issue with several users over the last 2 days. Once KB2462588 was installed, all of our images in Powerpoint were generating the corruption error message. I uninstalled the patch on all users and everyone is working fine. The Powerpoint files that were having the errors, are now working correctly. I didn't have to reboot either or get prompted for the install files for Office 2003. I am frustrated that when I searched on MS Knowledge yesterday with the error message, I didn't find anything referencing this problem.

  • Do you guys at Microsoft actually test anything? Do you know how many people and files this affected? Do you know how much time has been wasted?

  • So according to what i read here, I have to go through a file server serving about 500+ users to find all ppt files then open 1 by 1 in office 2007 etc.... and then the problem is fixed, well I really like the idea that MS serves us with a brilliant patch "corrupting" powerpoint files...and this is the best what MS could come up with...I'm very sorry but for me the best sollution as support engineer was to go back to the WSUS server and mark the update for approval removal...the issue was fixed in no time.

    I hope that the next security patch for powerpoint fixes the security leak, but leaves my powerpoint files just the way they were.



  • I was also affected by this, and the similar problem with the Excel Security Update that rendered me unable to even open the program.

    After 5 hours of work, I successfully deleted the offending updates, but already, my computer wants me to reload them. These should be eliminated by Microsoft and an appropriate update that works would then be welcome.

    BTW, I attempted to inform Microsoft of the problem, and those options are offline!

  • I had this problem too.

    After uninstalling the Security update for PowerPoint 2003 (KB2464588), most of my ppt files now open correctly, but now I get another nasty error: when I copy slides from a ppt file to another ppt file, if I select the "Keep source format" option, Powerpoint immediately crashes.

    Has anyone the same problem?

  • Unbelievable! I spent hours trying to figure out why my ppt kept crashing and giving messages about corrupt files. Finally saw online that the Security Update is actually CAUSING the problem. In the "Workarounds" - are they 6 different workarounds? Doesn't seem to make much sense. If it is, I tried #1 and it doesn't work for me.  Best workaround: UNINSTALL THE UPDATE!

  • I continue to be incensed over this. I hope that everyone will complain to Microsoft and insist on a patch that works properly.

  • In my Blog i explian how to Uninstall the Patch with Software Deployment for the german and english version. You can't uninstall or revoke it via WSUS. You can deny in WSUS but it want uninstall on the client.

  • Mike, thanks for posting the scripted uninstall instructions -- very helpful.  I'm sure what you posted was enough for someone who actually knows what they are doing, but I had to make some modfications to get it to work for me.  

    On the msiexec.command, the /package has to exactly match the package code for your installation of Office.  Mine did not match the one on the blog. You can find GUID in regedit under HKLM\software\microsoft\windows\currentversion\uninstall (just search for Office).  

    Then, for whatever reason, I was unable to get the /uninstall (package code) version to work.  It would always complain that the patch package could not be opened and to verify that it actually exists.  

    I had more success in providing the path to the MSP.  But my MSP was not in a directory c:\edv as shown in the example.  I'm not sure what c:\edv is or why the MSP would be found there, but it can be found inside the CAB file as Mike  mentioned.  Once I extracted that and referred to the path where I stored it, everything was fine.

    You can find the MSP file here:


  • This is far too complicated. My system works at present, and I'm not going to risk rendering it inoperative again using a procedure I can't follow. Microsoft has to provide a patch that works. Until then, the evil PowerPoint and Excel patches will remain uninstalled on my machine.

  • I can't believe that once this problem was discovered that the hotfix wasn't over written.  I came to church this morning, only to find this problem.  I don't have the office cd with me, so powerpoint is not going to be used today!  

    Thanks Microsoft! (sarcasm if you can't tell!)

  • Its just a DOS attack by Microsoft to force everyone to upgrade.

  • We only have 2003.  PowerPoint freezes instantly, so making a change and saving it isn't an option.  When is there going to be a fix for this?  We are a few weeks away from an annual user group conference and have already lost hours trying to fix this.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment