PublishSymbols fails after Windows Update

[lg2de]

Required Information

Question, Bug, or Feature?: Bug
Enter Task Name: PublishSymbols

Environment

• Azure DevOps Server (on-premises) Version Dev17.M153.5
• private Agent
  • on Windows Server 2019 Version 1809
  • agent version 2.170.0
  • 5 agents are identically configured to the same pool

Issue Description

The builds using PublishSymbols task were running fine until installation Windows updates.
Now the step fails with Encountered Win32 error '203' from method 'SymEnumSourceFiles'.

• We are using V1 and V2 of Publish symbols.
• Last successful run around 5th august.
• Windows updates installed on 13th august: KB4570505, KB4565349, KB4566424

Similar issues exist but already closed without helpful information:

• [Resolved] PublishSymbolsV2: Win32 203 error #9139 => x64 version on x64 Windows is installed
• PublishSymbols results in 'Encountered Win32 error '203' from method 'SymEnumSourceFiles'  #13439 => self-closed after downgrade to Win2016

Please note, the waning on dbghelp.dll is very confusing because expected and actual path are identical!

Task logs

1_Initialize Job.txt
14_Publish symbols.txt

Error logs

##[warning]Library dbghelp.dll is already loaded from an unexpected path. Expected 'C:\build\_work\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'. Actual 'C:\build\_work\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'.
##[error]Encountered Win32 error '203' from method 'SymEnumSourceFiles'.

[johnterickson]

@lg2de Are you running the 32-bit version of the agent or the 64-bit version of the agent? (For comparison to #9139)

[johnterickson]

@lg2de Also can you confirm that if you uninstall the KB, then this error goes away?

[isnits]

Hello,
The same issue here.
OS: Windows Server 2019 Standard Build 1809
Build agent: x64 version 2.153.1 installed on x64 OS
Tried with V1 and V2 Publish Symbols tasks
Mentioned updates are not installed in the system
Error:
[warning]Library dbghelp.dll is already loaded from an unexpected path. Expected 'C:\Builds_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'. Actual 'C:\Builds_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'.
##[error]Encountered Win32 error '203' from method 'SymEnumSourceFiles'.

[lg2de]

@johnterickson , initially I already noted that x64 is running.
I did not try to deinstall any windows update (KB?). This is the only change we noticed in the time range.

[M463]

I spend some serious time on this issue as well.
After failing to uninstall any of the mentioned KB (KB4570505, KB4565349, KB4566424) updates via wusa and experimenting with several versions of the task, I was eventually able to fix the problem by removing McAfee antivirus from the affected server.
It has since been replaced with a competitors product but unfortunately I'm not allowed to share the name of the product here due to company policies.

[Zanadar]

I am also experiencing this issue... can anyone confirm that removing a particular windows update resolves the issue?
Doesn't seem like anything else changed on the system in question.

[gwill1010]

I have the exact same issue too. Please respond.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[lg2de]

Disabling McAfee does not solve the problem.