Downloads of v 1.2:


Last Update:

06 May 2019

Package Maintainer(s):

Software Author(s):

  • maharmstone



WinBtrfs (Install)

This is not the latest version of WinBtrfs (Install) available.

1.2 | Updated: 06 May 2019



Downloads of v 1.2:



Software Author(s):

  • maharmstone



WinBtrfs (Install) 1.2

This is not the latest version of WinBtrfs (Install) available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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


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


To uninstall WinBtrfs (Install), 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 winbtrfs -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 winbtrfs -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 winbtrfs installed
    name: winbtrfs
    state: present
    version: 1.2
    source: STEP 3 URL

See docs at

chocolatey_package 'winbtrfs' do
  action    :install
  version  '1.2'
  source   'STEP 3 URL'

See docs at

    Name: winbtrfs,
    Version: 1.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winbtrfs
   Name     = 'winbtrfs'
   Ensure   = 'Present'
   Version  = '1.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'winbtrfs':
  provider => 'chocolatey',
  ensure   => '1.2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winbtrfs version="1.2" 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 gep13 on 08 May 2019.


WinBtrfs is a Windows driver for the next-generation Linux filesystem Btrfs.
A reimplementation from scratch, it contains no code from the Linux kernel, and should work on any version from Windows 7 onwards. It is also included as part of the free operating system ReactOS.

First, a disclaimer:

This software is in active development - YOU USE IT AT YOUR OWN RISK. I take NO RESPONSIBILITY for any damage it may do to your filesystem.

In other words, assume that the driver is going to corrupt your entire filesystem, and you'll be pleasantly surprised when it doesn't.

However, having said that, it ought to be suitable for day-to-day use.

Everything here is released under the GNU Lesser General Public Licence (LGPL); see the file LICENCE for more info.
You are encouraged to play about with the source code as you will, and I'd appreciate a note ([email protected]) if you come up with anything nifty.
On top of that, I'm open to relicensing the code if you've a burning desire to use it on a GPL or commercial project, or what have you - drop me a line and we'll talk.

md5: 5A6BE9AC1529C88641950ACA7BA128D5 | sha1: E7C78FCCA0776977C1A2526C6CEF264D2E45284C | sha256: 7FAEFFAE4585B10A5DFFF7213391E9D4245ACEA58D5F5F8B2E390E62E054955B | sha512: D912CD479177B87BA4D16AF3F40A203710EFEE91BB962407D466A851C9FA02B1650F63360AB9C229F9199F44B43378A4983BF3EF5BFFEFDDF142BE00B41E9C18

$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileLocation = Join-Path $toolsDir ''
$driverFile = Join-Path $toolsDir ''
$outputFile = Join-Path $toolsDir 'MarkHarmstone.cer'
$exportType = [System.Security.Cryptography.X509Certificates.X509ContentType]::Cert

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName

Get-ChocolateyUnzip $fileLocation $toolsDir

Write-Host "Removing bundled debug files"
Remove-Item -Recurse -Path $toolsDir\Debug

Write-Host "Extracting cert from driver"
$cert = (Get-AuthenticodeSignature $driverFile).SignerCertificate;
[System.IO.File]::WriteAllBytes($outputFile, $cert.Export($exportType));

Write-Host "Adding cert to trusted store"
certutil -addstore -f "TrustedPublisher" $toolsDir\MarkHarmstone.cer

Write-Host "Adding btrfs driver"
pnputil -i -a $toolsDir\btrfs.inf 

if (Get-OSArchitectureWidth 64) {
	Write-Host "Removing x32 files"
	Remove-Item -Recurse -Path $toolsDir\x86
} else {
	Write-Host "Removing x64 files"
	Remove-Item -Recurse -Path $toolsDir\x64


$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

write-host	"Listing drivers"
$btrfsDrivers = Get-WmiObject win32_pnpsigneddriver | where {$_.DeviceName -like "*btrfs*" -and $_.InfName -like

foreach($InfName in $btrfsDrivers)
	Write-Host "Removing btrfs driver" $btrfsDrivers.InfName
	pnputil -f -d $btrfsDrivers.InfName



                       Version 3, 29 June 2007

 Copyright (C) 2007 Free Software Foundation, Inc. <>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

  This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.

  0. Additional Definitions.

  As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.

  "The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.

  An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.

  A "Combined Work" is a work produced by combining or linking an
Application with the Library.  The particular version of the Library
with which the Combined Work was made is also called the "Linked

  The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.

  The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.

  1. Exception to Section 3 of the GNU GPL.

  You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.

  2. Conveying Modified Versions.

  If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified

   a) under this License, provided that you make a good faith effort to
   ensure that, in the event an Application does not supply the
   function or data, the facility still operates, and performs
   whatever part of its purpose remains meaningful, or

   b) under the GNU GPL, with none of the additional permissions of
   this License applicable to that copy.

  3. Object Code Incorporating Material from Library Header Files.

  The object code form of an Application may incorporate material from
