Forum Discussion
ATP Sensor will not install on Windows 2016
Environment: Windows Server Standard 2016, vSphere 7x, Hardware requirements met, .Net Framework 4.8.
We have 4 Windows Server 2016 Domain Controllers that all experience the exact same error that prevents us from installing the download classic sensor. I have tried rebooting, run as admin, upgrading .Net framework (from 4.7 to 4.8), etc. This occurs on all 4 DCs that are 2016. We have successfully installed on the 2019 DCs. I have searched online for this error but all suggested fixes are Visual Studio related and I dont think it applies to our situation.
"Error DeploymentManager ShowErrorMessage System.IO.FileLoadException: Could not load file or assembly 'System.ValueTuple, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)" error.
10 Replies
They finally updated the Sensor version in our portal and it now works. Thank you for your insight.
I am hoping this new working client takes time to show up on our portal because I just downloaded and tried installing on two different DC's in 2 separate datacenters and both game me the exact same error. This has been frustrating. I will try again in a few hours. Thank you for assisting so far.
- EliOfek
Microsoft
There is no point in multiple tries...
Can you go to
https://security.microsoft.com/securitysettings/identities?tabid=about
and tell me what is Sensor version you see there?
It should be 2.240.18612.44306.
If it's not, no point in even trying, it means there are still issues.You're on to something. Our version is older. I guess there's nothing I can do until this is rectified?
Is it possible to download a different version of the classic sensor? I have already spent an ungodly amount of hours trying to get this to work and am at my wits end.
- EliOfek
You can only download the version that the portal supports at the time.
The issue was fixed, refreshing the portal and downloading a new package now should resolve the issue.
(The issue was in one of the US clusters and now fixed).
Apologies for the inconvenience and thank you for this feedback that brought this to our attention so we can fix it faster.
- EliOfek
Hi,
This was a known issue in the package version you downloaded and should be fixed already.
Please try to download the newer version now available in the portal and try again.I just downloaded fresh from MDE site and still get the same error. Any other ideas?
