Downloads of v


Last Update:

13 Feb 2016

Package Maintainer(s):

Software Author(s):

  • See list of authors at


Blog WindowsLiveWriter OpenLiveWriter

OpenLiveWriter (Install)

  • 1
  • 2
  • 3 | Updated: 13 Feb 2016



Downloads of v



Software Author(s):

  • See list of authors at

  • 1
  • 2
  • 3
OpenLiveWriter (Install)

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install OpenLiveWriter (Install), run the following command from the command line or from PowerShell:


To upgrade OpenLiveWriter (Install), run the following command from the command line or from PowerShell:


To uninstall OpenLiveWriter (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade openlivewriter -y --source="'INTERNAL REPO 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 openlivewriter -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install openlivewriter
    name: openlivewriter
    version: ''
    state: present

See docs at

chocolatey_package 'openlivewriter' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller openlivewriter
    Name     = "openlivewriter"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'openlivewriter':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 17 Aug 2020.


Open Live Writer is an open source application enabling users to author, edit, and publish blog posts.
It is based on a fork of the well-loved but not actively developed Windows Live Writer code.

$packageName= 'openlivewriter'
$fileType = 'EXE'
$silentArgs = '--silent'
$scriptPath =  $(Split-Path $MyInvocation.MyCommand.Path)
$fileFullPath = Join-Path $scriptPath 'OpenLiveWriterSetup.exe'

Install-ChocolateyInstallPackage $packageName $fileType $silentArgs $fileFullPath

Write-Output "The install log is at `"$env:localappdata\SquirrelTemp\SquirrelSetup.log`""
$ErrorActionPreference = 'Stop';

$packageName = 'openlivewriter'
$softwareName = 'open live writer*'
$installerType = 'EXE'
$file = "$env:localappdata\OpenLiveWriter\Update.exe"

$silentArgs = '--uninstall -s'

if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if (!(Test-Path "$env:localappdata\openlivewriter\openlivewriter.exe"))
   If (!(Test-Path $file))
      throw "Could not find $file - because this software is always installed to a user profile folder, it must be uninstalled in the context of the user who installed it."
    Try {
      Uninstall-ChocolateyPackage -PackageName $packageName `
                                  -FileType $installerType `
                                  -SilentArgs "$silentArgs" `
                                  -ValidExitCodes $validExitCodes `
                                  -File "$file"

      #Remove leftovers so new install will succeed
      If (test-path "$env:localappdata\openlivewriter\.dead")
        remove-item "$env:localappdata\openlivewriter" -Recurse -Force -ErrorAction 'SilentlyContinue'
      If (test-path "C:\ProgramData\SquirrelMachineInstalls\OpenLiveWriter.exe")
        remove-item "C:\ProgramData\SquirrelMachineInstalls\OpenLiveWriter.exe" -Force -ErrorAction 'SilentlyContinue'
      Write-Output "The install log is at `"$env:localappdata\SquirrelTemp\SquirrelSetup.log`""
      throw $_.Exception
} else {
  Write-Warning "$packageName has already been uninstalled by other means or it is installed to a user's profile who is not the current user ($env:username)."
md5: 6AEE9DE163715375A743407E785EAA34 | sha1: 25C07923E5358664F249938E8C1703E42646C41D | sha256: A043CD29481044660503917110B0161D4DE3791487A5D31F4A74DF8DDF454ED7 | sha512: 090E01F333EE9E5156B2CDBAF40D6D81A2B166094040EB839357247320D36F8CCEA1FD83C2225A5C0BC00A2C93C7C0D0E84DD7638A41C02165D8F488EDFF2D6B

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.

Add to Builder Version Downloads Last Updated Status
OpenLiveWriter (Install) 467 Tuesday, December 29, 2015 Approved
OpenLiveWriter (Install) 365 Tuesday, December 29, 2015 Approved
OpenLiveWriter (Install) 459 Friday, December 18, 2015 Approved
OpenLiveWriter (Install) 361 Thursday, December 10, 2015 Approved

This package has no dependencies.

Discussion for the OpenLiveWriter (Install) Package

Ground Rules:

  • This discussion is only about OpenLiveWriter (Install) and the OpenLiveWriter (Install) 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 OpenLiveWriter (Install), 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