Windows 10: UnitTestIsolation from VSTEST.console is Non Compliance to FIPS

After Enabling registry Key : @"HKLM\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy"; is set to 1 . During Smoke test execution in the pipeline : FIPS Non-compliance error is reported in the release pipeline: Error : Data collector 'UnitTestIsolation' message: Data collector 'UnitTestIsolation' threw an exception during type loading, construction, or initialization: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.Additional Information : https://learn.microsoft.com/en-us/windows/security/security-founda

:)

 

Windows FIPS -140-2 & 140-3 Compliance

I notice information on Windows FIPS compliance is located here: Federal Information Processing Standard (FIPS) 140 Validation - Windows security | Microsoft Learn to include information regarding NIST certificates. Every certificate listed is marked "Historical", meaning they are no longer active certificates. Many of them were pushed to this state due to SP 500-56rev3.

Does Microsoft have an approach, or timeline to getting these revalidated? Or if they've been revalidated can the page be updated to include the new Cert #s?

 

Microsoft brings FIPS 140 Compliance to Authenticator

Source: https://techcommunity.microsoft.com/...g/ba-p/2365671

 

Can't Connect to WiFi - FIPS Mistakenly Enabled

Hello,

Please answer the questions below:

• How did you enable FIPS?
• Did you enable FIPS from the router page?

Please let us know if you have followed the steps mention by Jitendra Kushwaha in the TechNet link which you have sent.

I request you to follow the steps and disable the FIPS and try to connect to the network after restarting the device.

Registry disclaimer

To do so: Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow
these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

I hope this helps you. If you have any further queries, feel free to contact us. We will be happy to help you.

Thank you.