Box Tools vs Box Edit


Box Tools is the installer package that installs both Box Edit and Device Trust functionality. The Device Trust component is only used if Device Trust is enabled for your Box account.

Deploying Box Tools on Windows

This information applies to physical Windows environments. For more information on using Box desktop applications in virtual environments, see Using Box in Virtual Environments.

Single-user vs machine-wide installations

We offer two variations of Box Tools: single-user and machine-wide. The functionality between the two variations is the same but they install the programs in different locations and support different configurations. 


The standard Box Tools .exe installer available from installs Box Tools under the user's profile and should only be used for single-user machines. The single-user .exe installer does not require administrative rights and is designed to be easily installed by end users.   
The single-user version installs into the following locations on the computer: 
  • C:\Users\USERNAME\AppData\Local\Box\Box Edit
  • C:\Users\USERNAME\AppData\Local\Box\Box Local Com Server

The single-user installation is not recommended for mass deployments of Box Tools. 

With the single-user installation, both Box Edit.exe and Box Local Com Service.exe should be running as the end user. 



The machine-wide .msi installer installs Box Tools as a machine-wide program and supports multi-user machines. Any user on the machine can use Box Tools functionality (Box Edit and Device Trust) if the .msi installer is used. The machine-wide installer requires administrator rights to install Box Tools. 


After installing with the machine-wide version, users will need to log out of Windows and log back in again before Box Edit will be enabled for those users.


The machine-wide installation location:

  • C:\Program Files (x86)\Box\Box Edit
  • C:\Program Files (x86)\Box\Box Local Com Server


The machine-wide installer is recommended for mass deployments of Box Tools.

With the machine-wide installation, Box Edit.exe should be running as the end user and Box Local Com Windows Service.exe should be running as the SYSTEM user as a Windows service. 


System Image Deployments

If you are using a system image to deploy Box Edit, verify that the Box Edit Documents folder on your source machine (C:\Users\USERNAME\AppData\Local\Box\Box Edit\Documents) is empty before capturing the image.

.NET Framework support

The default version installed by the installers linked above support older .NET Framework versions: 4.0, 4.5 and 4.5.1. After installing, Box Tools will automatically update to a newer version if the machine supports .NET Framework 4.5.2+. This newer version is also TLS 1.1+ compliant.
If you would like to directly install the version that supports .NET Framework 4.5.2+, you can use these installers:

We recommend installing the latest version of the .NET Framework that is supported in your environment. 


Deploying Box Edit on macOS


The Mac installer for Box Tools can be used with Mac deployment tools, such as Casper Suite. A Casper install of Edit requires the Box Local Com Server to be launched upon startup. See Deploying Box Edit with Casper for more info.
Prior to installing anything, the installer will do any necessary uninstalling, getting rid of any outdated plugins and .app files that might cause problems with Box Edit. The installer will then create the folder "~/Library/Application Support/Box/Box Edit/" and add the .app files "Box" and "Box Local Com Server.appto that directory.
After this, the installer will launch both .app files, making sure that they are both running before exiting the installation. The .app files will register themselves to start up at login time for the user that they're running for.

Note: If the .app files are not started for a user, the web app won't be able to verify that Box Edit is installed, and the user will be prompted to install Box Edit when they try to edit a file.


If you are using a deployment tool other than Casper Suite, or deploying Box Edit using a custom installer, be sure that the two .app files have been placed in the appropriate directory, and be sure to either start running them (as the user who will be logging in to that particular machine) or set them up to start running at login.


Box Tools DNS, Proxy, and Browser Configuration Guidelines


Box Tools uses a loopback network interface connection between the browser ( and the desktop. This interface may require you to configure your network to support Box Tools.

In addition to the information below, Internet Explorer may require additional configuration


Box Tools v4:

Box Tools v4 requires the ability for browsers ( to communicate with the Box Local Com Server by making requests to (or if port 17223 is occupied) over HTTP. The ability to communicate to over HTTP is acceptable by the following w3c standard.
Because Box Tools v4 uses the loopback address, no DNS configuration should be needed for Box Tools v4. 
If the proxy configuration is specified by a PAC file or a wpad.dat file (i.e., a PAC file published via DNS WPAD discovery), requests to and should be allowed to connect DIRECT.
An example PAC file code snippet: 
// If the protocol or URL matches, send direct.
if (shExpMatch(url, "") || shExpMatch(url, ""))
        return "DIRECT";

Note: "Direct" should be in all uppercase: DIRECT

Alternatively, you can configure your operating system to bypass proxies for requests:
On Windows: 
  1. Navigate to Control Panel > Internet Options > Connections > LAN Settings (or Settings for a selected Connection)
  2. Check the Bypass proxy server for local addresses box

bypass proxy.png

On Macs:
  1. Navigate to System Preferences > Network > select your connection > Advanced… > Proxies.
  2. Add to the box under Bypass proxy settings for these Hosts & Domains.
bypass proxy mac.png
 (screenshot from macOS 10.11.6) 


Box Tools v3: 


Box Tools v3 uses a special domain ( to create a loopback network interface connection  between the browser and the desktop. This interface may conflict with DNS, proxy, and other network access configurations. 
If you're having trouble with Box Tools v3, make sure your users' networks are configured to allow browsers to reach the domain, which resolves to 
Below are a list of requirements and suggested mechanisms for configuring your DNS and proxies.

Note: Internet Explorer may require additional configuration to allow Box Edit to work. Please see the Box Edit Internet Explorer Configuration Guide for more information. 


If the networking system filters or selectively caches DNS responses:

  • The domain * must be allowed to resolve to
  • If wildcards are not allowed, must be allowed to resolve to


If the proxy configuration is specified by a PAC file or a wpad.dat file (i.e., a PAC file published via DNS WPAD discovery), the domain * should be allowed to connect DIRECT.


An example PAC file code snippet: 


// If the protocol or URL matches, send direct.

if (url.substring(0, 6)=="https:" && shExpMatch(url, ""))

        return "DIRECT";


Note: "Direct" should be in all uppercase: DIRECT

If the proxy is not configured through a PAC/WPAD file, but through DIRECT configuration in the operating system:


On Windows: Add an exception for * 

  1. Navigate to Control Panel > Internet Options > Connections > LAN Settings (or Settings for a selected Connection)
  2. Add * to the box under Do not use proxy server for addresses beginning with


On Macs: Add an exception for * 
  1. Navigate to System Preferences > Network > select your connection > Advanced… > Proxies.
  2. Add * to the box under Bypass proxy settings for these Hosts & Domains.
(screenshot from OS X 10.10.3)