📎 AI Summary:
The thread discusses a change in behavior of a Win32 API used to collect TCP connection statistics, which no longer resets counters when toggled, a change acknowledged by Microsoft but unmentioned in official documentation. The original poster seeks clarification and guidance on this issue, while others suggest consulting development forums or verifying command sequences, though the issue appears to be linked to an undocumented change by Microsoft. Overall, the user expresses concern over the inconsistency and the lack of official information regarding this API behavior.

monitoring

New Member
Joined
Jul 27, 2020
Messages
2
Thread Author #1
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
 

Solution
Thanks for your reply. This is not a command but a win32 api call

This has been acknowledged as a problem by MS. The behaviour is not documented.

Link Removed

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
Probably want to ask this one on a development forum as far as MS documentation is concerned the function and related functions have not changed.
 

RuskinF

Member
Joined
Feb 17, 2020
Messages
87
Since when did you notice this behavior?
What other command do you run just before running this?
Is there a change in your habit of running this command before or after some other commands?

It may be that you have changed the sequence of running some commands which cause this behavior.
If Microsoft changed the command execution then they would have brought it to the notice of the people in their documentation.
 

monitoring

New Member
Joined
Jul 27, 2020
Messages
2
Thread Author #4
Thanks for your reply. This is not a command but a win32 api call

This has been acknowledged as a problem by MS. The behaviour is not documented.

Link Removed
 

Solution