Downloads of v 4.1.7:


Last Update:

27 Feb 2020

Package Maintainer(s):

Software Author(s):

  • Webprofusion Pty Ltd


certifytheweb certify letsencrypt ssl iis win https certificate acme windows simple

Certify The Web (Install)

This is not the latest version of Certify The Web (Install) available.

  • 1
  • 2
  • 3

4.1.7 | Updated: 27 Feb 2020



Downloads of v 4.1.7:



Software Author(s):

  • Webprofusion Pty Ltd

  • 1
  • 2
  • 3
Certify The Web (Install) 4.1.7

This is not the latest version of Certify The Web (Install) available.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Requesting verifier exception due to reboot required by .net 4.6.2 dependency.


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Certify The Web (Install), run the following command from the command line or from PowerShell:


To upgrade Certify The Web (Install), run the following command from the command line or from PowerShell:


To uninstall Certify The Web (Install), run the following command from the command line or from PowerShell:


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade certifytheweb -y --source="'INTERNAL REPO URL'" --version="'4.1.7'" [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 certifytheweb -y --source="'INTERNAL REPO URL'" --version="'4.1.7'" 

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

Exit $exitCode

- name: Install certifytheweb
    name: certifytheweb
    version: '4.1.7'
    state: present

See docs at

chocolatey_package 'certifytheweb' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.1.7'

See docs at

cChocoPackageInstaller certifytheweb
    Name     = "certifytheweb"
    Version  = "4.1.7"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'certifytheweb':
  ensure   => '4.1.7',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 27 Feb 2020.


The GUI to easily request, install, managed and auto-renew free SSL/TLS certificates from ACME CAs such as for your IIS/Windows servers. Setting up https has never been easier.

# This runs in 0.9.10+ before upgrade and uninstall.
# Use this file to do things like stop services prior to upgrade or uninstall.
# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you
#  need to uninstall an MSI prior to upgrade, put the functionality in this
#  file without calling the uninstall script. Make it idempotent in the
#  uninstall script so that it doesn't fail when it is already uninstalled.
# NOTE: For upgrades - like the uninstall script, this script always runs from 
#  the currently installed version, not from the new upgraded package version.

# Close the UI window if currently open
Get-Process | Where-Object {$_.ProcessName -eq 'Certify.UI'} | Foreach-Object { $_.CloseMainWindow() | Out-Null } | stop-process –force

# Stop the Certify.Service background service
Get-Service Certify.Service | Where {$_.status –eq 'Running'} |  Stop-Service
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url64      = ''

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'exe'
  url64bit      = $url64
  softwareName  = 'Certify The Web*'
  checksum64    = '930a00ab8ac75827434f36ce76f81a295e2311e1bf6b5c8808a35b6911549971'
  checksumType64= 'sha256'
  validExitCodes= @(0)

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Certify The Web*'
  fileType      = 'EXE'
  validExitCodes= @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

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.

Add to Builder Version Downloads Last Updated Status
Certify The Web (Install) 5.6.7 269 Monday, March 28, 2022 Approved
Certify The Web (Install) 5.6.6 274 Thursday, March 17, 2022 Approved
Certify The Web (Install) 5.6.5 721 Wednesday, February 2, 2022 Approved
Certify The Web (Install) 5.6.4 460 Tuesday, January 11, 2022 Approved
Certify The Web (Install) 5.6.3 231 Friday, January 7, 2022 Approved
Certify The Web (Install) 5.6.2 789 Monday, December 20, 2021 Approved
Certify The Web (Install) 5.6.1 201 Friday, December 17, 2021 Approved
Certify The Web (Install) 5.5.7 782 Wednesday, October 27, 2021 Approved
Certify The Web (Install) 5.5.6 234 Thursday, October 21, 2021 Approved
Discussion for the Certify The Web (Install) Package

Ground Rules:

  • This discussion is only about Certify The Web (Install) and the Certify The Web (Install) 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 Certify The Web (Install), 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