Version 1.2037 does not have a fix for this Windows 10 bug, because the Windows bug is newer than the UCCNC version 1.2037, in other words 1.2037 was released earlier than the Windows bug was first introduced through the windows updates.
So, a workaround for this issue was introduced in version 1.2038 of the UCCNC. That and later versions have the workaround code for this problem.
viewtopic.php?f=2&t=240&start=40