Microsoft has acknowledged an issue with the latest Windows 10 security update KB4532693 and has provided detailed information about the issue and workaround in the article KB4542617. As per the KB article this issue applies to,
You can check issue and workaround in details below. Microsoft is continuing the investigation and promises to provide an update when more information is available.
Known issues in this update:
You might encounter issues using the Windows Server Container Image for the February 11, 2020 security update when used on a Windows Server container host that is not updated to the same security update.
When you run the command “docker run” you might not receive output and it might become non-responsive.
Your Windows Server Container in Kubernetes does not reach the “running” state
You receive the error, “docker: Error response from daemon: container <id> encountered an error during Start: failure in a Windows system call: The wait operation timed out. (0x102).”
The 2B February 11, 2020 security update for Windows Server container image was released but compatibility issues were found. While we investigate this issue, current pull requests using floating tags for Windows Server container images (such as ltsc2019, 1809, 1909, etc.) will temporarily default to pull the container images with the January 14, 2020 security update.
Mitigation: If you have already pulled the February 11, 2020 security update for container images and encounter issues, you will need to do one of the following:
We strongly recommend to update the container host to the February 11, 2020 security update for Windows (note: both the container and host need to be on the same Windows version, i.e. 1809, 1903, etc.)
Re-run the pull command or re-run your automation pipeline which will automatically pull the container image released January 14, 2020. Note We recommend you do not change your pull tags or automation at this time.