You receive the error, "SMBv1 server check failed" when running a Computer Details scan or any Scan Profile that uses the Computer Details scanner.
If you run the following command in a PowerShell prompt on the target computer throwing the error, you might also receive an error:
Invoke-CimMethod -Namespace root/Microsoft/Windows/SMB -ClassName MSFT_SmbServerConfiguration -MethodName GetConfiguration
This error is likely caused by a registry SMBv1 server setting that is either misconfigured, corrupted, or contains non-standard data. Specifically, a key/value in, HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters (though can exist elsewhere in the LanmanServer key or even in a different registry location)
For example, one customer had the DisableStrictNameChecking value set in HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters, which caused the scanner to fail.
See this TechNet thread for another example. Check any GPO or other script that could make changes to the registry. To resolve the issue, correct the registry and attempt the scan again.