Windows - Software - Install Artweaver Free (32-Bit)

What the Artweaver Free deployer does

This Automox Worklet™ deploys the 32-bit build of Artweaver Free to Windows endpoints. The Worklet reads the uninstall registry to detect a current install, downloads ArtweaverFree_32.exe from the Automox cache service, and runs the InnoSetup installer with /VERYSILENT and /NORESTART so the deployment never blocks the signed-in user. On 64-bit Windows, the application lands in C:\Program Files (x86)\Artweaver Free.

Artweaver Free is the free tier of Boris Eyrich's raster painting application. It is used by digital illustrators, art classrooms, and design training labs as a lightweight alternative to Photoshop or Krita. Standardizing on the 32-bit build keeps file format and plugin behavior consistent across mixed 32-bit and 64-bit Windows fleets, which matters for shared user profiles and shared art assets.

The Worklet is idempotent. If a DisplayName matching "Artweaver Free" already exists under the 64-bit uninstall hive or the Wow6432Node uninstall hive, evaluation exits 0 and remediation never runs. A reimage, an admin uninstall, or a profile rebuild flips the endpoint back to non-compliant on the next evaluation, and remediation re-deploys the installer with no human intervention.

Why deploy Artweaver from the Automox console

Creative and training endpoints rarely sit on a domain controller's reach. Art labs, design vendor laptops, and contractor workstations often live outside Group Policy, and they get reimaged on a schedule that breaks one-time installer scripts. A manual rollout means an admin opens the Artweaver download page on each endpoint, accepts the InnoSetup prompts, and confirms the install path. Repeating that on every art-lab and contractor workstation adds hours of operator time and produces version drift across the lab.

Deploy this Worklet to the art-lab and contractor workstation Device Group, and the next agent sync provisions a freshly imaged endpoint with the same Artweaver 32-bit baseline as every other lab machine, without anyone walking the floor with a USB stick.

How Artweaver deployment works

1. Evaluation phase: The Worklet uses [System.Environment]::Is64BitOperatingSystem to branch. On 64-bit Windows, it opens HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall via the Registry64 view and enumerates DisplayName values, then repeats the scan against HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall with Get-ChildItem and Get-ItemProperty. On 32-bit Windows, it scans only HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall. If any DisplayName matches "Artweaver Free", the script exits 0. If no match is found, it exits 1 and flags the endpoint for remediation.

2. Remediation phase: Remediation calls an ArtweaverCheck helper that scans the same uninstall hives but matches the broader pattern "Artweaver", so any Artweaver edition (Free or Plus) short-circuits the install with exit 0. If no Artweaver is present, the script downloads the 32-bit installer from the Automox cache endpoint (api.automox.com/api/cache with name=Artweaver_Free, os=Windows, arch=32) using System.Net.WebClient.DownloadFile to $scriptDir\ArtweaverFree_32.exe, then invokes it with Start-Process -ArgumentList ('/VERYSILENT', '/NORESTART') -Wait. ArtweaverCheck runs a second time to confirm the install, and any download or launch exception is caught and exits 1 so the failure surfaces in Automox activity logs.

Artweaver deployment requirements

• 32-bit or 64-bit Windows; on 64-bit Windows the application installs to C:\Program Files (x86)\Artweaver Free

• Network egress from the endpoint to api.automox.com over HTTPS (port 443) to pull the cached installer

• Local administrator privileges; the Automox agent context already meets this requirement

• Write access to the agent script working directory so System.Net.WebClient.DownloadFile can stage ArtweaverFree_32.exe

• No existing Artweaver edition (Free or Plus) on the endpoint; remediation matches the broader pattern "Artweaver" and skips install if any edition is registered under the uninstall hives

Expected state after Artweaver deployment

On a successful run, ArtweaverFree_32.exe is staged in the script directory, the InnoSetup installer completes with no UI, and Artweaver Free is registered under the appropriate uninstall hive (Wow6432Node on 64-bit Windows, the native Uninstall key on 32-bit Windows). The application is launchable from the Start menu under "Artweaver Free" and appears in Settings > Apps > Installed apps with a publisher of Boris Eyrich. Subsequent Worklet evaluations return exit code 0 and the endpoint reports compliant in the Automox console without re-running the installer.

Validate the deployment with Get-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object { $_.DisplayName -match 'Artweaver' } from an elevated PowerShell prompt; a single match confirms the install. Use FixNow from the Automox console for ad-hoc rollouts on freshly imaged art-lab endpoints, and pair this Worklet with an Uninstall Artweaver Worklet for full lifecycle coverage. To pin the deployment to a specific build, host the installer on an internal mirror and edit $url32 in remediation.ps1 to point at the mirror before saving the Worklet to your policy.