Skip to content

chore: Update windows defender configure action - #3315

Merged
timcassell merged 1 commit into
dotnet:masterfrom
filzrev:chore-update-configure-defender-action
Nov 5, 2026
Merged

timcassell merged 1 commit into
dotnet:masterfrom
filzrev:chore-update-configure-defender-action

Conversation

@filzrev

@filzrev filzrev commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

This PR update add-windowsdefender-exclusions composite action.
And add scripts to collect/print WindowsDefender related information when script failed.

Background

Windows Defender configure action is still failed randomly with following error.
(Currently It's occurred on windows-11-arm image only)

Warning: Failed to configure Windows Defender exclusions (attempt 1/5). Retrying...
  Warning: Failed to configure Windows Defender exclusions (attempt 2/5). Retrying...
  Warning: Failed to configure Windows Defender exclusions (attempt 3/5). Retrying...
  Warning: Failed to configure Windows Defender exclusions (attempt 4/5). Retrying...
  Add-MpPreference: Operation failed with the following error: 0x800106ba. Operation: MpPreference. Target: ConfigListExtension.

It looks like Windows Defender Service is not started when running CI.
So it need to collect WindowsDefender service information.

Note:
As far as I've confirmed, latest actions/runner-images repository.
Windows OS image exclude C:\ and D:\ drive by default.
https://github.com/actions/runner-images/blob/main/images/windows/scripts/build/Configure-WindowsDefender.ps1

So it might not needed to run add-windowsdefender-exclusions composite action anymore.

Though, It need to collect information to confirm WindowsDefender service is not started issue on windows-11-arm image.

@timcassell
timcassell merged commit ecfec51 into dotnet:master Nov 5, 2026
11 checks passed
@timcassell timcassell added this to the v0.16.0 milestone Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants