I found out that KB4088876 - Security Montly Quality Rollup for Windows Server 2012 R2 for x64-based system caused this problem.  It happened while both uninstalling and installing the KB.  We will now pick this update appart to determine why this is happening and why it happened both in February and in March.