Downloads of v 2018.12.16.0:


Last Update:

17 Dec 2018

Package Maintainer(s):

Software Author(s):

  • Antonio David Gellida Lavara


silent tweaks admin powershell cmd services appInstaller fixes


  • 1
  • 2
  • 3

2018.12.16.0 | Updated: 17 Dec 2018



Downloads of v 2018.12.16.0:



Software Author(s):

  • Antonio David Gellida Lavara

  • 1
  • 2
  • 3
winsys 2018.12.16.0

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall winsys, 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 winsys -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 winsys -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 winsys installed
    name: winsys
    state: present
    version: 2018.12.16.0
    source: STEP 3 URL

See docs at

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

See docs at

    Name: winsys,
    Version: 2018.12.16.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winsys
   Name     = 'winsys'
   Ensure   = 'Present'
   Version  = '2018.12.16.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winsys version="2018.12.16.0" source="STEP 3 URL"

See docs at

5. 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 30 Jan 2020.


Gives the user a powerful control center to toggle on and off many system settings in Windows 10, it is able to change system configurations, system updates, executable improvements, small system fixes, and more at the touch of a button.

# winsys install
$toolsDir            = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
$PackageParameters   = Get-PackageParameters
$urlPackage          = ''
$checksumPackage     = 'A3FE8049F316853E85DC84A572E0C08BA5CABC396A67E3B97A74F53871633B26E8CC42F9F6FCC26602AEA6585DE1131FF6F0DBBF4B098BD16BC8B2270AE7D4F3'
$checksumTypePackage = 'SHA512'
$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    fileType       = 'EXE'
    url            = $urlPackage
    checksum       = $checksumPackage
    checksumType   = $checksumTypePackage
	silentArgs     = '/VERYSILENT'
    validExitCodes = @(0, 1000, 1101)
Install-ChocolateyPackage @packageArgs
# winsys uninstall
$packageName = 'winsys'
$installerType = 'EXE'
$silentArgs = '/VERYSILENT'
$validExitCodes = @(0, 1000, 1101)

$processor = Get-WmiObject Win32_Processor
$is64bit = $processor.AddressWidth -eq 64
if ($is64bit) {
$unpath = "${Env:ProgramFiles(x86)}\winsys\unins000.exe"
} else {
$unpath = "$Env:ProgramFiles\winsys\unins000.exe"
Uninstall-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$unpath" -validExitCodes $validExitCodes

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
winsys 2018.12.08 175 Saturday, December 8, 2018 Approved
winsys 2018.10.29 228 Monday, October 29, 2018 Approved
winsys 2018.10.26 108 Saturday, October 27, 2018 Approved
winsys 2017.06.16 542 Friday, June 16, 2017 Approved

This package has no dependencies.

Discussion for the winsys Package

Ground Rules:

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