Rob Woodruff's Powersdhell Script fails

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

jaybird

New member
Dec 22, 2021
2
4
In podcast SN905 Steve was extolling the virtues of Rob's powershell script, but when I attempt to run it under Win 10 pro I get:
PS D:\downloads> .\Analyze-LastPassVault.ps1
.\Analyze-LastPassVault.ps1 : File D:\downloads\Analyze-LastPassVault.ps1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\Analyze-LastPassVault.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: :)) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
Any ideas for a solution?
TIA
Jay
 
  • Like
Reactions: CredulousDane
You would need to allow script execution on your system. It seems to be currently disabled :)

The following PowerShell will allow executing signed scripts for the currently running PowerShell process only.
Code:
Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope Process
 
EdwinG's solution appears to be very helpful -- hope it works for the OP.

For anecdotal purposes only, Rob's powershell script worked for me -- also in Windows 10 Pro -- but I had only a full, satisfactory result when running it in Edge. I tried Chrome first, and the script ran fine. But when I got to the part where I needed to copy the xml, I couldn't find Show More or Copy at the bottom of the window. So I tried it again in Edge and was able to complete the process.

Thanks, Ron & Steve for this very useful tool!
 
You would need to allow script execution on your system. It seems to be currently disabled :)

The following PowerShell will allow executing signed scripts for the currently running PowerShell process only.
Code:
Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope Process
Yes, that's the solution. Thank You.
Jay
 
Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope Process
Please note, unless you have good reason, you should turn this off as soon as you're done. PowerShell these days is being used for malware purposes, and you probably want the extra security.

Code:
Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser
 
Please note, unless you have good reason, you should turn this off as soon as you're done. PowerShell these days is being used for malware purposes, and you probably want the extra security.

Code:
Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser
That's exactly why I put it to a scope of Process.

The second you close the window, it reverts to the system's execution policy. See: https://learn.microsoft.com/en-ca/p...id=ps-gethelp&viewFallbackFrom=powershell-7.1