PowerPoint 2013: Images in presentation disappear - and are replaced with 'The image part with relationship ID rId2 was not found in the file'

Anonymous

I've used PPT for 20 years and started using PowerPoint 2013 through Office 365 2 months ago and this has happened to me 4 times.

1. I create a presentation (Using copy and paste and/or insert to include pictures and other images)

2. After working on the presentation for a while I save the file and realize all the images (except smart art) are gone and replaced with the message above.

3. I have reinstalled PPT 2013 and it happened again. I have documents that are 50 pages long and have had to insert new images (Hours of lost work) then 3 days later it happens again.

Not sure if it is related but I've noticed that once in a while when I try to save a document (Happens in Word and Outlook Calendar items) it tells me the file is locked and makes me save under a new name.

This is really a show stopper. Any suggestions?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

UPDATE:

I know it's been a while since our last update but that's only because we've been hard at work on a solution and doing our best to ensure that it really does eliminate the problem.

Good news - we think we've finally fixed all instances of this bug. The update is now available and how you get it will depend on your version of Office:

Click-2-Run: you should receive the update automatically
"Traditional" install: update will be available via Microsoft Update

The correct build number once the update is installed is:

MSI: 15.0.4613.1000
C2R: 15.0.4615.1001

Obviously we'd love your feedback once you've installed the update. If for some reason you continue to hit the issue please post back here and be sure to include which build of PowerPoint you have as well as any other sync/anti-virus software you may have installed.

We're deeply committed to eradicating this issue and while we've done extensive testing there's always the possibility that something slipped through the cracks.

Thanks,

Dan

0 comments

513 additional answers

Steve Rindsberg 99,176 Reputation points MVP Volunteer Moderator

2013-09-14T15:41:35+00:00

There's never much Microsoft presence here. It's us and a few "hired help" who aren't support engineers or developers and who don't even seem to have a channel they can use to report problems TO the developers.

I can promise you that the developers ARE aware of the problem.

But honestly, I'd stick with 2010 until the developers SOLVE the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-14T15:54:27+00:00
It just really bakes my biscuits to be pushed to upgrade to a product that is now virtually unusable.
- Rant avoided successfully! -
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-14T15:58:42+00:00

I got an email from one of the MVPs about this issue yesterday. I was told the other MVPs are beating up MS about this issue on a regular basis. MS is aware of the problem but apparently are not able to recreate it and if they can't recreate it they can't begin to understand it or fix it.

To a certain extent Microsoft may view an issue they can't recreate as a non-issue.

I'm not judgin' I'm just sayin'....

Mickey Mills

www.presentationwow.com
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-14T18:30:13+00:00

I got an email from one of the MVPs about this issue yesterday. I was told the other MVPs are beating up MS about this issue on a regular basis. MS is aware of the problem but apparently are not able to recreate it and if they can't recreate it they can't begin to understand it or fix it.

To a certain extent Microsoft may view an issue they can't recreate as a non-issue.

I'm not judgin' I'm just sayin'....

Mickey Mills

www.presentationwow.com

I know you aren't excusing Microsoft and I get how hard it is to find intermittent problems. But in my years of software development it was never ok to say that because I can't fix the problem, you don't have a problem. I think this issue is a bit of a time bomb for Microsoft. When the complaints stop being from a bunch of consultants and begin coming from major corporate and government clients, I suspect there will be more resources put on the problem. Until then I would like to see a "caveat emptor" stamp on the Office 2013 advertising.
Was this answer helpful?

0 comments No comments