- August 22, 2016 at 5:58 pm #51494
I've posted this in the feedback hub (HERE) but I wanted to see if anyone else is experiencing the same issue and if there's any known work-around or fixes? This is affecting me as this is on my main workstation (*slap self on wrist*). If all else fails I may need to roll back the update.
The issue is that when trying to do an implicit remoting session and importing the session into my current console I get the error:
Import-PSSession : Could not load type 'System.Management.Automation.SecuritySupport' from assembly 'System.Management.Automation, Version=188.8.131.52,
August 22, 2016 at 6:49 pm #51508
- This topic was modified 1 month, 1 week ago by Peter Jurgens.
UPDATE: First work-around is launching powershell with "-Version 2.0". Going back to v2 is fairly painful but at least I can get through with some of the things I need through implicit remoting...August 23, 2016 at 2:45 pm #51640
Any other options on this? Having the same issue. I'm not sure going back to v2 is going to work for me.
August 23, 2016 at 9:21 pm #51701
- This reply was modified 1 month, 1 week ago by Paul Hawkinson.
Hi Peter, why don't you lodge this issue on UserVoice https://windowsserver.uservoice.com/forums/301869-powershell. I've had a few bugs on there fixed.
Make sure to title is 5.1 as this is the version of Powershell that comes with AU.August 24, 2016 at 5:50 pm #51773
Reported here: https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/15807028-bug-import-pssession-no-longer-works-since-win-10
and here: http://answers.microsoft.com/en-us/spark/eb85073b-0234-4f8d-a11d-d6a245286bae?page=3
So far only workaround is to use v2
You must be logged in to reply to this topic.