Downloads of v


Last Update:


Package Maintainer(s):

Software Author(s):

  • Jivko Kolev


jivkok utilities tools


This is not the latest version of Jivkok.Tools available. | Updated: 12/31/2013



Downloads of v



Software Author(s):

  • Jivko Kolev


This is not the latest version of Jivkok.Tools available.

All Checks are Unknown

2 Test of Unknown Status

Validation Testing Unknown

Verification Testing Unknown

To install Jivkok.Tools, run the following command from the command line or from PowerShell:


To upgrade Jivkok.Tools, run the following command from the command line or from PowerShell:


To uninstall Jivkok.Tools, 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 -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 -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 installed
    state: present
    source: STEP 3 URL

See docs at

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

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

See docs at

    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

   Name     = ''
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install version="" 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 submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


This set includes a number of utilities installed as part of configuring new Windows machine:
7zip.install, 7zip.commandline, AutoHotKey_L, Calibre, CCleaner, CloseTheDoor, Console2, CrystalDiskInfo, Defraggler, Dexpot, Filezilla, Firefox, FoxitReader, FreeCommander, Git.Install, GoogleChrome, HTTrack, Inssider, Intel.SSD.Toolbox, KeePass, MicrosoftSecurityEssentials, MobaXTerm, Monosnap, NetScan64, NimbleText, nmap, NugetPackageExplorer, PDFCreator, PomoTime, Powershell, Putty, ResophNotes, RMPrepUSB, RoyalTS, Secunia.PSI, Shotcut, Shotty, SkyDrive, Skype, Speccy, SyncBack, Synergy, SwissFileKnife, TeamViewer, TeraCopy,, thebrain.install, Tunnelier, VirtualCloneDrive, VLC, WinDirStat, WinSCP, XMind.

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
Jivkok.Tools 432 Tuesday, December 31, 2013 Unknown
Jivkok.Tools 306 Monday, December 23, 2013 Unknown
Jivkok.Tools 311 Monday, November 25, 2013 Unknown
Jivkok.Tools 309 Monday, November 18, 2013 Unknown
Jivkok.Tools 339 Saturday, June 29, 2013 Unknown
Jivkok.Tools 315 Sunday, May 5, 2013 Unknown
Jivkok.Tools 385 Thursday, December 13, 2012 Unknown
Discussion for the Jivkok.Tools Package

Ground Rules:

  • This discussion is only about Jivkok.Tools and the Jivkok.Tools 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 Jivkok.Tools, 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