a header file that is part of the Library.  You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:

   a) Give prominent notice with each copy of the object code that the
   Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the object code with a copy of the GNU GPL and this license

  4. Combined Works.

  You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:

   a) Give prominent notice with each copy of the Combined Work that
   the Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the Combined Work with a copy of the GNU GPL and this license

   c) For a Combined Work that displays copyright notices during
   execution, include the copyright notice for the Library among
   these notices, as well as a reference directing the user to the
   copies of the GNU GPL and this license document.

   d) Do one of the following:

       0) Convey the Minimal Corresponding Source under the terms of this
       License, and the Corresponding Application Code in a form
       suitable for, and under terms that permit, the user to
       recombine or relink the Application with a modified version of
       the Linked Version to produce a modified Combined Work, in the
       manner specified by section 6 of the GNU GPL for conveying
       Corresponding Source.

       1) Use a suitable shared library mechanism for linking with the
       Library.  A suitable mechanism is one that (a) uses at run time
       a copy of the Library already present on the user's computer
       system, and (b) will operate properly with a modified version
       of the Library that is interface-compatible with the Linked

   e) Provide Installation Information, but only if you would otherwise
   be required to provide such information under section 6 of the
   GNU GPL, and only to the extent that such information is
   necessary to install and execute a modified version of the
   Combined Work produced by recombining or relinking the
   Application with a modified version of the Linked Version. (If
   you use option 4d0, the Installation Information must accompany
   the Minimal Corresponding Source and Corresponding Application
   Code. If you use option 4d1, you must provide the Installation
   Information in the manner specified by section 6 of the GNU GPL
   for conveying Corresponding Source.)

  5. Combined Libraries.

  You may place library facilities that are a work based on the
Library side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:

   a) Accompany the combined library with a copy of the same work based
   on the Library, uncombined with any other library facilities,
   conveyed under the terms of this License.

   b) Give prominent notice with the combined library that part of it
   is a work based on the Library, and explaining where to find the
   accompanying uncombined form of the same work.

  6. Revised Versions of the GNU Lesser General Public License.

  The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.

  Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version
of the GNU Lesser General Public License "or any later version"
applies to it, you have the option of following the terms and
conditions either of that published version or of any later version
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.

  If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
1. Download

2. Use checksum utility of preference to get checksum of zip

3. Check that it matches below
	MD5: 5a6be9ac1529c88641950aca7ba128d5
	SHA-1: e7c78fcca0776977c1a2526c6cef264d2e45284c
	SHA-256: 7faeffae4585b10a5dfff7213391e9d4245acea58d5f5f8b2e390e62e054955b
	SHA-512: d912cd479177b87ba4d16af3f40a203710efee91bb962407d466a851c9fa02b1650f63360ab9c229f9199f44b43378a4983bf3ef5bffefddf142be00b41e9c18

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
WinBtrfs 1.7.6 845 Thursday, January 14, 2021 Approved
WinBtrfs 1.7.5 950 Saturday, October 31, 2020 Approved
WinBtrfs 1.7.4 730 Sunday, August 23, 2020 Approved
WinBtrfs 1.7.3 701 Monday, May 25, 2020 Approved
WinBtrfs 1.7.2 440 Friday, April 10, 2020 Approved
WinBtrfs 1.7.1 390 Monday, March 2, 2020 Approved
WinBtrfs 1.7 133 Wednesday, February 26, 2020 Approved
WinBtrfs 1.6 251 Tuesday, February 4, 2020 Approved
WinBtrfs 1.5 410 Sunday, November 10, 2019 Approved

v1.2 (2019-05-05):

Dramatic speed increase when opening many small files, such as with a Git repository
Fixed crash on surprise removals of removable devices
Added ability to change drive letters easily
No longer creates free-space cache for very small chunks, so as not to confuse the Linux driver
Fixed corruption when very large file created and then immediately deleted
Minor bug fixes

