Skip to main content
Prowork Desktop installs per Windows user. Each user gets their own copy, signs in to Filed with their own code, and receives updates without admin rights. On a shared host, running the installer as an admin therefore installs Prowork for the admin only. install-all-users.ps1 closes that gap. An admin runs it once, and Windows installs Prowork silently for each user the next time they sign in.

​
What the script does

When an admin runs it, the script:
  1. Downloads the latest Prowork installer from Filed.
  2. Checks that the installer carries a valid digital signature from Filed, Inc., and stops without changing anything if it doesn’t.
  3. Stores it in C:\ProgramData\Filed\Prowork. Users can run it there but can’t change it.
  4. Registers it with Windows Active Setup, a built-in Windows feature that runs a command once for each user when they sign in.
When each user next signs in, Windows installs Prowork for them in %LOCALAPPDATA%\Filed Prowork, with no wizard and no admin prompt. Prowork then starts at sign-in and waits in the system tray for the user’s Filed sign-in code.
Users who already installed Prowork themselves are skipped, so they keep their current version.

​
Before you start

  • An admin account on the host.
  • Windows PowerShell 5.1 or later, which is included in Windows 10, Windows 11 and Windows Server 2016 and later.
  • Outbound HTTPS access to storage.googleapis.com, or a copy of the installer you have already downloaded (see Use a downloaded installer).
  • Microsoft Edge WebView2 Runtime installed for all users. Windows 11 and Azure Virtual Desktop images include it. The script warns you if it’s missing.

​
Install for all users

1

Open PowerShell as administrator

Sign in to the host with an admin account. Right-click Windows PowerShell and choose Run as administrator.
2

Download the script

3

Run it

The download is about 300 MB. When it finishes, the script prints the Prowork version that will be installed for each user.
4

Have each user sign out and sign back in

Prowork installs at the user’s next sign-in. A user who only disconnected and reconnected hasn’t signed in again, so they need to choose Sign out from the Start menu first.The install takes about 30 seconds. On a user’s first sign-ins Windows can hold back startup apps, so Prowork may take a minute or two to appear in the tray.
5

Each user connects Prowork to Filed

The user opens Prowork from the tray or the desktop shortcut and enters their own Filed sign-in code.
Admin accounts that sign in get Prowork too. A copy isn’t connected to anyone’s Filed account until that user enters a sign-in code.

​
Check that a user has Prowork

Signed in as the user, Prowork appears in Settings > Apps as Filed Prowork. From PowerShell:

​
Updates

Each user’s Prowork updates itself, without admin rights. Running the script again only refreshes the installer used for users who haven’t signed in since. It doesn’t reinstall Prowork for users who already have it.

​
Use a downloaded installer

For a host without internet access, or to pin a version, download the installer separately and pass it to the script:
The script checks the signature of that file in the same way.

​
Remove the all-users install

This removes the cached installer and stops installs for new users. It doesn’t uninstall Prowork for anyone. Each user who already has it keeps their copy until they remove it from Settings > Apps.

​
Other deployment tools

The Prowork installer is silent with /S. Tools that run commands in the signed-in user’s context, such as Intune, an RMM tool or a Group Policy logon script, can run it directly:
Add /R to start Prowork when the install finishes.
Running the installer as SYSTEM or as an admin installs Prowork for that account only, not for the signed-in user.

​
Troubleshooting

Check that the user signed out and signed back in after the script ran. Reconnecting to a disconnected session doesn’t count as a sign-in. Also check that the script finished without errors and that C:\ProgramData\Filed\Prowork\Filed-Prowork-setup.exe exists.
Wait a minute or two after a first sign-in. If it still isn’t running, open it from the Start menu or the desktop shortcut.
The download was incomplete or changed in transit, or a proxy replaced it. Run the script again, or download the installer separately and use -InstallerPath.
Install the Microsoft Edge WebView2 Runtime once for all users from Microsoft. Otherwise each user’s Prowork install adds its own copy.