Windows 10: Troubleshooting the BETA log collector (extract > open)

In the BSOD forum there are two log collectors: DM and BETA
BSOD - Posting Instructions - Windows 10 Forums

In the VIP forum there is a thread for Improving the Log Collection Script.
Improving the Log Collection Script

There is a new version of the BETA log collector that has fixed a black box with red characters flash:
Improving the Log Collection Script
Now the log collector no longer flashes and will display the red characters.
This text is posted later in the thread.

On this computer the BETA log collector was used at least five times and there are currently five folders on the desktop.

Recently the BETA log collector stopped working and this thread is to troubleshoot the BETA log collector so that it can collect the logs in the typical two click method:
1) extract
2) open

These are some images:

























& : The term '.\resources\main.ps1' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:2
+ &'.\resources\main.ps1'
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.\resources\main.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\aaaaaaaa\AppData\Local\Temp\7zOC0FCEAB0>


How do you troubleshoot the BETA log collector or troubleshoot the computer so that it can extract and the open the log collector.
The extract had previously worked as there are five beta zip folders on the desktop. Something has happened to where the extract does not appear to work.
How do you troubleshoot the extract?

:)

 

Log Collector Fails


Hi Jeffsun13,

We currently are working on an updated version of the log collector, right now it is still in beta, but we'd like you to try it to see if it resolves the problem.

For now it's not in a nice .exe format, but it is still pretty straightforward to run. Right-click the .zip, select "extract all" then in the new extracted folder double-click "log-collector" to run it.

 

Extracting Zip Files


Are the step-by-step processes identical? That is, the folder extracted from and the folder extracted to belong to the same hierarchical file system structure. If they are, that suggests mildly the Cumulative Update left an electron or two out of place.

 

BSOD Kernel Security Check Failure


For any BSOD please use the beta log collector to post a new zip for troubleshooting.
log collector v2-beta08.zip
(extract > open)