This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi ,
I have a query regarding Microsoft.Synchronization.Data.Server.dll. One of the country's trusted cyber security sources define the hash "da5ee020bef41dc95c3532cbaa1ea8f4" to be suspicious/malicious. The hash is for file "Microsoft.Synchronization.Data.Server.dll". How can I verify that the original microsoft .dll hash and the one with above hash are same ?
Multiple open source resources verified the file "Microsoft.Synchronization.Data.Server.dll" with hash "da5ee020bef41dc95c3532cbaa1ea8f4" to be genuine. Is there any way to confirm the .dll is safe and has not been injected ?
current Location of file in the server:
| Hash Results | File Directory |
|---|---|
| da5ee020bef41dc95c3532cbaa1ea8f4 | c:\Program Files (x86)\Microsoft Synchronization Services\ADO.NET\v1.0\Microsoft.Synchronization.Data.Server.dll |
| da5ee020bef41dc95c3532cbaa1ea8f4 | c:\Windows\assembly\GAC_MSIL\Microsoft.Synchronization.Data.Server\1.0.0.0__89845dcd8080cc91\Microsoft.Synchronization.Data.Server.dll |
Thanks in advance!
Best Regards,
Mahadev
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Hi Mahadev,
Your query regarding Microsoft.Synchronization.Data.Server.dll would be best addressed on MSDN forums. Most of the users on this forum are professional programmers which would address and help you out to answer your questions.
Let us know if you have other queries.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
