Downloads of v


Last Update:

16 Aug 2020

Package Maintainer(s):

Software Author(s):

  • Компания АТОЛ


admin atol driver drivers pos barcode pdt printers 1c 1c-enterprise

Atol DTO (Install)

  • 1
  • 2
  • 3 | Updated: 16 Aug 2020



Downloads of v



Software Author(s):

  • Компания АТОЛ

  • 1
  • 2
  • 3
Atol DTO (Install)

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Exemption for this package version only:

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall Atol DTO (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 atol-dto -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 atol-dto -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 atol-dto
    name: atol-dto
    version: ''
    state: present

See docs at

chocolatey_package 'atol-dto' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller atol-dto
    Name     = "atol-dto"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'atol-dto':
  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.

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

This package was approved as a trusted package on 16 Aug 2020.


Driver package intended to help with connecting Atol business automation hardware to PC: cash registers, input devices, checkue printers, weighing scales, portable data terminal and others. All drivers in package compatible with business platform 1C:Enterprise.

# According to
# [System.Environment]::OSVersion.Version
# - does not show [Windows 10 release](
# - does not differentiate between Windows 8.1 (6.3.9600) and Windows 8 (6.2.9200)
# - [deprecated](
# [Environment]::OSVersion is same as previous
# Get-WmiObject Win32_OperatingSystem
# - does not show [Windows 10 release](
# - [deprecated](
# Get-CimInstance Win32_OperatingSystem
# - does not show [Windows 10 release](
# Get-ComputerInfo is PowerShell 5+

function getFoldername{
    $windowsVersion = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"
	$bitness = Get-ProcessorBits
	if ($bitness -eq 32) {
		$bitness = 86
	if ($windowsVersion.CurrentMajorVersionNumber -ge 10) {
		return "W10_x$bitness"
	} else {
		return "W7W8_x$bitness"

$packageArgs = @{
  packageName            = "$env:chocolateyPackageName"
  url                    = ''
  checksum               = '478827a408e36419e1fd4513bc1ff45bc8037b78a51d65406a15c46b630bbea0'
  checksumType           = 'sha256'
  UnzipLocation          = "$env:TMP"
Install-ChocolateyZipPackage @packageArgs

$foldername = getFoldername

$packageArgs = @{
  FileFullPath           = "$env:TMP\\installer\exe\KKT10-"
  FileFullPath64         = "$env:TMP\\installer\exe\KKT10-"
  Destination            = "$env:TMP"
  SpecificFolder         = "USB_Drivers\$foldername"
Get-ChocolateyUnzip @packageArgs

(Get-AuthenticodeSignature "$env:TMP\USB_Drivers\$foldername\").SignerCertificate | Export-Certificate -FilePath "$env:TMP\atol-usbcom.cer"
Import-Certificate -FilePath "$env:TMP\atol-usbcom.cer" -CertStoreLocation Cert:\LocalMachine\TrustedPublisher

$packageArgs = @{
  packageName            = "$env:chocolateyPackageName"
  FileType               = 'exe'
  SilentArgs             = '/S'
  File                   = "$env:TMP\\installer\exe\KKT10-"
  File64                 = "$env:TMP\\installer\exe\KKT10-"
Install-ChocolateyInstallPackage @packageArgs

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
Atol DTO (Install) 153 Friday, May 8, 2020 Approved
Atol DTO (Install) 339 Thursday, February 28, 2019 Approved
Atol DTO (Install) 195 Wednesday, February 6, 2019 Approved
Atol DTO (Install) 10.4.2 216 Wednesday, November 21, 2018 Approved
Atol DTO (Install) 10.4.1 192 Thursday, September 20, 2018 Approved
Atol DTO (Install) 10.4.0 177 Friday, September 7, 2018 Approved
Atol DTO (Install) 10.3.1 194 Tuesday, August 21, 2018 Approved
Atol DTO (Install) 10.3.0 196 Wednesday, November 14, 2018 Approved
Atol DTO (Install) 10.2.0 158 Wednesday, November 14, 2018 Approved
Atol DTO (Install) 10.1.1 317 Monday, April 2, 2018 Approved
Atol DTO (Install) 10.1.0 164 Wednesday, November 14, 2018 Approved

This package has no dependencies.

Discussion for the Atol DTO (Install) Package

Ground Rules:

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