SharePoint 2016 Configuration Failed: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

adil 1,206 Reputation points
2020-12-27T13:14:11.13+00:00

Hi,I Prepared new SharePoint 2016 Test Server and when i run Configuration wizard in Updating SharePoint step it throws the following error:

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
anyone has idea how to fix this issue and for SharePoint Server is below Security policy required to be enabled or disable? i checked in server it was Enable.
security policy 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing'

51501-sp2916configfailed.png

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,810 questions
0 comments No comments
{count} votes

Accepted answer
  1. Trevor Seward 11,681 Reputation points
    2020-12-27T22:24:37.783+00:00

    FIPS must be disabled. SharePoint uses MD5 internally for fast hashing, but it does not use it for security purposes as MD5 is insecure.

    See https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/federal-information-processing-standard-security-standards.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. JoyZ 18,041 Reputation points
    2020-12-28T02:25:00.9+00:00

    Hi @adil ,

    As trevor said, disable FIPS group policy then run PS Config again, here are steps to disable the group policy:

    1. Open Local Group Policy Editor (gpedit.msc).
    2. Click Computer Configuration> Windows Settings> Security Settings> Local Policies>Security Options.
    3. Scroll to 'System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing' (this should not be enabled).
    4. Ensure the policy is DISABLED.
    5. Repeat on all Windows servers in your FARM which are affected.
    6. Perform IIS RESET.
    7. Verify the setting and ensure the policy is disabled.

    51484-image.png


    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments