Downloads of v 2015.09.01:


Last Update:

22 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Stephen Griffin




This is not the latest version of MFCMapi available.

2015.09.01 | Updated: 22 Jan 2016



Downloads of v 2015.09.01:



Software Author(s):

  • Stephen Griffin



MFCMapi 2015.09.01

This is not the latest version of MFCMapi available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Validation Testing Passed

Verification Testing Failed


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


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


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

See docs at

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

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

See docs at

    Name: mfcmapi,
    Version: 2015.09.01,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller mfcmapi
   Name     = 'mfcmapi'
   Ensure   = 'Present'
   Version  = '2015.09.01'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install mfcmapi version="2015.09.01" 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 by moderator ferventcoder on 22 Jan 2016.


MFCMAPI provides access to MAPI stores to facilitate investigation of Exchange and Outlook issues and to provide developers with a sample for MAPI development.

This package downloads both the x86 and x64 binaries and puts them in %ChocolateyBinRoot%\MfcMapi.

try {
  $packageName = 'mfcmapi'
  $binRoot = Get-BinRoot
  Write-Debug "Bin Root is $binRoot"
  $installDir = Join-Path "$binRoot" "$packageName"

  # We're going to copy both the 32-bit and 64-bit executables, because
  # the bitness of Outlook won't necessarily match the bitness of the
  # OS.
  # These links map to September 2015 Release, build
  $x86Url = ''
  $x64Url = ''

  $x86InstallDir = Join-Path "$installDir" "x86"
  $x64InstallDir = Join-Path "$installDir" "x64"
  Install-ChocolateyZipPackage ($packageName + " 32 bit") $x86Url $x86InstallDir
  Install-ChocolateyZipPackage ($packageName + " 64 bit") $x64Url $x64InstallDir

  Write-ChocolateySuccess 'mfcmapi'
} catch {
  Write-ChocolateyFailure 'mfcmapi' $($_.Exception.Message)

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
MFCMapi 2019.2.19207.938 266 Saturday, July 27, 2019 Approved
MFCMapi 2019.0.19115.01 97 Saturday, June 22, 2019 Approved
MFCMapi 2015.09.01 1117 Friday, January 22, 2016 Approved
MFCMapi 2014.02.13 1108 Monday, February 24, 2014 Approved

This package has no dependencies.

Discussion for the MFCMapi Package

Ground Rules:

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