New
#51
Okay so the issue occurred in the new local account. A rerun of that powershell command in the new account completes with no problem. So far none of the suggestions have helped, though I need to see how to fix whatever the powershell issue was in the original account that caused that error. Reading more it seems that cortana error is common so maybe it is not a big deal. Meanwhile the issue continues.
Last edited by tomseys; 18 Nov 2015 at 20:33.