This
problem is most likely caused by Microsoft’s updates

KB4048957、KB4048954、or
KB4048960;

[Depending
on which version of Windows you are using].

Please
check if the above updates were recently.

Anticipate
that Microsoft should fix the problem in future releases.

Here is
a temporary solution:

Windows7
/ Windows2008 - remove KB4048957 and KB4048960

Windows10
- remove KB4048954 and KB4048955

Window
2012 R2 - remove KB4048958 and KB4041777