Test-ExchAVExclusions: allow icuuc.dll and icuin.dll

[DKhrebin]

The allow list carries icu.dll but not the two ICU component libraries that Windows ships next to it, icuuc.dll and icuin.dll. All three are present in System32 through Windows Server 2025.

Because of that, the FIP-FS processes that do text extraction and scanning, ParserServer and scanningprocess, report both libraries as unexpected modules on every run, which is noise that hides the findings that matter.

Sample output before the change:

PROCESS: ParserServer PID(51008) UNEXPECTED MODULE: icuin.dll COMPANY: The ICU Project
        PATH: C:\Windows\SYSTEM32\icuin.dll
        FileVersion: 61, 1, 0, 0
PROCESS: scanningprocess PID(30240) UNEXPECTED MODULE: icuuc.dll COMPANY: The ICU Project
        PATH: C:\Windows\SYSTEM32\icuuc.dll
        FileVersion: 61, 1, 0, 0

.build\CodeFormatter.ps1, cspell and .build\Build.ps1 all pass.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟢 Approval recommended

The narrowly scoped allowlist update has no unresolved blocking issues.

Pull request overview

Updates the AV exclusions tester to recognize Windows Server 2025 ICU component libraries.

Changes:

• Adds icuuc.dll and icuin.dll to the module allowlist.

File summaries

File	Description
Diagnostics/AVTester/Test-ExchAVExclusions.ps1	Allows the two ICU component DLLs.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.