03-19-2020 02:04 PM
Shut/No shut does NOT resolve the issue in our case.
The latest Microsoft patch causes the same issue.
Has Cisco been in contact with Microsoft to determine what the problem is?