It's indeed a bug in Windows 10 1803. There's a workaround for the problem in WinSCP 5.13.2:
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Completely reinstalling winscp 5.13.2 seems to have solved the issue for me