Feel free to take the code and run it through Chat GPT, Gemini or any AI to verify the integrity of the code before running.
You might want to vibe code edit the code to work specifically the PC models you will be working with.
Note: Use this code at your own risk.
Open the Powershell with elevated privileges (run as administrator)
Use the blue button on the right to copy the code below.
Paste and in the Powershell window, and then tape enter
This script is usefull for pulling indepth information and the status of your computer.
However, it would be certainly worth running the full certs check, after step two, or when troubleshooting.
See full Gemini's description of the code, below.
Please review the Disclaimer Page & Explanation & user risk agreement before executing any scripts or utilising the code provided on this site.
Main menu contains scripts, disclaimers and documentation. Plus as a bonus, the code for embedded a copy text button into Google sites.
Enforces Privileges: The script checks if it is currently running with local administrator rights.
Auto-Relaunch: If it is not running as an admin, it automatically relaunches a new PowerShell window, bypasses execution policies, and requests administrative permissions via Windows User Account Control (UAC).
Visual Effects: Clears the console screen and prints a customized "Nexus System Hardware Integrity Orchestrator" splash screen.
Audio Cues: Plays retro-style motherboard frequency chimes ([Console]::Beep) to signal to the user that the workspace is loading and ready.
The script enters a continuous loop that displays a text-based user interface offering three distinct diagnostic actions, running until the user explicitly selects option 4 to exit:
Action 1: Live Hardware Audit Dashboard
Tests the physical NVRAM space on the motherboard by attempting a mock bcdedit configuration export to the temporary directory.
Queries system variables to check if the machine is booting via modern UEFI or legacy MBR/BIOS.
Checks the status of the Secure Boot framework and probes the hardware database (db) for the updated Windows UEFI CA 2023 certificate.
Checks the registry for active group policies (GPOs) that might be blocking configuration rollouts.
Interrogates the Trusted Platform Module (TPM) to determine its version (e.g., 1.2 vs 2.0) and checks if BitLocker drive encryption is active or suspended.
Action 2: Context-Aware Diagnosis & Action Plan
Evaluates whether the computer belongs to a corporate enterprise environment (checking for an Active Directory domain join or Microsoft Intune enrollment URLs) or is a standalone workgroup PC.
Assesses the hardware lifecycle based on the computer model name (specifically categorizing legacy vs. modern HP EliteOne/EliteBook generations).
Generates a step-by-step priority "Action Plan" instructing the user exactly how to remediate flags—such as updating firmware, switching to UEFI mode via MBR2GPT.exe, or manually suspending BitLocker protectors before flashing a BIOS update.
Action 3: System BIOS & Fleet Cross-Reference
Pulls the active BIOS version string, release date, vendor name, and system model via Windows Management Instrumentation (WMI/CIM).
Evaluates the local BIOS version against a built-in baseline compatibility matrix for HP corporate hardware to issue a hard Compliance Status ("PASS" vs. "OUTDATED").
Provides direct web links to the official HP driver repository and optional Windows Update channels so the administrator can source the correct firmware binaries.
The Exit Sequence: Once the exit option is chosen, the script kicks off an elaborate, stylized exit procedure.
Telemetry Simulation: It scrolls through ten distinct stages of "decommissioning data buffers" while emitting descending harmonic audio sweeps to simulate a hardware system powering down.
System Hardware Queries: To learn how the script interacts with motherboards using the commands built into this code, see Microsoft Learn: Get-CimInstance Cmdlet Documentation.
PowerShell Interface Controls: To understand how the text colors, loops, and terminal sounds are managed in administrative scripts, refer to Microsoft Learn: About Objects in PowerShell.