Resolving ProductivityBlocks Install Failure on Windows 10 64-bit

Problem Overview

AutomationDirect ProductivityBlocks (the graphical block programming environment used with the P1AM-ARDUINO ProductivityOpen shield) fails to install on a 64-bit Windows 10 workstation when the host machine is configured with the Arduino IDE from the Microsoft Store. The installer either terminates silently, hangs at the "extracting" stage, or returns a generic Windows AppX deployment error, even though Arduino IDE 1.8.12 is reported as functional and the P1AM controller is operating normally on its own.

Because the P1AM CPU is actively running ladder logic and the Arduino sketches are uploading successfully, technicians frequently assume the problem is in ProductivityBlocks itself. The actual root cause is an environment mismatch: the ProductivityBlocks installer was built against the legacy Win32 Arduino distribution and cannot register its package metadata against the sandboxed UWP "Arduino IDE" app distributed through Microsoft Store.

Affected Configurations

Root Cause Analysis

The Microsoft Store version of the Arduino IDE is delivered as a UWP / MSIX package. Three structural differences make it incompatible with ProductivityBlocks:

1. Install Path: The Store app installs to %LOCALAPPDATA%\Microsoft\WindowsApps\<package> in a per-user, ACL-restricted AppX container. The ProductivityBlocks installer writes Arduino board package metadata, examples, and CLI tools to %LOCALAPPDATA%\Arduino15\packages and the legacy sketchbook under Documents\Arduino\libraries\ProductivityBlocks, paths that the AppX container does not expose to the system-wide installer.
2. Elevation Model: "Run as administrator" on a Store app does not grant write access outside the AppX container. Even when the ProductivityBlocks installer is launched elevated, the Arduino registry hive that the installer queries is virtualized per-package and resolves to a non-writable stub.
3. Process Token: The Store build is launched by AppXSvc under a different session token than the Win32 build. ProductivityBlocks registers a prebuilder.jar hook that introspects the running arduino_debug.exe process; when the host is the AppX shim (Arduino IDE.exe mapped to MicrosoftCorporationII.WindowsAppRuntime...), the introspection fails and the installer aborts the package copy.

