Post problem reports here for Batch files for use in BSOD debugging

Matthew Wai said:

You cannot do that without the approval of the administrator who has removed the original version of LOGS.bat.

True, I had forgotten about that, thanks.

Matthew Wai said:

You should have written the above post in this thread.
You should have posted a link to 【LOGS.bat】, so that the administrator could download it.
You should have clicked on "Edit Post" --> "Save Changes" without making any changes, so that the text "@Matthew Wai", intended to be a notification, would work.

Before I start looking through the files, it looks like the script doesn't support onedrive desktop locations.

network\wlan.txt Has to go, as it has SSID info.
network\wlan-report-latest.html Has to go, IPV6 and other PII
network\WORKSTATION-SMB-Config.txt Has to go, IPV6 and other PII

In fact I'm stopping there, this created 25mb of logs for my pretty clean new install - the script is blindly collecting too much information so fully vet, collecting info should be targeted for just what you need and not for every possibility.

John, would it be best to delete the LOGS.bat entry in the BSOD repository then?

zbook said:

LOGS.bat is very useful for Windows upgrade troubleshooting.
It was created by the script guys on Technet.
It is currently used by Microsoft.
I'd like to have a working copy for us so that it can be used for BSOD and Windows upgrade troubleshooting, and any thread in which there are problems running V2.
For networking the commands for the whole network folder could be deleted.
(I've not yet used the contents of this folder).
(Maybe someone in the networking and sharing forum could indicate which are most useful?)

It collects far too much irrelevant information that could/does contain PII, why are a users SSID's needed to troubleshoot anything other than a wifi network issue? 123k just on Printer names and locations - not needed, it just goes on.

We should only be collecting the info we need and not a full forensic breakdown of a user's PC as it's just too hard to guarantee that PII isn't being leaked.

The script does provide great info, but it should be broken down and the sections used surgically to protect the user's information.