Winrm. Fix encryption problem or reinstall?

Question

PowerShell

I switched to Windows 10. For a
couple of days everything worked fine, today when I tried to create a new session to the exchange server via powershell with the standard New-PSSession command, I got the following:

PS C:\Windows\system32> New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri sus-sw-77/powershell
New-PSSession : [sus-sw-77] Connection to remote server sus-sw-77 failed. Error message:
The WinRM client cannot process the request. The encrypted message body is malformed and cannot be
decrypted. Make sure the service encrypts the message body according to the specifications. See the
edit section "about_Remote_Troubleshooting" for details.
string:1 char:1
+ New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108295,PSSessionOpenFailed

winrm pc output

PS C:\Users\n.shalnev> winrm qc
The WinRM service is already running on this computer.
WSManFault
Message = The WinRM client is unable to process the request. The encrypted message body is malformed and cannot
be decrypted. Make sure the service encrypts the message body according to the specifications.
Error code: -2144108295 0x803380F9
The WinRM client is unable to process the request. The encrypted message body is malformed and cannot be decrypted
. Make sure the service encrypts the message body according to the specifications.

PS for clarification: the console is running with administrator rights, everything is in order with the server, everything is successful from other PCs (though on WIN 8.1). On this computer, as the day before yesterday, the session was installed with the same command without problems ... I didn’t install anything new .. but just in case I deleted everything that I found superfluous.

Answer 1

Suddenly someone will help.
The problem turned out to be in ESET NOD 32. I solved it by removing the antivirus from the computer, now it no longer appears when installing the latest versions, apparently the problem was solved with updates.

Answer 2

And how do you connect to Exchange? Why is your Windows 10 PSSession trying to connect to localhost?
Not very clear problem. Need more details.