Upgraded docker from 17.06.2-ee-15 to 18.03.1-ee-4 and some random error in Eventviewer

HI All,

Docker version 18.03.1-ee-4, build 0ded23c
Windows server 2016 version : 1607 build

I have upgraded docker EE from 17.06.2-ee-15 to 18.03.1-ee-4. I have couple of containers running without any issues

But I was checking event viewer logs and saw this error. I am curious what is causing these errors.

Any idea whats wrong.

1)

The description for Event ID 11 from source docker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

exec's CreateProcess() failed
container=8413a046ba3df4862a83f6e185091ff254ae82bd88111218daddc3782ddfd111 exec=f9c4504cee7ee9762908c55043f52def15a6d528ae38f05c7ba4147ea5967982 error=container 8413a046ba3df4862a83f6e185091ff254ae82bd88111218daddc3782ddfd111 encountered an error during CreateProcess: failure in a Windows system call: The requested compute system operation is not valid in the current state. (0xc0370105) extra info: {"CommandLine":"powershell ipconfig","WorkingDirectory":"/","CreateStdInPipe":true,"CreateStdOutPipe":true,"CreateStdErrPipe":true,"ConsoleSize":[0,0]} module=libcontainerd namespace=moby

2)
The description for Event ID 1 from source docker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Error setting up exec command in container c17fdc0640fb4c451834a8d39482ae6e2425f8b24ca5df6eb5c6df6ba3c44233: Container c17fdc0640fb4c451834a8d39482ae6e2425f8b24ca5df6eb5c6df6ba3c44233 is not running

Thanks,
Vishnu