Downloads of v 19.03.02:


Last Update:

20 Jul 2021

Package Maintainer(s):

Software Author(s):

  • Microsoft


Windows Security Baseline 1903


  • 1
  • 2
  • 3

19.03.02 | Updated: 20 Jul 2021



Downloads of v 19.03.02:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
WinSecurityBaseline 19.03.02

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Must be installed on Windows 10 or Windows Server 2016.


Scan Testing Successful:

No detections found in any package files


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


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


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

See docs at

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

See docs at

    Name: winsecuritybaseline,
    Version: 19.03.02,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winsecuritybaseline
   Name     = 'winsecuritybaseline'
   Ensure   = 'Present'
   Version  = '19.03.02'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winsecuritybaseline version="19.03.02" 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 approved by moderator flcdrg on 24 Jul 2021.


Windows security baselines

Applies to

  • Windows Server 2016+
  • Windows 10

Package Specific

Package Parameters

The following package parameters can be set:

  • /OSType:workstation\server - Default values is server

Package Uninstallation

  • Package LGPO settings cannot be uninsalled programticall once installed. This need to be done manually!

Using security baselines in your organization

Microsoft is dedicated to providing its customers with secure operating systems, such as Windows 10 and Windows Server, and secure apps, such as Microsoft Edge. In addition to the security assurance of its products, Microsoft also enables you to have fine control over your environments by providing various configuration capabilities.

Even though Windows and Windows Server are designed to be secure out-of-the-box, many organizations still want more granular control over their security configurations. To navigate the large number of controls, organizations need guidance on configuring various security features. Microsoft provides this guidance in the form of security baselines.

We recommend that you implement an industry-standard configuration that is broadly known and well-tested, such as Microsoft security baselines, as opposed to creating a baseline yourself. This helps increase flexibility and reduce costs.

Here is a good blog about Sticking with Well-Known and Proven Solutions.

What are security baselines?

Every organization faces security threats. However, the types of security threats that are of most concern to one organization can be completely different from another organization. For example, an e-commerce company may focus on protecting its Internet-facing web apps, while a hospital may focus on protecting confidential patient information. The one thing that all organizations have in common is a need to keep their apps and devices secure. These devices must be compliant with the security standards (or security baselines) defined by the organization.

A security baseline is a group of Microsoft-recommended configuration settings that explains their security impact. These settings are based on feedback from Microsoft security engineering teams, product groups, partners, and customers.

Why are security baselines needed?

Security baselines are an essential benefit to customers because they bring together expert knowledge from Microsoft, partners, and customers.

For example, there are over 3,000 Group Policy settings for Windows 10, which does not include over 1,800 Internet Explorer 11 settings. Of these 4,800 settings, only some are security-related. Although Microsoft provides extensive guidance on different security features, exploring each one can take a long time. You would have to determine the security impact of each setting on your own. Then, you would still need to determine the appropriate value for each setting.

In modern organizations, the security threat landscape is constantly evolving, and IT pros and policy-makers must keep up with security threats and make required changes to Windows security settings to help mitigate these threats. To enable faster deployments and make managing Windows easier, Microsoft provides customers with security baselines that are available in consumable formats, such as Group Policy Objects backups.

$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir  = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$arguments = Get-PackageParameters

$OSVersion = [System.Environment]::OSVersion.Version

if($OSVersion.Major -lt 10){
  throw "Windows build must be Windows10+ or Server2016+"

$SecBaseLineUrl = '' # download url, HTTPS preferred
$LGPOUrl        = ''

$SecBaseLinePackageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName"
  url           = $SecBaseLineUrl
  checksum      = 'F51FC91A6E5CEEE9D965F2D12319DEFA25073101421D212F95F40A402DDA7740'
  checksumType  = 'sha256'
  silentArgs    = ''

$LGPOPackageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName\Scripts\Tools"
  url           = $LGPOUrl
  checksum      = 'CB7159D134A0A1E7B1ED2ADA9A3CE8CE8F4DE391D14403D55438AF824247CC55'
  checksumType  = 'sha256'
  silentArgs    = ''

Install-ChocolateyZipPackage @SecBaseLinePackageArgs
Install-ChocolateyZipPackage @LGPOPackageArgs

#If unzip does not place LPGO.exe in tools directory then move it
if (!(Test-Path -Path "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName\Scripts\Tools\LGPO.exe")){
    $gci = Get-ChildItem -Path "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName\Scripts\Tools\" -Filter '*LGPO.exe' -Recurse
    if ($gci){
        Move-Item -Path $gci[0].FullName -Destination "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName\Scripts\Tools\$($"
        throw "Unable to find LGPO.exe"

#Run Microsoft PS1 installer
if ($arguments.ContainsKey("OSType")) {
  Write-Host "OSType Argument Found"
  $OSType = $arguments["OSType"]
  if ($OSType -notmatch "Server|Workstation"){
    Throw "Arguments must be either 'server' or 'workstation'"
  $OSType = 'Server'

$ScriptInstallerPath = "${env:ProgramFiles(x86)}\$env:ChocolateyPackageName\Scripts\Baseline-LocalInstall.ps1"

if ($OSType -eq 'Server'){
  & $ScriptInstallerPath -WSNonDomainJoined
elseif ($OSType -eq 'Workstation'){
  & $ScriptInstallerPath -Win10NonDomainJoined
else {
  Throw "Error selection powershell arguments"
$ErrorActionPreference = 'Stop'; # stop on all errors

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  ZipFileName   = 'Windows 10 Version 1903 and Windows Server Version 1903 Security Baseline -'

Uninstall-ChocolateyZipPackage @packageArgs

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
WinSecurityBaseline (Install) 19.03.01 1056 Friday, November 29, 2019 Approved

This package has no dependencies.

Discussion for the WinSecurityBaseline Package

Ground Rules:

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