How to Silently Install EditPlus

Silent install · · 5 min read

Get a reliable rollout and predictable detection for EditPlus with a deployment approach built for IT admins. This guide focuses on packaging and deploying the ES-Computing editor as a machine-wide install that requires admin rights, using the verified silent install command and a dependable detection rule. Whether you are standardizing deployment through Intune, SCCM, or PDQ, the steps here help reduce manual effort, improve consistency, and support clean, repeatable software distribution across managed Windows devices.

STEP 0

Quick snapshot: Silently install EditPlus on Windows

Run in an elevated PowerShell session:

powershell
ES-Computing.EditPlus.6.1.780.0.X64.exe -s -sp-s

Overview

ApplicationEditPlus
Version6.1.780.0
PublisherES-Computing
Installer typeUnknown
Install scopeSystem / machine-wide
Requires adminYes
Silent installAvailable
Silent uninstallAvailable
Detection methodRegistry
Installer fileES-Computing.EditPlus.6.1.780.0.X64.exe
DownloadEditPlus installer

Silent install steps

EditPlus installs through a PowerShell command, so run it in an elevated PowerShell session. Command Prompt cannot run this cmdlet.

Install with PowerShell

  1. Download or stage the installer (ES-Computing.EditPlus.6.1.780.0.X64.exe) to a local folder, for example C:\Installers.
Installers
This PCLocal Disk (C:)InstallersSearch Installers
ES-Computing.EditPlus.6.1.780.0.X64.exe6/17/2026 9:14 AMApplication
1 item1 item selected
  1. Open PowerShell as Administrator — right-click Start (or press Win+X), then:
    • On Windows 10: choose Windows PowerShell (Admin).
    • On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
Right-click the Start button — or press ⊞ Win + X
Apps and Features
Power Options
Device Manager
Disk Management
Terminal
Terminal (Admin)
Task Manager
Settings
  1. Run the silent install command:
powershell
ES-Computing.EditPlus.6.1.780.0.X64.exe -s -sp-s

Deployment Notes

Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.

RequirementAdministrator privileges required
Install scopeMachine
Restart behaviorNo restart expected

Detection Rules

Configure your deployment tool with the detection rule below to confirm a successful install of EditPlus. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.

Registry detection

Key pathHKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\EditPlus
Value nameDisplayVersion
Expected version6.1.780.0

PowerShell detection script

Prefer a script-based check? Use this as a custom detection script in Microsoft Intune (or any tool that supports detection scripts). It exits 0 when EditPlus is detected and 1 otherwise.

powershell
$Key = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\EditPlus'
$Value = (Get-ItemProperty -Path $Key -Name 'DisplayVersion' -ErrorAction SilentlyContinue).'DisplayVersion'
if ($Value -eq '6.1.780.0') { exit 0 }
exit 1

Silent Uninstall Steps

Remove EditPlus silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.

Method 1: Uninstall with Command Prompt

Run the uninstall command from an elevated Command Prompt.

  1. Open Command Prompt as Administrator.
  2. Run the silent uninstall command.
cmd
"%ProgramFiles%\EditPlus\remove.exe" -s

Method 2: Uninstall with PowerShell

Run the same silent uninstall command through PowerShell.

  1. Open PowerShell as Administrator.
  2. Run the silent uninstall command.
powershell
Start-Process -FilePath "%ProgramFiles%\EditPlus\remove.exe" -ArgumentList '-s' -Wait

Deployment Examples

Drop the snippet below into your deployment tool, Group Policy, or scheduled task. It wraps the silent install command for EditPlus as a PowerShell script — copy, save, and run.

PowerShell script example

Save the following content as install-editplus.ps1 in the same folder as the installer.

powershell
Set-Location -Path $PSScriptRoot
$Installer = 'ES-Computing.EditPlus.6.1.780.0.X64.exe'
$Installer -s -sp-s
exit $LASTEXITCODE

Frequently asked questions

Can I silently install EditPlus on Windows?
Yes. This guide uses Unknown switches for a completely unattended installation of EditPlus 6.1.780.0 without user prompts. It is commonly used with Intune, SCCM, PDQ Deploy, and RMM tools.
Do I need administrator privileges to install EditPlus?
Yes, administrator rights are required to install EditPlus. Run the installer as Administrator or deploy it using the SYSTEM context.
Will installing EditPlus restart the computer?
No. The EditPlus install commands in this guide do not cause an automatic restart on Windows. If a reboot is needed by the application, plan it through your deployment tool.
How do I verify EditPlus installed successfully?
Verify that EditPlus installed successfully by using the detection rule in this guide, such as a file path, registry key, MSI product code, or MSIX package family name. These are commonly supported by Intune, SCCM, and PDQ.
How do I silently uninstall EditPlus?
To silently remove EditPlus, use the silent uninstall command provided in this guide.
Which deployment tools support these commands?
These EditPlus commands are commonly used with Intune, SCCM/MECM, PDQ Deploy, ManageEngine, NinjaOne, Datto RMM, Atera, and Action1.

Troubleshooting

If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.

Run as administratorMake sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions.
Verify the installer file nameConfirm that the installer file name matches the command shown in this guide: ES-Computing.EditPlus.6.1.780.0.X64.exe.
Run from the correct folderRun the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder.
Check exit codesIf the installer returns a non-zero exit code, review the installer log or your deployment tool's logs. Some packages use additional success exit codes.
Restart if requiredIf the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer.
Validate detection rulesIf your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully.

Deployment recap

Before you roll EditPlus out to production, confirm you have:

  • The silent install command, run from an elevated prompt
  • The matching silent uninstall command for rollback
  • The detection rule wired into your deployment tool

Got all three? You’re ready to deploy at scale. If this guide saved you time, fuel the next one:

Rating
be the first to rate

Comments

Loading comments…

    Leave a comment

    ✎ Edit