Downloads:

7,003

Downloads of v 1.0.0.20150904:

5,356

Last Update:

9/5/2015

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

microsoft file checksum md5 sha1 KB841290

File Checksum Integrity Verifier

1.0.0.20150904 | Updated: 9/5/2015

Downloads:

7,003

Downloads of v 1.0.0.20150904:

5,356

Software Author(s):

  • Microsoft

File Checksum Integrity Verifier 1.0.0.20150904

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

To install File Checksum Integrity Verifier, run the following command from the command line or from PowerShell:

>

To upgrade File Checksum Integrity Verifier, run the following command from the command line or from PowerShell:

>

To uninstall File Checksum Integrity Verifier, 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade fciv -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 fciv -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure fciv installed
  win_chocolatey:
    name: fciv
    state: present
    version: 1.0.0.20150904
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


chocolatey_package 'fciv' do
  action    :install
  version  '1.0.0.20150904'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: fciv,
    Version: 1.0.0.20150904,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller fciv
{
   Name     = 'fciv'
   Ensure   = 'Present'
   Version  = '1.0.0.20150904'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


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

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install fciv version="1.0.0.20150904" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 by moderator ferventcoder on 12/28/2015.

Description

The File Checksum Integrity Verifier tool is an command line utility that computes MD5 or SHA1 cryptographic hashes for files


tools\chocolateyInstall.ps1
# Download and extract fciv to package path. Chocolatey will automatically create a stub exe in a directory in PATH.
$arguments = @{
    packageName = 'fciv'
    url = 'http://download.microsoft.com/download/c/f/4/cf454ae0-a4bb-4123-8333-a1b6737712f7/Windows-KB841290-x86-ENU.exe'
    checksumType = 'sha1'
    checksum = '99FB35D97A5EE0DF703F0CDD02F2D787D6741F65'
    installerType = 'exe'
    silentArgs = """/T:${Env:chocolateyPackageFolder}"" /Q"
    validExitCodes = @(0)
}
Install-ChocolateyPackage @arguments

# Cleanup after previous package version, which extracted to $Env:SystemDrive\tools\fciv
# This should not influence the installation of this version, so catch and ignore all errors.
try {
  if (Test-Path (Join-Path (Split-Path $env:chocolateyPackageFolder) 'fciv.1.0.0.0')) {
    $fcivPath = Join-Path $Env:SystemDrive 'tools\fciv'
    if (Test-Path $fcivPath) {
      Write-Debug "Removing previous installation location $fcivPath"
      Remove-Item $fcivPath -Recurse -ErrorAction Continue
    }

    $userPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
    if ($userPath -ne $null -and $userPath -like "*$fcivPath*") {
      Write-Debug "Removing previous installation location $fcivPath from the user PATH variable"
      $newUserPathChunks = $userPath -split ';' | Where-Object { $_ -ne '' -and $_.TrimEnd('\') -ne $fcivPath }
      $newUserPath = $newUserPathChunks -join ';'
      if ($newUserPath -ne $userPath) {
        [Environment]::SetEnvironmentVariable('PATH', $newUserPath, 'User')
      }
    }

    $currentPath = $Env:PATH
    if ($currentPath -ne $null -and $currentPath -like "*$fcivPath*") {
      Write-Debug "Removing previous installation location $fcivPath from the current Powershell PATH variable"
      $newCurrentPathChunks = $currentPath -split ';' | Where-Object { $_ -ne '' -and $_.TrimEnd('\') -ne $fcivPath }
      $newCurrentPath = $newCurrentPathChunks -join ';'
      if ($newCurrentPath -ne $currentPath) {
        $Env:PATH = $newCurrentPath
      }
    }
  }
} catch {
  Write-Warning "Failed to clean up after previous fciv package version: $($_.Exception.Message)"
}

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
File Checksum Integrity Verifier 1.0.0.20140521 1194 Wednesday, May 21, 2014 Unknown
File Checksum Integrity Verifier 1.0.0.0 453 Thursday, April 11, 2013 Unknown

1.0.0.20150904:
Added checksum.


This package has no dependencies.

Discussion for the File Checksum Integrity Verifier Package

Ground Rules:

  • This discussion is only about File Checksum Integrity Verifier and the File Checksum Integrity Verifier 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 File Checksum Integrity Verifier, 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