Short answer: when an HP dock firmware update fails with “Risky action blocked”, Microsoft Defender’s attack surface reduction (ASR) rule “Block process creations originating from PSExec and WMI commands” is stopping HP’s firmware installer, because the installer starts its update process through WMI. The fix is an ASR exclusion for the HP Firmware Installer folder, added by your IT team in Intune or Group Policy. Then restart and run the dock update again. Don’t turn the rule off for everyone.
A renewable energy business contacted us because one of their managers kept getting a Windows Security pop-up every time he plugged his laptop into his HP dock. The dock was offering a firmware update, but the update never finished. A few weeks later the same thing happened again on a newer dock at another of their sites. Both times, Windows Security’s Protection history showed the HP Firmware Installer being blocked by an attack surface reduction rule. We added a narrow exclusion for the installer, he restarted, and the dock firmware updated first time. Here is what we found and how to fix it.
Fixed by Kenn Cruz, IT Support Specialist, and Emma Mitchell, Senior Engineer at GCIT. Written up by Elliot Munro, CISO.
Symptoms
When you connect an HP USB-C dock or run the HP dock firmware update, a Windows Security notification appears and the update stops. In Windows Security > Protection history the entry reads:
Risky action blocked. App or process blocked: WmiPrvSE.exe. Blocked by: Attack surface reduction. Rule: Block process creations originating from PSExec and WMI commands. Affected items: C:\Program Files\HP\HP Firmware Installer\HP USB-C Dock G5\HPFirmwareInstaller.exe

You may also notice:
- The pop-up comes back every time you dock, because the dock keeps offering the same update.
- The organisation name appears in the message, for example “GCIT has blocked this action” or “Your IT administrator has blocked this action”.
- The affected item changes with the dock model, for example HP USB-C/A Universal Dock G2 or HP USB-C Dock G5, but the rule and the blocked process (
WmiPrvSE.exe) stay the same. - HP Support Assistant or HP Image Assistant reports the dock firmware update as failed.

Affected Software
- Application: HP Firmware Installer for HP USB-C docks (USB-C Dock G5, USB-C/A Universal Dock G2 and similar models)
- Platform: Windows 10 and Windows 11 with Microsoft Defender attack surface reduction rules in Block mode
- Related Services: Microsoft Intune endpoint security policies, Microsoft Defender for Endpoint or Defender for Business
Cause
Attack surface reduction rules are part of Microsoft Defender. They block behaviour that attackers commonly use, even when the file itself is not malware. The rule “Block process creations originating from PSExec and WMI commands” (GUID d1e49aac-8f56-4280-b9ba-993a6d77406c) stops programs from launching new processes through Windows Management Instrumentation (WMI), which is a popular way for attackers to move between computers.
HP’s dock firmware installer uses WMI to start part of its update. Windows sees WmiPrvSE.exe (the WMI provider host) trying to create a process for HPFirmwareInstaller.exe, matches the rule, and blocks it. The installer is legitimate. It just behaves like something the rule is designed to stop.
Because the rule is in Block mode, there is no “allow” button for the user. The exception has to be made in the security policy.
Resolution
For staff
- Take a screenshot of the Protection history entry (Windows Security > Protection history, then select the “Risky action blocked” entry to expand it). The rule name and the affected item are what IT needs.
- Send it to your IT support team and let them know which dock you are using.
- Once they confirm the exclusion is in place, restart your computer, plug back into the dock and run the firmware update again.
For IT: add a narrow ASR exclusion in Intune
- In the Microsoft Intune admin center, go to Endpoint security > Attack surface reduction and open the policy that sets your ASR rules.
- Edit the configuration settings. Either add a per-rule exclusion to Block process creations originating from PSExec and WMI commands (preferred), or add an entry under Attack Surface Reduction Only Exclusions, which applies to every ASR rule.
- Add the HP installer path. A folder path covers future dock models and installer versions:
C:\Program Files\HP\HP Firmware Installer\To be stricter, add the exact file instead, for example
C:\Program Files\HP\HP Firmware Installer\HP USB-C Dock G5\HPFirmwareInstaller.exe. - Save the policy. If you have more than one policy that sets ASR rules (for example a separate Defender for Endpoint policy), add the same exclusion to each one.
- On the affected computer, sync the device from Settings > Accounts > Access work or school > Info > Sync, or restart it so the policy is picked up.
- Have the user run the dock firmware update again and confirm it completes.
If you manage ASR rules with Group Policy instead, use Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Attack Surface Reduction > Exclude files and paths from Attack Surface Reduction Rules.
Check that it worked
Run the update, then look at Protection history again. There should be no new “Risky action blocked” entry, and HP Support Assistant (or the dock’s own updater) should report the new firmware version.
Important Notes
- Keep the rule on. The PSExec and WMI rule protects against a common technique attackers use to spread across a network. Exclude the HP installer path only, never disable the rule or switch the whole policy to Audit mode to get one update through.
- A file-level exclusion breaks on the next model. In our case the first exclusion was for one dock model, and a different dock at another site was blocked again a month later. A folder-level exclusion for
C:\Program Files\HP\HP Firmware Installer\avoids that. Only administrators can write to Program Files, which keeps the exclusion safe. - Exclusions can take time. A policy change in Intune can take up to a few hours to reach a device. A sync or a restart speeds it up.
- The block and a dock fault can be two separate problems. In another case, a staff member saw the same kind of Windows Security pop-up and could not use the monitors on an HP dock. We updated the ASR policy, synced the laptop and installed pending updates, but the screens still did not work through the dock. Reinstalling the dock driver did not help either. The monitors worked when plugged straight into the laptop, so we recommended repairing or replacing the dock. If the pop-up has stopped and the screens still do not work, test the dock and monitors separately before changing the security policy again.
- Other vendors do the same thing. Some Dell, Lenovo and printer driver installers also launch processes through WMI. If a different updater is blocked by the same rule, the fix is the same pattern with that vendor’s path.
Related Resources
- Microsoft Learn: Block process creations originating from PSExec and WMI commands
- Microsoft Learn: Enable attack surface reduction rules (including exclusions)
- Fix: Business Application Blocked by Attack Surface Reduction (ASR) Rules
- ThreatLocker Blocked an App? How to Request Approval
- Fix: “Action Blocked” When Opening Email Attachments in Outlook (ASR)
- Hardware and device management at GCIT
- Fix: AVD Session Host Build Fails at RD Agent Install (ASR Block)
If security tools are getting in the way of everyday updates in your business, get in touch with our team.