log4shelldetect VS Windowslog4jClassRemover

I'm not sure what you mean. You can deploy a built binary over your network and run it on all your servers. For example: curl -sSL https://github.com/1lann/log4shelldetect/releases/download/v0.0.2/log4shelldetect_0.0.2_Linux_x86_64.tar.gz | tar -C /tmp/ -zxf - log4shelldetect && /tmp/log4shelldetect -mode list /path/to/scan 2>/dev/null would download and extract the prebuilt binary to /tmp, and run it scanning at /path/to/scan, only outputting paths to potentially vulnerable .jars and ignoring warnings. You can replace the URL with your own build or distribute your own build as you wish.

Read the README and the Release Notes https://github.com/CrazyKidJack/Windowslog4jClassRemover/releases/latest

This is fine if you only have 1 or two JAR files to deal with and you don't mind installing 7-sip to do it. However, if you have lots of JAR files, or if you don't want to install 7-zip, I created an open-source VBS script that will do it for you without needing to install any additional software. https://github.com/CrazyKidJack/Windowslog4jClassRemover

While most people that need to know probably already know enough to do what they need to do AND the information from the OP is way more complete than mine, I have not seen anyone create a Windows script that can remove the JndiLookup.class file from log4j-core JARs easily the way the zip command is able to on linux. So I thought I would post this here if anyone needs to do that... https://github.com/CrazyKidJack/Windowslog4jClassRemover