Catching Ctrl-c fails on Windows

[taldcroft]

From @jskrist :

The DelayedKeyboardInterrupt class in #177 does not seem to work as expected on Windows. When I use Ctrl+C to stop the program as the progress bar is updating (during file transfer), instead of the messages defined here, I see the message:

[PROGRESS_BAR_OUTPUT]forrtl: error (200): program aborting due to control-C event
Image              PC                Routine            Line        Source
libifcoremd.dll    00007FF80F1194C4  Unknown               Unknown  Unknown
KERNELBASE.dll     00007FF856AF56FD  Unknown               Unknown  Unknown
KERNEL32.DLL       00007FF859D74034  Unknown               Unknown  Unknown
ntdll.dll          00007FF85A213691  Unknown               Unknown  Unknown

Then after restarting the sync, and allowing it to finish, if I try to do a normal sync (without adding new files) there is always some file that seems "locked" which causes an error like:

2019-11-04 09:47:09,283 Processing 5min data for thm2eng
Traceback (most recent call last):
[error back trace]

  File "C:\ci\hdf5_1525883595717\work\src\H5F.c", line 511, in H5Fopen
    unable to open file
  File "C:\ci\hdf5_1525883595717\work\src\H5Fint.c", line 1604, in H5F_open
    unable to read superblock
  File "C:\ci\hdf5_1525883595717\work\src\H5Fsuper.c", line 413, in H5F__super_read
    file signature not found

End of HDF5 error back trace

Unable to open/create file '[LOCAL_PATH]\test\data\thm2eng\5min\TB2T3.h5'

Where the actual file that is unable to be opened or created changes, as does the type of statistic and MSID. I suspect it corresponds to the specific msid that was being downloaded when Ctrl+C was hit.