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

Thanks for clarifying John. It look like then, that I have the update, and it doesn't work. Just great. I have the update .1000....and still have the problem. Windows update (I don't know what Click2Run is), uploaded 2 new ones, but the PPT build number did not change. I rebooted just in case that would help, but it didn't.

Hi Linda,

I feel your pain. This issue started for me well over a year ago.

The first time I saw it was when a client sent me back a PowerPoint I sent to him and his reply was...

"All the images are gone."  Thus began my nightmare.

If this is just starting for you, consider yourself fortunate, even though that doesn't help you ready for your Wednesday presentation.

Now, if you have your presentation and the images are all gone, running the fix won't get them back.

I found the only solution there is reinserting the images. I don't have a clue how many hours I've put into going back and reinserting images back into broken presentations.

My problems stopped when I changed the backup software I was using.  I've also since gone to Win 8 on a new computer and haven't seen this reoccur for a few months now.

If the fix has done it's job, and I can't speak to whether it has nor not since my fix occurred long before MS rolled out their fix. But from what I understand this shouldn't happen to new presentation created with the latest build. If it does, I'm sure MS wants to know about it.

Good luck with that and i wish you much success as you try to get ready for Wednesday.

Oh, wow, John, how awful! This is crazy...I'm thinking "recall"!!

I just bought a Surface RT just to give presentations (heck of a big decision for me..being unemployed now for 6 years. Teaching seems to be the only way I can make money in this sucky economy). This is my FIRST presentation with PPT AND it's in front of retired University grads...bad timing to say the least.

So I do have Windows 8. I did reinsert all the photos, but they randomly disappear again. Gremlins.

Anyway, I greatly appreciate the time you spent trying to help me out. Really great of you!

Linda

Oh, wow, John, how awful! This is crazy...I'm thinking "recall"!!

I just bought a Surface RT just to give presentations (heck of a big decision for me..being unemployed now for 6 years. Teaching seems to be the only way I can make money in this sucky economy). This is my FIRST presentation with PPT AND it's in front of retired University grads...bad timing to say the least.

So I do have Windows 8. I did reinsert all the photos, but they randomly disappear again. Gremlins.

Anyway, I greatly appreciate the time you spent trying to help me out. Really great of you!

Linda

You might try this, as long as you are having to reinsert anyway.  Work on a slide at a time and after each image is inserted do a save to a new file.  That way if you do break one you can always fall back to the previous save.

If you get some message that the file is read only, that usually means the act of saving will break the file. IF not you can likely safe successfully. If you do break the file just open the last save and do a different edit sequence. I know it sounds nut, but I discovered if I would add a text box or shape before I inserted and image I might get it to save. I would simply dd those off slide so they didn't matter.

Once you get everything saved you can go back and delete the older save-as files.

I know it's a PITA but it might be the only way to get through it.  Once I found the safe-often trick the lost image thing rarely cost me more than a few minutes and I could always move forward.  

Because what we found as a root cause being some kind of file sharing or file backup application you might want to turn of syncing to any file sharing app you might be running such as Dropbox or Google Drive. Don't know if that will help but it couldn't hurt to at least get you though the next day or so.

MM

I believe Dropbox is a primary culprit. I've only ever seen this happen when an open file is saved periodically over a long period of time to a synced Dropbox folder.