Downloads of v 1.00-beta2:


Last Update:

10 Oct 2019

Package Maintainer(s):

Software Author(s):

  • Registry File (.REG) Validator Team.


registryfiles-validator parsing reg regedit file check

Registry File (.REG) Validator

This is a prerelease version of Registry File (.REG) Validator.

1.00-beta2 | Updated: 10 Oct 2019



Downloads of v 1.00-beta2:



Software Author(s):

  • Registry File (.REG) Validator Team.

Registry File (.REG) Validator 1.00-beta2

This is a prerelease version of Registry File (.REG) Validator.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Registry File (.REG) Validator, run the following command from the command line or from PowerShell:


To upgrade Registry File (.REG) Validator, run the following command from the command line or from PowerShell:


To uninstall Registry File (.REG) Validator, 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 registryfiles-validator -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 registryfiles-validator -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 registryfiles-validator installed
    name: registryfiles-validator
    state: present
    version: 1.00-beta2
    source: STEP 3 URL

See docs at

chocolatey_package 'registryfiles-validator' do
  action    :install
  version  '1.00-beta2'
  source   'STEP 3 URL'

See docs at

    Name: registryfiles-validator,
    Version: 1.00-beta2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller registryfiles-validator
   Name     = 'registryfiles-validator'
   Ensure   = 'Present'
   Version  = '1.00-beta2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'registryfiles-validator':
  provider => 'chocolatey',
  ensure   => '1.00-beta2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install registryfiles-validator version="1.00-beta2" 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 is exempt from moderation. While it is likely safe for you, there is more risk involved.

This tool parses a .REG file to find all the invalid entries.

How to use

Drag&drop the .REG file on the tool and a list of the wrong entries will be immediately shown.

$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "$toolsDir"

  url           = Get-RedirectedURL ''
  checksum      = '5AD7934660E589CD6739204FB461AFCA35496D87ED05D594648EF9540D0AB139'
  checksumType  = 'sha256'  

Install-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
Registry File (.REG) Validator 1.00-beta2 67 Thursday, October 10, 2019 Exempted

  • 1.00beta2: fixed issues with dwords with wrong value length and added support for REG_NONE hexadecimal strings and added a command-line version.
  • 1.00beta1: initial release.
Discussion for the Registry File (.REG) Validator Package

Ground Rules:

  • This discussion is only about Registry File (.REG) Validator and the Registry File (.REG) Validator 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 Registry File (.REG) Validator, 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