problem with automatic download of print support app

Automatic PSA download and association are not controlled by the manufacturer name in the Store listing or in the PSA package, but by how the PSA is associated with the printer in Windows.

For consumer and standard scenarios, automatic download works like this:

1. The printer is installed and exposes a Hardware ID or Compatible ID.
2. A printer manufacturer publishes an extension INF (psa.inf) to Windows Update that:
   • Matches that Hardware ID/Compatible ID, and
   • Specifies the PSA association.
3. When the printer is connected, Windows uses that extension INF to automatically download and install the PSA from Microsoft Store.

Key points relevant to the scenario:

• The association is based on the printer’s Hardware ID/Compatible ID and the extension INF published on Windows Update, not on the manufacturer name string.
• If the extension INF is not correctly prepared, not installed, or not published via Windows Update for that printer ID, Windows will not automatically associate and download the PSA. In that case, the UI will show “Get App” even though the PSA can be installed manually from the Store.
• For enterprise/business environments, PSA association can also be overridden via a registry key under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PSA\Association where the value name is the printer Hardware ID/Compatible ID and the value data is the PSA AUMID (for example, "dd5de805-d9bb-4785-88e9-399cbff2130e_ph1m9x8skttmg!App"). This registry-based association has higher priority than the extension INF.

Therefore, a different manufacturer name such as "ZZZZZZ" does not by itself block automatic download. The issue is more likely that:

• The psa.inf extension INF is not correctly associated with the printer’s Hardware ID/Compatible ID, or
• The extension INF is not installed/published in the environment where testing occurs, so Windows falls back to showing “Get App”.

Verifying steps:

1. Confirm the printer’s Hardware ID/Compatible ID on the target system.
2. Ensure the psa.inf correctly references that ID and is installed (or published via Windows Update) for that printer.
3. Optionally, for enterprise testing, configure the PSA association via the registry key with the correct AUMID and Hardware ID/Compatible ID, then reconnect or reinstall the printer and verify that the PSA is used instead of “Get App”.

References:

• Print support app association
• Printer extensions
• Print Support App v1 and v2 design guide
• UWP device apps for printers (print)
• Sample Printer INF Files
• Printer INF files
• Package-Aware Print Drivers that Do Not Share Files