Skip to content
New

Noise Blocker 3: Real-time AI noise cancellation is here. Read the announcement

Deploy Noise Blocker Business

Install the virtual microphone with administrator privileges, then install the Business application as each employee.

Updated

Quick start

Use the same signed Business installer for both steps. The driver belongs to the Windows device. The application belongs to the employee’s Windows profile.

1. Install the driver as an administrator

Run this command as SYSTEM or from an already elevated administrator process:

Device context · administrator required
Setup.exe /S /COMPONENT=driver
  • Installs only the machine-wide Noise Blocker virtual microphone.
  • Returns 3010 when Windows must restart.
  • Leaves employee profiles unchanged.

2. Install the app as the employee

Wait for the driver installation and any required restart. Then run this command in the signed-in employee’s standard user context:

User context · standard user required
Setup.exe /S /COMPONENT=app /UPDATE_POLICY=managed /DRIVER_OWNERSHIP=external

Wrapped for display. Copy keeps the command on one line.

  • Installs Noise Blocker in that employee’s Windows profile.
  • Disables employee-managed application updates.
  • Leaves driver installation, repair, and removal to IT.

After installation, the employee signs in to their company access page and pairs Noise Blocker. The deployment package does not contain a company slug, employee email, pairing code, or licence.

Setup.exe command-line reference

Run the installer without arguments for an interactive installation of the driver and application.

Silent deployment uses this form:

Syntax
Setup.exe/S/COMPONENT={driver|app}[/ACTION=uninstall][/UPDATE_POLICY={managed|self-service}][/DRIVER_OWNERSHIP={external|self-service}]

Arguments

/S

Value
none (flag)
Applies to
All operations

Runs without prompts, browser launch, app launch, or automatic restart.

/COMPONENT

Value
driver | app
Applies to
Silent mode

Selects the machine-wide driver or per-user application. Every silent command requires this argument.

/ACTION

Value
uninstall
Applies to
Driver and app

Removes the selected component. Omit this argument to install or update it.

/UPDATE_POLICY

Value
managed | self-service
Applies to
App only

Choose managed when IT deploys updates. Choose self-service to allow in-app updates.

/DRIVER_OWNERSHIP

Value
external | self-service
Applies to
App only

Choose external when IT manages the driver. Choose self-service to allow employee-initiated driver setup and repair.

Rules and defaults

  • Argument names and values are case-insensitive.
  • Silent mode requires exactly one /COMPONENT argument.
  • Unknown, malformed, duplicated, or conflicting arguments return code 87.
  • A new app-only install defaults to UPDATE_POLICY=self-service and DRIVER_OWNERSHIP=external.
  • An update keeps the existing policy when the command omits that policy.
  • /ACCOUNT_SLUG is not supported and returns code 87.

Common commands

Update the application while keeping IT responsible for updates:

Update app
Setup.exe /S /COMPONENT=app /UPDATE_POLICY=managed

Remove the application from the current employee profile:

Remove app
Setup.exe /S /COMPONENT=app /ACTION=uninstall

Remove the shared driver from the device:

Remove driver · administrator required
Setup.exe /S /COMPONENT=driver /ACTION=uninstall

Exit codes

Code
0
Meaning
Success
Action
No action
Code
3010
Meaning
Success; restart required
Action
Schedule or prompt for a restart
Code
5
Meaning
Wrong privilege or execution context
Action
Run the driver as SYSTEM/admin or the app as the target employee
Code
87
Meaning
Invalid arguments or conflicting configuration
Action
Correct the command or stored configuration
Code
1603
Meaning
Installation or removal failed
Action
Collect the setup log, correct the cause, and retry

A failed command may have completed some steps. Check the installed state before retrying. Setup writes its operation log under the executing account’s temporary directory after initialization.

Microsoft Intune

Package the Business installer as a Win32 app . Create two Intune app entries from the package: one for the driver and one for the per-user application.

Driver entry

Use this install command:

Install command · administrator required
Setup.exe /S /COMPONENT=driver

Use this uninstall command:

Uninstall command · administrator required
Setup.exe /S /COMPONENT=driver /ACTION=uninstall
  • Install behaviour: System
  • Assignment: Device group
  • Restart code: Map 3010 to a soft restart

Detect the machine-wide virtual microphone and its supported driver version. Do not use an installer helper file as proof that the driver works.

Application entry

Use this install command:

Install command
Setup.exe /S /COMPONENT=app /UPDATE_POLICY=managed /DRIVER_OWNERSHIP=external

Wrapped for display. Copy keeps the command on one line.

Use this uninstall command:

Uninstall command
Setup.exe /S /COMPONENT=app /ACTION=uninstall
  • Install behaviour: User
  • Assignment: Employee user group
  • Success code: 0

Detect the application in the current employee profile. Check the installed version, Business mode, managed update policy, and external driver ownership. Company name is not a valid detection rule because it appears only after pairing.

Assignment order

  1. Assign the driver entry to a pilot device group.
  2. Wait for successful installation and complete any restart.
  3. Assign the application entry to the corresponding employee user group.
  4. Verify installation and pairing before expanding both assignments.

Shared Windows devices

Install the driver once per device. Assign the application to every employee who uses Noise Blocker on that device because the application and Business settings are per user.

Questions?

For any questions about deployment, contact [email protected] .