This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 93%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
I have been using this API function a lot on older versions of windows to collect per connection tcp statistics.
Its behaviour seems to have changed of late. Previously disabling and re-enabling statistics would reset the counters for the statistics. This does not happen any more.
Can anyone point me in the right direction for a better place to ask this question if this forum is the incorrect location.
thanks
I neglected to add that the statistics never seem to get reset
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 20%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMO%3C/text%3E%3C/svg%3E)
Hello, I'm a Windows developer and I can confirm this is a bug. Can I ask what the impact of this bug is for you? Thanks!
Hi Matt, thanks for the reply. I have an app that makes extensive use of this API. At the moment I have tried to code around the issue by remembering the last values and then subtracting the current values to get the delta for the items that I know (and not all of them I am sure) are not reset to zero by disabling/enabling estats in newer versions of windows. This kind of works but will blow up eventually when the last value becomes too large. I imagine that this also impacts windows resource monitor as I can see it uses the same API.
Is there a chance that this will get fixed.
Hi,
According to your description, seems that your issue is more related with development of Windows. Try to create a new thread in Win32 API tag, they might be more familiar with your issue.
Win32 API subforum:
https://learn.microsoft.com/en-us/answers/topics/winapi-general.html
Bests,
Hi,
If any reply is useful for you, please mark it as answer.
Bests,
This behavior seems to have been introduced sometime in Windows 10. I have some versions of Windows 10 that behave like this:
1) Enable stats
2) Collect stats
3) Disable stats
4) Enable stats < - at this point all extended tcp stats have returned to zero
And some that do this
1) Enable stats
2) Collect stats
3) Disable stats
4) Enable stats <- at this point extended tcp stats counters remain as they were before step 3
WIndows 2019 seems to follow the second pattern. Some versions of Windows 10 follow the first pattern.
All versions of Windows prior to windows 10 that support TCP estats and that I have tested follow the first pattern.
