I do not know if that is still the case so ymmv. I didn’t think about this until I’d already cleared the files, but in the “olden days” you had to specify all three “special” attributes in the command (system, hidden, and read-only) in order to add/remove any of them, so that’s why I did it that way. With the system attribute gone, I was then able to delete the files and clear the vulnerability from Nessus. To make sure Flash is completely removed, head to Apps & Features page in the Settings app and uninstall it manually. Turns out that all four files had the system attribute set, so in an elevated command prompt, navigated to the folder and ran “attrib *.* -s -h -r” which removed the system attribute. Get Adobe Express free Adobe Flash Player EOL General Information Page Since Adobe no longer supports Flash Player after Decemand blocked Flash content from running in Flash Player beginning January 12, 2021, Adobe strongly recommends all users immediately uninstall Flash Player to help protect their systems.
Those files were quite persistent even changing permissions and ownership to Everyone did not allow them to be deleted, but did result in the fun message, “You require permission from Everyone to make changes to this file.” The only issue I had was that the DISM command (at least on 2016) still left the four ActiveX files under c:\windows\system32\macromed\flash intact, three of which were still triggering our Nessus scanner as critical vulnerabilities.
0 kommentar(er)
