conversion aborted v13.70- loss of key functionality

[Libby Skipworth]

This is also a problem for me, receiving conversion aborted error even when trying to print a test page from the printer in control panel.

1. I have updated Nitro Pro to the latest version (13.70),
2. uninstalled the latest windows update (in case that was the problem),
3. uninstalled HP "Smart" Print program, the only new software on computer (installed while I was traveling to access a printer at another site)
4. attempted to update the Nitro PDF Created (no errors, so assume was updated)

This error blocks key functionality for NitroPro - please provide solution as soon as possible.

Edited January 20, 2023 by Libby Skipworth

[Allain Umailin]

Hello @Libby Skipworth,

Thank you for reaching out to us through our Community Forums!

Let us try some troubleshooting by referring to these steps:

1. Download and run our Clean Up utility to uninstall your current Nitro Pro and reboot your machine:

https://downloads.gonitro.com/professional_13.70.2.40/install-cleanup/install-cleanup.zip

NOTE: This clean-up tool will erase any existing signature files within Nitro so please save them to another location before using the clean-up tool in order to keep them. Please see this link for backing up custom stamps/signatures: https://kb.gonitro.com/knowledgebase#/search/stamps/000004509

2. After rebooting, download and install the latest version of Visual Studio (vc_redist.x64.exe & vc_redist.x86.exe) then reboot again your machine. Visual Studio 2015, 2017, 2019, and 2022 all share the same redistributable files:
https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads

3. Clear all your Downloads folder or delete all downloaded Nitro installers. This step is important because we noticed that if you are saving all the installers and you download them in the same folder (like the downloads folder), the EXE can pick up any MSI installer in that folder and you may pick-up one of the older builds instead of the newly downloaded package.

4. Download and install Nitro PDF Pro 13.70 using these offline English MSI packages:

x64   https://downloads.gonitro.com/professional_13.70.2.40/en/retail/nitro_pro13_ba_x64.msi
x32   https://downloads.gonitro.com/professional_13.70.2.40/en/retail/nitro_pro13_ba_x86.msi

To know if you have 32-bit or 64-bit Windows system, please refer to this article:

https://support.microsoft.com/en-ph/help/15056/windows-32-64-bit-faq

Important: If you are using Chrome or any of the Chromium-based browsers (e.g., Vivaldi, etc.) and you are unable to access the above installer links, you're more than likely experiencing the results of a new security feature that was silently pushed out to the browsers, which blocks .exe/.msi/etc downloads without any visible error or prompt on the browser's frontend user space. In order to bypass this, please try these steps:

a. Right-click the link you're trying to download, and select "Save link as..."
b. Choose your save location and select "Save"
c. On the bottom edge of your browser window, the Downloads bar should now appear and the file will show up with a red error icon, attempting to block the download. Press the caret button and select "Keep"

5. After installation, you can activate it by opening Nitro PDF Pro, clicking on the Help tab > About Nitro Pro > Activate by entering your serial number 504919-xxyyzz-149004

6. Turning off User Account Control (UAC) for Nitro Pro. Here are two methods that you can follow:

a. Right-click the Nitro shortcut > Properties > Compatibility > Turn off any settings there.

b.
i. Right-click > Troubleshoot Compatibility > Troubleshoot Program
ii. Check "The program requires additional permissions" > Next > Test the program...
iii. Wait for the program to launch > Next > Yes, save these settings for this program > Close

 
Thank you very much in advance and I am looking forward to hearing back from you.

[Libby Skipworth]

Hi Allain,

the print function works again, after working through all the steps.

I did get an immediate crash on testing - a crash report was sent in. Will have to do a bit more to see if the crash is going to be an ongoing problem.

Thanks,

Libby