Maybe this is of relevance for you:
You could try to update powershell.
And this thread seems to have the same error message:
and also some solutions.