tshark.exe -a duration:<seconds> unreliable in Windows 10

edit

I'm finding that "-a duration:<seconds>" only works sometimes for tshark.exe in Windows 10. Has anyone else found this to be unreliable in Windows as well? The unreliability I'm observing seems to be somewhat correlated with how heavy my network traffic is. When it fails, the tshark.exe process launched with "-a duration:<seconds>" runs indefinitely.

Thanks