Apache Log4j Detection for Windows - Manifest / Properties...

So scan entire file systems along with inspecting each Java archive file in-depth continues whether "thorough test" and "override normal accuracy" is set or not. The change here is to not check manifest and properties files unless you have those things set.

This does not appear to help with the memory usage issue, which according to the engineers/developers I have reporting issues to me is due to "not disposing of their zip archives when done using them, and leave them open until the script completes". If you do not have enough RAM for the amount of JAR/WAR/EAR files, you may see a powershell instance consume all available RAM. "in my experience with Powershell, it can be very lazy about garbage collection and you often need to call it explicitly when working with large data structures."

Another one also found this: "> cmd.exe /c dir /A-L /s /r /b

will recurse symlinks. As such, when it finds a symlink to a directory containing WAR/JAR/EAR files, I believe it will multiply the memory required to parse the true directory at best, and at worst parse any symlinks recursively until the machine runs out of RAM(to hold the list of paths) or pathlength(260 default)."