Tool detects SMBv1 enabled, even though feature isn't installed

[get-fooby]

When recently conducting a test of a Windows Server 2016 device, the SMBv1 feature was not present on the host however, the logic to detect SMBv1 reported that SMBv1 wasn't explicitly disabled. While correct, SMBv1 isn't explicitly disabled, the feature is not present.

The tool should perform one of the following

• Nothing different: it's correct in that SMBv1 is indeed not explicitly disabled even though the server is not explicitly vulnerable to any SMBv1 attacks as it isn't present.
• Not report that SMBv1 is explicitly disabled: SMBv1 is simply not present on the device
• Report both: SMBv1 is not explicitly disabled, but that there is no issue as the feature is not installed to this server and so the server is not vulnerable.

At present, the output does not consider the SMBv1 feature within the report.