v1.1 (2018-12-15):
Support for Zstd compression
Passthrough of Linux metadata to LXSS
Refactored shell extension
Fixed memory leaks
Many other bug fixes

v1.0.2 (2018-05-19):
Minor bug fixes

v1.0.1 (2017-10-15):
Fixed deadlock
Binaries now signed
Minor bug fixes

v1.0 (2017-09-04):
First non-beta release!
Degraded mounts
New free space cache (compat_ro flag free_space_cache)
Shrinking and expanding of volumes
Registry options now re-read when changed, rather than just on startup
Improved balancing on very full filesystems
Fixed problem preventing user profile directory being stored on btrfs on Windows 8 and above
Better Plug and Play support
Miscellaneous bug fixes

v0.10 (2017-05-02):
Reflink copy
Sending and receiving subvolumes
Group mappings (see Mappings section above)
Added commands for scripting etc. (see Commands section above)
Fixed an issue preventing mounting on non-PNP devices, such as VeraCrypt
Fixed an issue preventing new versions of LXSS from working
Fixed problem with the ordering of extent refs, which caused problems on Linux but wasn't picked up by btrfs check
Added support for reading compressed inline extents
Many miscellaneous bug fixes

v0.9 (2017-03-05):
Better handling of multi-device volumes
Performance increases when reading from RAID filesystems
No longer lies about being NTFS, except when it has to
Volumes will now go readonly if there is an unrecoverable error, rather than blue-screening
Filesystems can now be created with Windows' inbuilt
Zlib upgraded to version 1.2.11
Miscellaneous performance increases
Miscellaneous bug fixes

v0.8 (2016-12-30):
Volume property sheet, for:
Adding and removing devices
Showing disk usage, i.e. the equivalent to btrfs fi usage
Checksums now calculated in parallel where appropriate
Creation of new filesystems, with mkbtrfs.exe
Plug and play support for RAID devices
Disk usage now correctly allocated to processes in taskmgr
Performance increases
Miscellaneous bug fixes

v0.7 (2016-10-24):
Support for RAID5/6 (incompat flag raid56)
Seeding support
LXSS ("Ubuntu on Windows") support
Support for Windows Extended Attributes
Improved removable device support
Better snapshot support
Recovery from RAID checksum errors
Fixed issue where creating a lot of new files was taking a long time
Miscellaneous speed increases and bug fixes

v0.6 (2016-08-21):
Compression support (both zlib and lzo)
Mixed groups support
No-holes support
Added inode property sheet to shell extension
Many more mount options (see below)
Better support for removable devices
Page file support
Many miscellaneous bug fixes

v0.5 (2016-07-24):
Massive speed increases (from "sluggish" to "blistering")
Massive stability improvements
RAID support: RAID0, RAID1, and RAID10
Asynchronous reading and writing
Partition-less Btrfs volumes
Windows sparse file support
Object ID support
Beginnings of per-volume mount options
Security improvements
Notification improvements
Miscellaneous bug fixes

v0.4 (2016-05-02):
Subvolume creation and deletion
Reparse points
Hard links
Plug and play
Free-space cache
Fix problems preventing volume from being shared over the network
Miscellaneous bug fixes

v0.3 (2016-03-25):
Bug fixes:
Fixed crashes when metadata blocks were SINGLE, such as on SSDs
Fixed crash when splitting an internal tree
Fixed tree traversal failing when first item in tree had been deleted
Fixed emptying out of whole tree (probably only relevant to checksum tree)
Fixed "incorrect local backref count" message appearing in btrfs check
Miscellaneous other fixes
Added beginnings of shell extension, which currently only changes the icon of subvolumes

v0.2 (2016-03-13):
Bug fix release:
Check memory allocations succeed
Check tree items are the size we're expecting
Added rollbacks, so failed operations are completely undone
Fixed driver claiming all unrecognized partitions (thanks Pierre Schweitzer)
Fixed deadlock within CcCopyRead
Fixed changing properties of a JPEG within Explorer
Lie about FS type, so UAC works
Many, many miscellaneous bug fixes
Rudimentary security support
Debug log support (see below)

v0.1 (2016-02-21):
Initial alpha release.

This package has no dependencies.

Discussion for the WinBtrfs (Install) Package

Ground Rules:

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