We help IT Professionals succeed at work.

Paperport Application Crash ''PPDesktopView'

Low Priority
443 Views
Last Modified: 2018-07-28
Comment
Watch Question

Developer
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2018
Commented:
Hi Germel,
the problem 'PPDesktopView'
Please provide more details on the problem...screenshots would be helpful, too. I can't tell what the problem is with just the word "PPDesktopView". That said, the word "Crash" in your title leads me to suggest watching this 5-minute EE video Micro Tutorial:
What to do when PaperPort crashes, hangs, or fails to start

In addition, if you're not using version 14.5 with Patch 1 and the PP14 Scanner Connection Tool, I strongly recommend all three, as discussed in these EE articles:
PaperPort 14 - Free Upgrade to Version 14.5
How to install the Patch 1 update for PaperPort 14.5
PaperPort 14 Scanner Connection Tool - Fix Scanning Problems in PaperPort 14

Also, since you're on W10, I recommend reading this article:
PaperPort 14 in Windows 10 - A First Look

Some of the Tips in there may be helpful. Regards, Joe
Joe WinogradDeveloper
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2018

Commented:
The author never came back with additional details on the problem, but the suggestions in the selected post have solved crashes for many PaperPort users and is worth having in the PAQ.
OK everyone. Do be advised that PP 14.5 will cease to work on all RS5 Windows 10 Builds after 17704. Mine worked fine on build 17692, but refused to open starting with the next build. The issue still ongoing. I am now testing the new 19H1 (RS6) branch, and so far, it is still broken. The splash screen will appear and disappear. Nothing more. I have tried compatibility settings to no avail.
Joe WinogradDeveloper
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2018

Commented:
Hi GW,
The answer to your problem is almost certainly in this EE article:

What to do when PaperPort crashes, hangs, or fails to start - popular fix for Mozilla Firefox users

It has hit thousands of PaperPort users this month, and it is not specific to W10 or any particular build of W10. In fact, the bug is 100% reproducible in W7. The fix in the article works on all platforms. Regards, Joe