This is a confirmed, tracked issue on the AutomationDirect/ProductivityBlocks issue tracker (issue #1: Microsoft Store Arduino IDE blocks install).

Prerequisites

• Local administrator account on the Windows 10 64-bit workstation.
• Working internet egress to github.com, arduino.cc, and downloads.arduino.cc.
• Approximately 1.2 GB of free disk space (Arduino IDE 1.8.x + Java JRE + ProductivityBlocks libraries).
• USB connection to the P1AM-ARDUINO shield installed on a Productivity Series CPU (any P1 CPU with a ProductivityOpen header).
• Existing ladder program (optional) to confirm Arduino sketches are still uploading to the controller.

Step-by-Step Resolution

1. Confirm the source of the existing Arduino IDE.
   • Open Settings → Apps → Apps & features.
   • Search for "Arduino IDE". If the publisher shows Microsoft Corporation or the source is Microsoft Store, it is the incompatible build.
   • Note the install path. Store builds are located under C:\Program Files\WindowsApps\ArduinoLLC.ArduinoIDE_* (hidden AppX folder).
2. Uninstall the Microsoft Store Arduino IDE.
   • From Apps & features, select Arduino IDE → Uninstall.
   • If uninstall is blocked (Store licensing), open an elevated PowerShell and run Get-AppxPackage *ArduinoLLC.ArduinoIDE* | Remove-AppxPackage.
3. Download the Win32 Arduino IDE installer.
   • Navigate to arduino.cc/en/software and select Windows 7 and up (NOT the "Microsoft Store" option on the page).
   • Save the installer to a local path, e.g. C:\Installers\arduino-1.8.19-windows.exe.
4. Install the Win32 Arduino IDE.
   • Right-click the installer → Run as administrator.
   • Accept the default C:\Program Files (x86)\Arduino install path.
   • Allow the installer to install the Adafruit / Arduino USB drivers when prompted.
5. Verify the Win32 install.
   • Launch Arduino IDE from the Start menu and confirm the title bar shows Arduino 1.8.x (the Store build shows "Arduino IDE" without a version number).
   • Open File → Preferences and record the sketchbook location; ProductivityBlocks will install libraries to a sub-folder here.
6. Download the latest ProductivityBlocks release.
   • Go to the ProductivityBlocks Releases page and pull the most recent .exe installer.
   • Close any open Arduino IDE windows before continuing.
7. Run the ProductivityBlocks installer elevated.
   • Right-click the downloaded installer → Run as administrator.
   • Accept the license, choose the install path (default is recommended), and complete the wizard.
   • Installer completes in seconds once the Win32 Arduino IDE is in place.
8. Launch ProductivityBlocks.
   • Open Arduino IDE, then launch ProductivityBlocks from the Start menu or desktop shortcut.
   • Confirm the ProductivityBlocks menu appears under Tools in Arduino IDE.

Verification Procedure

1. Open Arduino IDE 1.8.x (Win32 build). Confirm the splash screen and version string in the window title.
2. Launch ProductivityBlocks and create a new project.
3. Drag a "Digital Write" block onto the canvas, set pin 13, and click Upload to P1AM.
4. Verify the sketch compiles and uploads to the P1AM-ARDUINO shield without error.
5. Monitor the P1AM CPU's COM port in Device Manager (Ports & COM) – the port should enumerate as USB Serial Device (COMx) and remain stable across uploads.
6. Cycle power on the Productivity Series CPU and confirm the last uploaded sketch starts automatically (bootloader recovery).

ProductivityBlocks Architecture

ProductivityBlocks is a Java-based visual programming front-end built on Google's Blockly library, packaged with a Windows installer that performs four discrete operations:

1. Registers a custom Arduino library path under %USERPROFILE%\Documents\Arduino\libraries\ProductivityBlocks.
2. Adds a prebuilder.jar hook that runs prior to arduino-builder to inject P1AM-ARDUINO board definitions.
3. Writes CLI symlinks for the ProductivityBlocks upload protocol over the P1AM serial bridge.
4. Installs a Windows registry key under HKLM\SOFTWARE\Arduino\Arduino IDE used to locate the parent IDE.

Step 4 is the failure point with the Microsoft Store IDE: the AppX package does not write that registry hive, and the ProductivityBlocks installer's discovery routine returns a null path, which is then reported as "no compatible Arduino IDE found."

P1AM-ARDUINO Hardware Compatibility

Troubleshooting Matrix

Preventive Controls

• Establish a deployment standard image that includes the Win32 Arduino IDE 1.8.x and excludes any Microsoft Store Arduino package.
• Use Group Policy or AppLocker to block the ArduinoLLC.ArduinoIDE package family for engineering workstations.
• Document the install procedure in the plant's automation workstation setup checklist.
• Pin the ProductivityBlocks GitHub repository to a monitored watch list to receive notifications on new releases and known-issue updates.
• When training new technicians, walk through the ProductivityBlocks training video to reinforce the Win32 IDE requirement.

Related Configuration Notes

The ProductivityBlocks installer's reliance on the legacy Win32 Arduino path is intentional: the Microsoft Store IDE is a UWP container and cannot be extended by third-party package installers without explicit MSIX bundle support. AutomationDirect distributes ProductivityBlocks as a Win32 installer for this reason. New technicians should be trained to download Arduino IDE from arduino.cc directly, not from the Windows Store tile on first-run Windows 10 installations.

For technicians working in restricted environments where Microsoft Store apps cannot be removed (for example, Windows 10 in S Mode), ProductivityBlocks is not a viable workflow and the P1AM-ARDUINO should be programmed through standard Arduino sketches (text-based) rather than the block interface.