One of the IIS short file name vulnerability patching methods change the registry one note

1)
1.png is a scan when there is no fix for the vulnerability

Repair:
2) Modify the registry key value:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem

Modify NtfsDisable8dot3NameCreation to 1.

2.png to modify the registry and restart the machine after the scan

3) The source code clips or copied to other directories such as D:\wwwroot\ ==> D:\wwwroot.bak\, and then copy the D:\wwwroot.bak\ files back (the clip is copied, copy the old directory of the file to delete all)

3.png
Scan again, bug fix

Ps:
After the registry changed, the code location has to be re-moved, the vulnerability can be counted.

One of the IIS short file name vulnerability patching methods change the registry one note