Had this error on a server, found an article that references Hyper-V which I did not have installed and in addition states that the error can be safely ignored… Lame. Why can it be ignored…
I noticed that the next entry after getting this error on every boot, was the VDS successfully starting.
The Virtual Disk service entered the running state.
On inspection the service is set to manual, so I can only assume that the first request to use the VDS cause the initial error but this request also has the server start the service. So I tried setting the service to start automatically and now the error is gone.
So again no explanation but a way to get the error removed from your logs…
How to stop this error coming again and again in the event viewer?
ReplyDelete