Notices: This section not yet converted to new layout. Download stats are rolling back out.

Crealogix PayMaker Office

Package test results are passing.

This package was rejected on 2/13/2019. The reviewer chocolatey-ops has listed the following reason(s):

ITIGO (maintainer) on 07 Jan 2019 09:17:19 +00:00:

User 'ITIGO' (maintainer) submitted package.

chocolatey-ops (reviewer) on 07 Jan 2019 09:51:07 +00:00:

crealogix-paymaker-office has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.


Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 07 Jan 2019 10:51:20 +00:00:

crealogix-paymaker-office has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit for details.
This is an FYI only. There is no action you need to take.

Pauby (reviewer) on 09 Jan 2019 09:52:06 +00:00:

A few issues:

  1. Your <licenseUrl> does not point to a license.

  2. The <projectUrl> is invalid.

  3. The <packageSOurceUrl> does not point to the source for this package.

  4. In your chocolateyInstall.ps1 the $version variable splits the version at the '.' only to reassemble it again using '.' - is there a reason for this?

  5. In your chocolateyInstall.ps1 file (and chocolateyUninstall.ps1), lines 39 to 46, you have hardcoded the C:\ drive in there for your paths - what if the user doesn't have a C:\ drive? Can you use environment variables (such as $env:ProgramData)?

Is there are reason you have a dependency on both vcredist2008 and vcredist2013?

chocolatey-ops (reviewer) on 29 Jan 2019 09:54:36 +00:00:

We've found crealogix-paymaker-office v5.0.7.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:
* Log in to the site and respond to the review comments.
* Resubmit fixes for this version.
* If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 13 Feb 2019 09:56:58 +00:00:

Unfortunately there has not been progress to move crealogix-paymaker-office v5.0.7.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

The multi-banking software PayMaker Office offers you comprehensive features for your payment transactions, with an overview and transparency at all times and across different banks. You can make payments of all types and in a wide variety of formats quickly and reliably.

Package Parameters

  • /CleanStartmenu Removes frequently used Crealogix PayMaker Office shortcuts from the Startmenu.
  • /RemoveDesktopIcons Removes the desktop icon from Crealogix PayMaker Office.


  • tools\chocolateyInstall.ps1 Show
    # crealogix-paymaker-office install
    $ErrorActionPreference = 'Stop';
    $toolsDir            = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
    $PackageParameters   = Get-PackageParameters
    $urlZip              = ''
    $checksumZip         = '0069051d5ece9d4b6f22a6673684a4a5d130741765842d6791080a748a392b9a2afb07cba371eb3f2ce3acb445d856a5fc102dd811a1382199a7ca8e58069a34'
    $checksumTypeZip     = 'SHA512'
    $unzipLocation       = "$($env:TMP)\$($env:ChocolateyPackageName)\$($env:ChocolateyPackageVersion)"
    $version             = "$($env:ChocolateyPackageVersion.split(".")[0, 1, 2] -join '.')"
    Import-Module -Name "$($toolsDir)\helpers.ps1"
    $zipArgs = @{
        packageName    = $env:ChocolateyPackageName
        url            = $urlZip
        unzipLocation  = $unzipLocation
        checksum       = $checksumZip
        checksumType   = $checksumTypeZip
    $packageArgs = @{
        packageName    = $env:ChocolateyPackageName
        fileType       = 'MSI'
        file           = "$($unzipLocation)\PayMaker$($version).msi"
        silentArgs     = '/q'
        ValidExitCodes = @(0, 1000, 1101)
    Install-ChocolateyZipPackage @zipArgs
    Install-ChocolateyInstallPackage @packageArgs
    if ($PackageParameters.RemoveDesktopIcons) {
        Remove-DesktopIcons -Name "PayMaker" -Desktop "Public"
    if ($PackageParameters.CleanStartmenu) {
        Remove-FileItem `
            -Path "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PayMaker"
        Install-ChocolateyShortcut `
            -ShortcutFilePath "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PayMaker.lnk" `
            -TargetPath "C:\Program Files (x86)\CLX.PayMaker\PaymentStudio.exe" `
            -WorkDirectory "C:\Program Files (x86)\CLX.PayMaker\"
  • tools\chocolateyuninstall.ps1 Show
    # crealogix-paymaker-office uninstall
    $ErrorActionPreference = 'Stop';
    $toolsDir            = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
    Import-Module -Name "$($toolsDir)\helpers.ps1"
    Remove-FileItem `
        -Path "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PayMaker.lnk" 
  • tools\helpers.ps1 Show
    function Test-RegistryValue {
        param (
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Path,
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Value
        try {
            Get-ItemProperty -Path $Path | Select-Object -ExpandProperty $Value -ErrorAction Stop | Out-Null
            return $true
        catch {
            return $false
    function Remove-FileItem {
        param (
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Path
        try {
            Remove-Item `
                -Path $Path `
            Write-Output `
                -InputObject "Remove $($Path)"
        catch {
            Write-Output `
                -InputObject "Failed remove $($Path)"
    function Update-RegistryValue {
        param (
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Path,
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Name,
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Value,
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Type,
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Message
        try {
            Set-ItemProperty `
                -Path $Path `
                -Name $Name `
                -Value $Value
            Write-Output `
                -InputObject $Message
        catch {
            New-ItemProperty `
                -Path $Path `
                -Name $Name`
                -PropertyType $Type `
                -Value $Value
            Write-Output `
                -InputObject $Message
    function Remove-DesktopIcons {
        param (
            [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Name,
            [parameter(Mandatory = $false)]$Desktop
        if(!$Desktop)  {
           $Desktop = 'All' 
            if ($Desktop -eq 'All') {
                foreach ($User in Get-ChildItem -Path "C:\Users") {
                    Remove-FileItem -Path "C:\users\$($User)\desktop\$($Name).lnk"
                Remove-FileItem -Path "C:\Users\default\desktop\$($Name).lnk"
                Remove-FileItem -Path "C:\Users\Public\Desktop\$($Name).lnk"
            } elseif ($Desktop -eq 'Public') {
                Remove-FileItem -Path "C:\Users\Public\Desktop\$($Name).lnk"
            } elseif ($Desktop -eq 'Default') {
                Remove-FileItem -Path "C:\Users\Default\desktop\$($Name).lnk"

Virus Scan Results

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.


Package Maintainer(s)

Software Author(s)



Release Notes

Version History

Version Downloads Last updated Status
Crealogix PayMaker Office 58 Tuesday, October 23, 2018 approved
Crealogix PayMaker Office 54 Monday, September 10, 2018 approved
Crealogix PayMaker Office 49 Wednesday, September 5, 2018 approved

Discussion for the Crealogix PayMaker Office Package

Ground rules:

  • This discussion is only about Crealogix PayMaker Office and the Crealogix PayMaker Office 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 Crealogix PayMaker Office, 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 uses cookies to enhance the user experience of the site.