TLS 1.0 and 1.1 still flags on Windows Server 2016 after disabling via reg key

We have Windows Servers that are being flagged as having TLS1.0 and 1.1 enabled even after disabling via reg key. They are being flagged against a specific port to do with an app that was removed last year but we can’t find any trace of that app anywhere. Another interesting thing is that the reg key fix worked on Server 2019 but still persists on 2016 i.e. Server 2016 is still being with flagged with having TLS1.0 and 1.1 enabled while 2019 doesn’t after reg key fix.
Hope that makes some sense. Anyone else have any similar issues?


Update: The issue was with my scan template. It did not cover the port in question. Once I included the port in the scan template, IVM correctly found it to not be vulnerable to legacy TLS connections.