Downloads of v 2014.0526.1531:


Last Update:

10 Dec 2014

Package Maintainer(s):

Software Author(s):

  • Eva Peskova


pdf editor library pdf-utilities


2014.0526.1531 | Updated: 10 Dec 2014



Downloads of v 2014.0526.1531:



Software Author(s):

  • Eva Peskova

PDFedit 2014.0526.1531

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test

Validation Testing Unknown

Verification Testing Passed


To install PDFedit, run the following command from the command line or from PowerShell:


To upgrade PDFedit, run the following command from the command line or from PowerShell:


To uninstall PDFedit, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade pdfedit -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade pdfedit -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure pdfedit installed
    name: pdfedit
    state: present
    version: 2014.0526.1531
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'pdfedit' do
  action    :install
  version  '2014.0526.1531'
  source   'STEP 3 URL'

See docs at

    Name: pdfedit,
    Version: 2014.0526.1531,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pdfedit
   Name     = 'pdfedit'
   Ensure   = 'Present'
   Version  = '2014.0526.1531'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pdfedit':
  provider => 'chocolatey',
  ensure   => '2014.0526.1531',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pdfedit version="2014.0526.1531" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator purity on 10 Dec 2014.


PDFedit includes PDF manipulating library based on xpdf, GUI, set of command line tools and a pdf editor. You can use it to read, change and extract information from a PDF file. The graphical interface is based on QT.

try {
	$packageName = 'pdfedit'
	$installerType = 'msi'
	$partialInstallArgs = '/quiet /qn /norestart TARGETDIR='
	$is64bit = (Get-WmiObject Win32_Processor).AddressWidth -eq 64
	if ($is64bit) {$installPath = ${Env:ProgramFiles(x86)}} else {$installPath = $Env:ProgramFiles}
	$installArgs = $($partialInstallArgs + '"' + $installPath + '"')
	# due to limitations of Ketarin/chocopkgup when using repos like
	# 1. url is partly hardcoded and 2. DownloadUrlx64 is used to pass non-compatible nuget version number
	$url = ''
	$validExitCodes = @(0)
	Install-ChocolateyPackage "$packageName" "$installerType" "$installArgs" "$url" -validExitCodes "$validExitCodes"
  Write-ChocolateySuccess $packageName
} catch {
	Write-ChocolateyFailure $packageName $($_.Exception.Message)
try {
	$packageName = 'pdfedit'	
	$app = Get-WmiObject -class win32_product | Where-Object {$_.Name -like "$packageName"}
	if ($app) {
	  $msiArgs = $('/x' + $app.IdentifyingNumber + ' /quiet /qn /norestart')
	  Start-ChocolateyProcessAsAdmin $msiArgs 'msiexec'
	  Write-ChocolateySuccess $packageName
} catch {
	Write-ChocolateyFailure $packageName $($_.Exception.Message)

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the PDFedit Package

Ground Rules:

  • This discussion is only about PDFedit and the PDFedit package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or PDFedit, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus