Problems with pasting graphs into MS PowerPoint 2019

The Problem

Users report that copying Prism graphs as embedded or linked objects into Microsoft PowerPoint 2019 is impossible. This issue also occurs when using Prism's 'Send to PowerPoint' command. This problem is specific to Microsoft PowerPoint 2019, and does not affect Microsoft Word 2019, Microsoft Excel 2019, or other versions of Microsoft PowerPoint.

This issue is also not specific to Prism. We have observed difficulties with copying data into Microsoft PowerPoint 2019 from other applications including Adobe Illustrator (errors when pasting), Adobe Photoshop (unable to paste), and Wordpad (unable to paste). There may be other apps with the same issue.

Why does this happen?

This issue was first observed after the Volume licensed (corporate) version of Microsoft Office 2019 was patched with the update of July 9, 2024—Version 1808 (Build 10412.20006). We had not received any complains related to this issue prior to this update. Other Microsoft Office versions (including Microsoft Office 2016 and newer patches) do not exhibit this issue.

Microsoft recently released an update to Office 2019 (release date August 13, 2024, Version 1808, Build 10413.20020). However, this update has not resolved this issue based on our testing.

What can I do?

Paste as a picture. Copy graphs from Prism to PowerPoint using the 'Paste Picture' option. First, copy the graph from Prism, and open Microsoft PowerPoint 2019. Then, right-click on the desired slide and select 'Paste as Picture' from the contextual menu.

Link to Microsoft Word first. We have had reports from users that a viable workaround for this issue is to start by adding the graph as a linked or embedded object into Microsoft Word. Once added, copy and paste the linked object into Microsoft PowerPoint.

Switch to Microsoft Office 365 or the latest version of Microsoft Office. Newer versions of Office do not exhibit the described issue.

It is also possible that Microsoft will release a patch for Microsoft Office 2019 with a fix for this issue. In the event that we confirm that a future patch from Microsoft fixes this issue, we will update this FAQ accordingly.