Downloads of v 12.0.1:


Last Update:

08 Oct 2021

Package Maintainer(s):

Software Author(s):

  • SweetScape Software Inc.


010editor admin editor hex file binary template script trial

010 Editor (Portable)

  • 1
  • 2
  • 3

12.0.1 | Updated: 08 Oct 2021



Downloads of v 12.0.1:


Software Author(s):

  • SweetScape Software Inc.

  • 1
  • 2
  • 3
010 Editor (Portable) 12.0.1

  • 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


Deployment Method: Individual Install, Upgrade, & Uninstall

To install 010 Editor (Portable), run the following command from the command line or from PowerShell:


To upgrade 010 Editor (Portable), run the following command from the command line or from PowerShell:


To uninstall 010 Editor (Portable), 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 010editor.portable -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 010editor.portable -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 010editor.portable
    name: 010editor.portable
    version: '12.0.1'
    state: present

See docs at

chocolatey_package '010editor.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '12.0.1'

See docs at

cChocoPackageInstaller 010editor.portable
    Name     = "010editor.portable"
    Version  = "12.0.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { '010editor.portable':
  ensure   => '12.0.1',
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 08 Oct 2021.



(30 day trial) Easily edit any text file, binary file, drive, or process on your computer.
Our unique Binary Templates technology allows you to view and edit complex binary data in an
easy, intuitive way. Includes a whole range of powerful analysis and editing tools.

Package-specific issue

If this package isn't up-to-date for some days, Create an issue

Support the package maintainer and Patreon

$ErrorActionPreference = 'Stop';

$url32            = ''
$url64            = ''
$checksum32       = '9b7e28164933a0651824f541378f1a81e44ac100c8afb967d623079c23055501'
$checksum64       = 'e4acec2bdc2c0b90037191b5cfa4c48282087f71241e945e62982176ad364840'
$checksumType32   = 'sha256'
$checksumType64   = 'sha256'
$installLocation = Join-Path "$env:ChocolateyInstall\lib" "010editor.portable\tools"

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

if((Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne $true) {
	$unzip_file = Split-Path $url64 -leaf
} else {
	$unzip_file = Split-Path $url32 -leaf

New-Item "$installLocation\010EditorPortable.exe.gui" -type file -force | Out-Null
New-Item "$installLocation\AppData\assistant.exe.ignore" -type file -force | Out-Null
New-Item "$installLocation\AppData\010Editor.exe.ignore" -type file -force | Out-Null

$full_dl_filename = (Join-Path "$cwd" "$unzip_file")

$packageArgs = @{
  packageName   = '010editor.portable'
  fileType      = 'EXE'
  softwareName  = '010 Editor*'
  FileFullPath  = $full_dl_filename

  checksum      = $checksum32
  checksumType  = $checksumType32
  url           = $url32

  checksum64    = $checksum64
  checksumType64= $checksumType64
  url64bit      = $url64

Get-ChocolateyWebFile @packageArgs

$extractPath = (Join-Path "$installLocation" "..\extract")
innounp -x -b -y -d"$extractPath" "$full_dl_filename"
robocopy (Join-Path "$extractPath" "{app}") "$installLocation" /e /mov /NFL /NDL /NJH /NJS /nc /ns /np
Remove-Item -Path $extractPath -Recurse -Force
Remove-Item -Path "$full_dl_filename" -Force
$ErrorActionPreference = 'Stop'

$installLocation = Join-Path "$env:ChocolateyInstall\lib" "010editor.portable\tools"

Write-Output "Removing 010editor.portable from '$installLocation'"
Remove-Item $installLocation -Recurse -Force -ea 0

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
010 Editor (Portable) 12.0 19 Saturday, September 18, 2021 Approved
010 Editor (Portable) 11.0.1 139 Tuesday, November 10, 2020 Approved
010 Editor (Portable) 11.0 111 Wednesday, September 30, 2020 Approved
010 Editor (Portable) 10.0.2 104 Friday, August 21, 2020 Approved
010 Editor (Portable) 1684 Tuesday, May 23, 2017 Approved



Discussion for the 010 Editor (Portable) Package

Ground Rules:

  • This discussion is only about 010 Editor (Portable) and the 010 Editor (Portable) 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 010 Editor (Portable), 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