“I can’t take a screenshot of the BIOS, UEFI, or boot screen” is frustrating when you need that image for troubleshooting. You were hoping the usual screenshot shortcut would work, but Windows hasn’t loaded yet. To enable virtualization in BIOS for troubleshooting, follow the steps for your specific hardware.
Fix #1: Photograph the physical screen
Use this method when you need to capture the actual PC’s firmware, boot logo, recovery screen, or startup error. Since Windows isn’t running, Windows + Shift + S and Print Screen can’t capture anything. For more information on capturing screenshots in Windows, visit the official Microsoft Windows 11 screenshot guide.
- Pause the screen if the firmware or boot tool supports it. Check the bottom or side of the display for a pause option.
- Lower the monitor brightness until text remains clear without glowing through the camera image.
- Hold your phone parallel to the screen. Moving farther back can reduce flicker and moiré patterns.
- Tap the screen text on your phone to set focus and exposure.
- Take several photos. Boot screens can disappear quickly, so keep the clearest image.
The result won’t look as clean as a software screenshot, but it records the real hardware screen. If reflections or flicker keep getting in the way, use a video capture device or reproduce the boot process in a virtual machine like VirtualBox.
Fix #2: Reproduce the boot screen in VirtualBox
A virtual machine runs bootable media inside a window on your Windows desktop. This lets the host PC capture the VM window even while the virtual machine is displaying BIOS, a bootloader, or recovery media. To learn more about using VirtualBox, watch this YouTube tutorial.
This approach works best for bootable ISO files and operating system installers. It won’t reproduce hardware-specific firmware errors from your physical PC. For help with troubleshooting USB device issues in Windows 11, refer to our guide.
- Download and install VirtualBox, then open Oracle VirtualBox Manager.
- Select New to create a virtual machine.
- Enter a descriptive name, such as
Boot Screenshot, and choose the operating system type that matches the bootable media.
- If VirtualBox detects an installer, choose the option to skip unattended installation. The wording or placement can vary by VirtualBox version.
- Continue to the hardware settings and assign enough memory for the boot environment. Follow the recommended range shown by VirtualBox if you aren’t sure.
- Create a virtual hard disk if you plan to install or repair an operating system inside the VM. If you only need to display bootable utility screens, choose the option that creates the VM without a virtual hard disk.
- Review the summary, then finish creating the virtual machine.
- Select the new VM, open Settings, and choose Storage.
- Select the virtual optical drive, choose the disk-file option, and attach your bootable ISO.
- Start the virtual machine. You should see the ISO’s startup or boot menu inside the VirtualBox window.
- Press
Windows + Shift + Son the host PC and drag over the VM window.
- Select the Snipping Tool notification, crop the image if needed, and save it.
This is usually the breakthrough when camera photos look grainy or show dark bands. The host captures the VirtualBox window as normal desktop content, so it doesn’t matter that the guest operating system hasn’t started. For more on sharing your screen in Microsoft Teams, visit our tutorial.
If the VM displays a blank screen, confirm that the ISO is bootable and remains attached to the virtual optical drive. A boot image built for different firmware or processor architecture may also fail to start. Check the official Microsoft documentation for more information on Windows system and recovery partitions.
Fix #3: Use a VM console or boot diagnostics
Cloud virtual machines and managed virtualization platforms often provide a browser-based console or boot-diagnostics page. These tools can capture startup errors before the guest operating system becomes usable. To get Windows 11 from the Insider Preview, follow our step-by-step guide.
- Open the management portal for the affected virtual machine.
- Select the VM and locate its console, boot-diagnostics, or startup-diagnostics area. The exact label depends on the platform.
- Start or restart the VM from the management portal.
- Wait for the console image to refresh. You should see the current boot stage or an error screen.
- Use the portal’s download or capture option when available. Otherwise, press
Windows + Shift + Sand capture the browser console.
A black or stale image usually means the display hasn’t initialized or the console hasn’t refreshed. Wait briefly, reload the diagnostic view, and restart the VM if the displayed image doesn’t change. For help with disabling or uninstalling Xbox Game Bar in Windows 11, refer to our guide.
Fix #4: Capture a server through remote management
Business-class servers can include an out-of-band management controller, which operates separately from Windows. Its remote console can show firmware checks, startup menus, and boot failures from another computer. To learn more about downloading Windows 11, visit the official Microsoft website.
- Open the server’s management address in a browser.
- Sign in with an authorized management account.
- Open the remote console or virtual console.
- Restart the server only if doing so won’t interrupt active work or services.
- Capture the required screen using the console’s image option or
Windows + Shift + S.
You should get a clean view of the server’s startup output without standing in front of the machine. If no remote-console option appears, check the server model’s documentation and management license.
When these methods don’t work
Some boot screens depend on the physical graphics adapter, firmware, or failing hardware and can’t be reproduced in a VM. Use a camera or external capture device for those screens. If a remote console remains blank through several restarts, check the server or virtualization platform’s display and boot-diagnostics settings before assuming Windows caused the failure. To pause, defer, or disable Windows updates in Windows 10 and 11, follow our step-by-step guide.
Conclusion
Fix #2, capturing bootable media inside VirtualBox, usually produces the cleanest screenshots and is worth the setup effort. For hardware-specific BIOS or UEFI failures, Fix #1 records what the PC actually displays; repeated blank screens or graphical corruption can point to a deeper firmware, display, or hardware problem. To clear the TPM chip in Windows 11, refer to our tutorial.
