You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an issue where the app Traffic Monitor for Windows fails to display network speed after the system has been running for an extended period (one week without shutting down). The app consistently shows 0.00 kbps in the taskbar display.
Steps to Reproduce:
Install Traffic Monitor for Windows.
-Enable the "Auto run when Windows starts" option in the app's general settings.
-Allow the app to start at boot by enabling it in the Task Manager's startup apps list.
-Use the system continuously without shutting it down for a week or more.
-Observe that the network speed in the taskbar displays 0.00 kbps despite active network usage.
Expected Behavior:
The app should display the current network speed accurately, even after prolonged system uptime.
Actual Behavior:
The network speed remains stuck at 0.00 kbps despite active network traffic.
The text was updated successfully, but these errors were encountered:
I encountered an issue where the app Traffic Monitor for Windows fails to display network speed after the system has been running for an extended period (one week without shutting down). The app consistently shows 0.00 kbps in the taskbar display.
Steps to Reproduce:
Install Traffic Monitor for Windows.
-Enable the "Auto run when Windows starts" option in the app's general settings.
-Allow the app to start at boot by enabling it in the Task Manager's startup apps list.
-Use the system continuously without shutting it down for a week or more.
-Observe that the network speed in the taskbar displays 0.00 kbps despite active network usage.
Expected Behavior:
The app should display the current network speed accurately, even after prolonged system uptime.
Actual Behavior:
The network speed remains stuck at 0.00 kbps despite active network traffic.
The text was updated successfully, but these errors were encountered: