Windows Boot Toolkit: Open BIOS/UEFI, TPM & Secure Boot in Seconds

Stop wasting time clicking through Settings. This lightweight, transparent batch script lets you boot to BIOS, verify TPM 2.0, and check Secure Boot status with a single keypress.

If you've ever needed to get into BIOS on a Windows machine, you already know the frustration. Settings → Update & Security → Recovery → Advanced Startup → Restart Now → wait for a blue screen → hope you click the right option before the countdown expires. That's four clicks and thirty seconds on a good day — and considerably more when something is already broken.

I got tired of that workflow. So I built a tool to replace it. The Valley4Techs Boot Toolkit is a single Windows batch script — no installation, no third-party software, no admin portal — that puts every critical boot and system tool behind a single numbered menu. You run it as Administrator, press a key, and you're done.

In this guide, I'm going to walk you through exactly what the toolkit does, how each option works under the hood, when you'd actually reach for it, and how to customize it for your own setup. The .bat file is freely available — and by the end of this article, you'll understand every line of it.

I'm Mostafa Amaan, and on Valley4Techs I write practical tech guides built around real tools and real problems. Let's get into it.

Why Windows Buries Its Most Useful Tools (And Why That's a Problem)

Windows has excellent built-in utilities for managing your boot environment. The TPM management console, Secure Boot status check, boot configuration editor, BIOS version reader — they're all there, fully functional, and they've been there for years.

The problem is access. Every one of these tools lives a different number of clicks deep in the Settings tree, requires a separate command, or needs you to remember an obscure run dialog shortcut. Under normal circumstances, that's mildly annoying. During a troubleshooting session — when your machine is misbehaving, when you're trying to resolve a Windows 11 upgrade error at 11 PM, when a client is waiting — it becomes a genuine obstacle.

From my experience doing on-site IT support and system builds, the tools you need most urgently are always the ones buried deepest. BIOS restart. TPM check. Secure Boot status. Boot configuration. These come up constantly during Windows 11 migrations, dual-boot setups, and hardware troubleshooting. Having them all a single keypress away changes how fast you can work.

What Is a Batch Script (And Why You Should Trust This One)

A batch script ( .bat file) is a plain text file containing a sequence of Windows Command Prompt instructions. When you run it, Windows executes those instructions line by line — the same commands you could type yourself in a terminal, just automated.

The Valley4Techs Boot Toolkit is entirely transparent. You can open it in Notepad before running it and read every single line. Nothing is compiled, nothing is obfuscated, nothing contacts external servers. Every command it executes is a native Windows tool: shutdown, tpm.msc, bcdedit, wmic, msinfo32 — all built into Windows, all fully documented by Microsoft.

The Toolkit Menu at a Glance

When you run the toolkit as Administrator, you're greeted with a clean text menu on a green-on-black terminal. Here's everything available in version 1.0:

Nine functional options, each mapped to a native Windows tool or system command. No surprises, no hidden behavior — just the tools you already know, surfaced faster.

Option 1: Reboot Directly into BIOS / UEFI Firmware

This is the headline feature. Press [1] and the machine restarts directly into your BIOS/UEFI firmware settings — no key-mashing required, no missed timing, no going through the Windows recovery screen.

Under the hood, this runs a single command:

shutdown /r /fw /t 0

The /fw flag (firmware) is the key detail here. It tells Windows to boot directly into the UEFI firmware interface on the next restart. The /t 0 sets the delay to zero seconds, so it happens immediately.

The old method — Settings → Recovery → Advanced Startup — accomplishes the same thing eventually. This is just faster. On modern machines that POST in under two seconds, this is often the only reliable way to get into firmware without a USB drive trick.

Option 5: Check Secure Boot Status — True or False in Seconds

If you've been troubleshooting a Windows 11 upgrade error that complains about Secure Boot, this is your first stop. Option 5 runs a PowerShell cmdlet that returns one of two answers: True or False. No ambiguity.

powershell -Command "Confirm-SecureBootUEFI"

Since the toolkit is written as a Windows batch file, it executes this PowerShell cmdlet under the hood. A result of True means Secure Boot is enabled and functioning. A result of False means it's present but disabled — fixable in BIOS settings (use Option 1 to get there immediately). A CmdletNotSupportedException error means the hardware doesn't support Secure Boot at all, which points to a legacy BIOS machine.

The reason I built this check into the toolkit is that I've seen countless Windows 11 upgrade attempts fail because Secure Boot was disabled in firmware but nobody thought to check. Knowing the status before opening BIOS saves you from hunting through menus blindly.

Option 4: TPM Management — Your Windows 11 Compatibility Check

The TPM (Trusted Platform Module) requirement is the most common sticking point for Windows 11 upgrades. Option 4 opens the native Windows TPM Management Console — tpm.msc — directly. No navigating through Device Manager, no guessing at run dialog shortcuts.

What you'll see inside the console tells you everything you need to know:

• Status: The TPM is ready for use — you have a functioning TPM. Check the specification version (you need 2.0 for Windows 11).
• Compatible TPM cannot be found — either TPM is disabled in BIOS, or the hardware genuinely doesn't have one. Open BIOS settings next (Option 1) and check under Security settings.
• TPM is present but not initialized — this is uncommon but fixable. The console has a built-in wizard to initialize it.

Option 6: Check Your BIOS Version — Before Any Firmware Update

Before downloading a BIOS update from your motherboard manufacturer's website, you need to know what version you're currently running. Option 6 pulls this directly using WMIC:

powershell -Command "(Get-CimInstance Win32_BIOS).SMBIOSBIOSVersion"

Historically, IT guides used the command wmic bios get SMBIOSBIOSVersion. However, Microsoft has officially deprecated WMIC in Windows 11 and disabled it by default starting with version 24H2. To future-proof the toolkit, this version uses the PowerShell Get-CimInstance query shown above, which works flawlessly on modern Windows 11 versions.

The version string returned (e.g., F.70, 2.7.1, P1.40) matches exactly what you'll see on your manufacturer's download page. Compare the two, and you'll know in five seconds whether a firmware update is available or already applied.

This option has saved me from applying the wrong BIOS update on a client machine more than once. The five seconds it takes to check is a good habit before any firmware operation.

Option 7: Boot Configuration Data — Diagnose Dual-Boot and Startup Issues

Option 7 runs bcdedit — the Boot Configuration Data editor — and displays your complete boot setup. This is the tool you reach for when Windows isn't starting correctly, when a dual-boot setup stops showing the OS picker, or when you need to audit what's registered in the bootloader.

The output shows every boot entry on the machine: which operating systems are registered, their identifiers, the device and path each one points to, the timeout before auto-boot, and any recovery tools registered in the boot sequence.

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
timeout                 10

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11

For a dual-boot machine that's no longer showing the Linux option, this output will tell you immediately whether the Linux entry was removed (common after a Windows update rewrites the BCD) or simply needs its timeout adjusted. It's the starting point for any bootloader repair.

Options 2, 3, 8, and 9: The Supporting Cast

The remaining options are shortcuts to tools you likely already know, made faster to reach:

Option 2 — Advanced Startup Options opens the Windows Recovery settings page directly via the ms-settings:recovery URI. Useful when you want to boot into Safe Mode, reset the PC, or access the full Windows RE environment without using Option 1's immediate restart.

Option 3 — System Information launches msinfo32, the System Information window. This shows your full hardware summary: CPU, RAM, motherboard, BIOS version in detail, installed drivers, running services, and much more. I use this when building a documentation file for a new machine setup.

Option 8 — Disk Management opens diskmgmt.msc — the graphical disk and partition manager. Essential during OS installations, partition resizing, or diagnosing unallocated space issues.

Option 9 — Device Manager opens devmgmt.msc. First stop when a driver is misbehaving, a device isn't recognized, or you need to check hardware status after a major Windows update.

The Complete Batch Script Code

If you prefer to inspect and create the batch file manually on your system, you can copy the full code block below. Open Notepad, paste this code, and save the file with the name ValleyBootToolkit.bat. Make sure to set the file type to "All Files (*.*)" before saving.

@echo off
:: Check for Administrator Privileges
net session >nul 2>&1
if %errorlevel% neq 0 (
    echo [ERROR] This script must be run as Administrator.
    echo Please right-click this file and select 'Run as Administrator'.
    pause
    exit /b
)

:MENU
cls
color 0A
echo ============================================================
echo             Valley4Techs Boot Toolkit v1.1
echo ============================================================
echo  [1] Reboot into BIOS / UEFI Firmware (Save your work first!)
echo  [2] Open Advanced Startup Options
echo  [3] View System Information
echo  [4] Open TPM Management Console
echo  [5] Check Secure Boot Status (PowerShell)
echo  [6] Show BIOS Version (Modern query)
echo  [7] Show Boot Configuration Data (bcdedit)
echo  [8] Open Disk Management
echo  [9] Open Device Manager
echo  [10] Exit
echo ============================================================
set /p choice="Enter your choice (1-10): "

if "%choice%"=="1" goto BIOS
if "%choice%"=="2" goto ADVANCED
if "%choice%"=="3" goto SYSINFO
if "%choice%"=="4" goto TPM
if "%choice%"=="5" goto SECUREBOOT
if "%choice%"=="6" goto BIOSVER
if "%choice%"=="7" goto BCD
if "%choice%"=="8" goto DISK
if "%choice%"=="9" goto DEVMGMT
if "%choice%"=="10" exit /b
goto MENU

:BIOS
echo WARNING: Your system will restart immediately to firmware. Save all work!
pause
shutdown /r /fw /t 0
goto MENU

:ADVANCED
start ms-settings:recovery
goto RETURN

:SYSINFO
start msinfo32
goto RETURN

:TPM
start tpm.msc
goto RETURN

:SECUREBOOT
echo Checking Secure Boot Status...
powershell -NoProfile -ExecutionPolicy Bypass -Command "Confirm-SecureBootUEFI"
goto RETURN

:BIOSVER
echo Querying BIOS Version...
powershell -NoProfile -Command "(Get-CimInstance Win32_BIOS).SMBIOSBIOSVersion"
goto RETURN

:BCD
bcdedit
goto RETURN

:DISK
start diskmgmt.msc
goto RETURN

:DEVMGMT
start devmgmt.msc
goto RETURN

:RETURN
echo.
echo Press any key to return to the menu...
pause >nul
goto MENU

How to Download and Use the Valley4Techs Boot Toolkit

Setup takes about thirty seconds. Here's the exact process:

1. Download the file. Get the script directly using the download button below. It is a plain text file — you can open it in Notepad to review every line before running it.
   📥 Download Windows Boot Toolkit
2. Place it somewhere accessible. The Desktop works. A dedicated Tools folder is cleaner. A USB drive you carry for IT work is ideal — the file runs from any location on any Windows machine.
3. Right-click → Run as Administrator. This is required. The script's first action is checking for elevated privileges. If you double-click without admin rights, it will display an error and exit — it will not run with reduced permissions and fail silently.
4. Press the number for the option you want. The menu is self-explanatory. For most Windows 11 upgrade troubleshooting, the sequence is: 5 (Secure Boot) → 4 (TPM) → 1 (BIOS if needed).

How to Customize It for Your Own Workflow

The toolkit is structured as a series of labeled goto blocks in a batch script. Adding, removing, or modifying an option takes about ten minutes even if you've never written a batch script before.

Here's the structure of a single option — this is Option 3 (System Information) in its entirety:

:SYSINFO
start msinfo32
goto RETURN

That's it. Three lines. A label, the command, and a return to the menu. To add your own option — say, opening the Windows Firewall advanced settings — you'd:

1. Add a menu line: echo [A] Open Windows Firewall
2. Add a routing line: if /I "%choice%"=="A" goto FIREWALL
3. Add the handler block: :FIREWALL → wf.msc → goto RETURN

Other tools worth adding depending on your workflow: services.msc (Services), eventvwr.msc (Event Viewer), regedit (Registry Editor), or netplwiz (User Account management). Each one follows the exact same pattern.

3 Real Scenarios Where This Toolkit Saves You Time

Let me be concrete about when this actually matters, based on situations I encounter regularly.

Scenario 1: Windows 11 upgrade blocked by TPM/Secure Boot. You get the "This PC doesn't meet the minimum system requirements" error. Run the toolkit. Option 5 checks Secure Boot — False. Option 4 confirms TPM 2.0 is present but Secure Boot is off. Option 1 restarts directly into BIOS. You enable Secure Boot, save, reboot. Upgrade proceeds. Total time: under two minutes. Without the toolkit: clicking through Settings, guessing which BIOS screen to look at, probably one extra restart.

Scenario 2: Dual-boot stops showing OS picker after a Windows update. This is a classic — Windows updates occasionally overwrite the BCD and remove Linux entries. Option 7 shows you exactly what's registered in the bootloader. You can confirm whether the Linux entry is gone or just hidden, and know what repair command to run in your Linux recovery tool (typically boot-repair or manual efibootmgr work from a live USB).

Scenario 3: You're checking a used PC before buying or reselling. Option 6 shows the BIOS version — you can cross-reference with the manufacturer to see how up to date the firmware is. Option 3 opens System Information for a full hardware overview. Option 4 confirms TPM status before committing to a Windows 11 installation. You have a complete hardware assessment in under a minute.

Frequently Asked Questions

These are the questions I get asked most often about Windows boot tools and this toolkit specifically.

Final Thoughts

The Valley4Techs Boot Toolkit doesn't add capabilities to Windows — it removes friction. Every tool in the menu was already on your machine, already functional. The script just puts them all a keypress away and eliminates the Settings navigation you'd normally do under pressure, when something is already wrong.

For regular home users, it's a convenient shortcut. For IT professionals and system builders who open BIOS and check TPM status multiple times a week, it's a workflow change that adds up quickly. Keep it on your desktop, keep it on a USB drive, and make it part of your standard toolkit alongside the other tools you carry.

If you're building up your Windows troubleshooting knowledge more broadly, check out our BIOS vs UEFI differences guide — it explains the underlying technology behind Options 1 and 5 and helps you understand what you're looking at when you actually get into firmware settings. And if you're working on Windows 11 compatibility specifically, our Windows 11 setup guide covers the full upgrade and clean-install process from start to finish.