failed to waitForNotification: callbackNumber does not exist in callbackMap

Hi,

xref:

• https://github.com/prometheus-community/windows_exporter/issues/1861

a EKS user recently reports a issue with the windows_exporter.

[...]
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1095
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1096
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1097
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1098
windows-exporter time="2025-01-29T14:07:57Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1099
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1100
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1102
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1103
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1104
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1105
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1106
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1109
windows-exporter time="2025-01-29T14:08:12Z" level=error msg="failed to waitForNotification: callbackNumber does not exist in callbackMap" callbackNumber=1108
[...]

After a quick research, the messages are coming from https://github.com/microsoft/hcsshim/blob/8d81359dc374e39d9edd63639a0402fbbea694f9/internal/hcs/waithelper.go#L37

As maintainer of windows_exporter, I would like to ask how I can identify the root cause? Or do I implement hcsshim wrongly?

• Windows: Server 2019
• hcsshim version: github.com/Microsoft/hcsshim v0.12.7

It is noticeable, that the same error appears with v0.12.5 as well.

Start with internal/hcs/waithelper.go at the reported callbackMap error and compare its behavior across hcsshim v0.12.5 and v0.12.7. Then inspect pkg/collector/container/container.go to determine how windows_exporter uses hcsshim. Done means identifying whether the exporter integration or hcsshim is responsible and documenting a reproducible root cause or required correction.