Downloads of v


Last Update:

20 Aug 2014

Package Maintainer(s):

Software Author(s):

  • Patch My PC


Admin Software Update Updates

Patch my PC

This is not the latest version of Patch my PC available.

  • 1
  • 2
  • 3 | Updated: 20 Aug 2014



Downloads of v



Software Author(s):

  • Patch My PC

  • 1
  • 2
  • 3
Patch my PC

This is not the latest version of Patch my PC available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Patch my PC, run the following command from the command line or from PowerShell:


To upgrade Patch my PC, run the following command from the command line or from PowerShell:


To uninstall Patch my PC, 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 patch-my-pc -y --source="'INTERNAL REPO URL'" --version="''" [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 patch-my-pc -y --source="'INTERNAL REPO URL'" --version="''" 

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

Exit $exitCode

- name: Install patch-my-pc
    name: patch-my-pc
    version: ''
    state: present

See docs at

chocolatey_package 'patch-my-pc' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller patch-my-pc
    Name     = "patch-my-pc"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'patch-my-pc':
  ensure   => '',
  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.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


Patch My PC helps to simplify the process of keeping your software up to date.

Link to start menu is no longer working. Looking for a package writer who can fix this.

$name = 'Patch my PC'
$id = 'patch-my-pc'
$url = ''
$pwd = "$(split-path -parent $MyInvocation.MyCommand.Definition)"

# Combatibility - This function has not been merged
if (!(Get-Command Install-ChocolateyPinnedItem -errorAction SilentlyContinue)) {
	Import-Module "$($pwd)\Install-ChocolateyPinnedItem.ps1"

try {

	$installDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $chocTempDir = Join-Path $env:TEMP "chocolatey"
    $tempDir = Join-Path $chocTempDir "$id"

	# Calculate $binRoot, which should always be set in $env:ChocolateyBinRoot as a full path (not relative)
	$binRoot = Get-BinRoot;

    #if (![System.IO.Directory]::Exists($tempDir)) { [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null }
    #$file = Join-Path $tempDir "$($id)Install.$fileType"
    $file = "$binRoot\PatchMyPC.exe"
    $tempFile = "$pwd\PatchMyPC.exe"

    Write-Host "Did someone change the binRoot?";
    Write-Host "Old: $binRoot";
    Write-Host "New: $nugetExePath";

    Get-ChocolateyWebFile $id "$tempFile" "$url"

	# Copy shortcut to start menu
#	Install-ChocolateyPinnedItem "$file"
#	Install-ChocolateyPinnedItem "$tempFile"

	$meh = Join-Path $nugetExePath "PatchMyPC.exe"
	Install-ChocolateyPinnedItem $meh

    Write-ChocolateySuccess $name
} catch {
	Write-ChocolateyFailure $name $($_.Exception.Message)
function Install-ChocolateyPinnedItem {

	# We need to know the translation for the Explorer context-menu item for pinning an item to the start-menu or taskbar.
	# Be careful. Commands vary from Windows version to version. E.g. Win7 -> Startmenu; Win8 -> Start;
	# We need loose matching. So we want to match the action (Pin) and the target (Start(menu) or Task(bar)) separately.
	# Translations
	# or even better, figure out a way to pin items to start without using this MONSTROUS trick.

	# Pin (to start)
	$verbPin = @{}
	$verbPin['da-DK'] = "Fastgør"
	$verbPin['en-US'] = "Pin" 
	$verbPin['fi-FI'] = "Kiinnitä"
	$verbPin['nb-NO'] = "Fest"
	$verbPin['nl-NL'] = "Vastmaken" 
	$verbPin['sv-SE'] = "Fäst"

	# (Pin to) Start
	$verbStart = @{}
	$verbStart['da-DK'] = "Start"
	$verbStart['en-US'] = "Start" 
	$verbStart['fi-FI'] = "Käynnistä"
	$verbStart['nb-NO'] = "Start"
	$verbStart['nl-NL'] = "Start" 
	$verbStart['sv-SE'] = "Start"
	# (Pin to) Taskbar
	$verbTask = @{}
	$verbTask['da-DK'] = "Proceslinje"
	$verbTask['en-US'] = "Task" 
	$verbTask['fi-FI'] = "Tehtävälkkiin"
	$verbTask['nb-NO'] = "Oppgavelinjen"
	$verbTask['nl-NL'] = "Taak" 
	$verbTask['sv-SE'] = "Aktivitetsfältet"

	# Get Locale
	$locale = (get-culture).Name
	# Not sure if get-culture < Windows 8, better not use
	# Usage
	if ($target -eq "") { 
		write-host "usage: Install-ChocolateyPinnedItem <file to pin> [-taskbar true]" 
		write-host "       -taskbar true (executable only) pins target to desktop TaskBar in stead of Start"
	else { 
		# Switch for Taskbar instead of Start
		if ($taskbar -ne "") {
			$verbAction = $verbTask
		} else {
			$verbAction = $verbStart

		# Path exists?
		if (-not (test-path "$target")) {
			write-host "No such file: '$target'";

		$pinned		= $false
		$path		= split-path "$target"
		$file		= split-path "$target" -leaf
		$explorer	= new-object -com "Shell.Application" 
		$folder		= $explorer.nameSpace($path)   
		$item		= $folder.parseName($file)
		$options	= $item.Verbs()	# > $null # This will still output irrelevant warnings for certain context menu items such as github. How to I hide these?

		foreach ($option in $options) {
			$oName = $option.Name.Replace("&","")
			# Be careful. Commands vary from Windows version to version. E.g. Win7 -> Startmenu; Win8 -> Start;
			# We need loose matching.
			# WARNING - This trick might also cause UNpinning if $file was already pinned!
			# First, match Pin
			foreach ($vPin in $verbPin.values) {
				if ($oName -imatch $vPin) {
					# Second, match action (either Start or Task(bar))
					foreach ($vAction in $verbAction.values) {
						if ($oName -imatch $vAction) {
							# write-host "Locale detected: $($vAction.key)" # Don't know key in values-foreach
							write-host "Command detected: $oName"
							write-host "Executing '$oName' for '$target'"
							$pinned = $true
					if ($pinned) { break }
		if ($pinned) { write-host "Succesfully Pinned '$file'" }
		else { write-host "Could not pin '$file'" }
C:\Windows\System32\msiexec.exe /x {F6881752-3DD7-44C9-9AC6-D827A1E641CC}

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
Patch my PC 3108 Thursday, August 12, 2021 Approved
Patch my PC 2039 Saturday, April 10, 2021 Approved
Patch my PC 727 Thursday, March 4, 2021 Approved
Patch my PC 5332 Tuesday, September 29, 2020 Approved
Patch my PC 1051 Thursday, May 28, 2020 Approved
Patch my PC 4545 Friday, February 14, 2020 Approved
Patch my PC 3322 Wednesday, July 10, 2019 Approved
Patch my PC 1253 Tuesday, January 1, 2019 Approved
Patch my PC 598 Friday, September 14, 2018 Approved

This package has no dependencies.

Discussion for the Patch my PC Package

Ground Rules:

  • This discussion is only about Patch my PC and the Patch my PC 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 Patch my PC, 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