Windows 10: BETA Log Collector upload for slow boot troubleshooting

I have the latest version of windows 10 dual boot with ubuntu budgie and have been noticing slow boots. Yes, I've disabled fastboot, but I don't think that's the issue because when I had windows dual boot setup w/ linux mint for the first time on an older version of windows 10 (I think 1511), it didn't take as long as it does now. I think when removing linux mint something went wrong and now the boot is slower only for windows 10 partition. I can attach a screen shot of what you may want to look at in my BCD file via VisualBCD if requested. Also, There is a entry in the BCD called "Ubuntu" which isn't related to ubuntu budgie because ubuntu budgie's entry is "ubuntu" and when I mount the EFI partition and view the files, "ubuntu" exists but "Ubuntu" doesn't exist. When I try and delete "Ubuntu" via VisualBCD it just comes right back on next load up. Perhaps this could be a culprit in my issue?*Think

:)

 

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?

This was the BETA log collector when it was ran successfully on 8/1/2018
DESKTOP-9HEBUKS-(2018-08-01_19-50-52).zip

 

Troubleshooting the BETA log collector (extract > open)


This is the 7zip setting that must be deselected in order to run the BETA log collector:

 

Troubleshooting the BETA log collector (extract > open)


The problem seems to be the extract?
It use to work as there are five BETA log collector folders on the desktop.
There was another area to click extract which no longer appears like it use to.
Clicking on the extract in the image does not properly extract.
So far unable to use the beta log collector and had used it multiple times.

Any idea how to troubleshoot the beta log collector or the computer?
For the computer scannow, restorehealth all without integrity violations.