Initial System Configuration
To enable Secure Boot on the MSI MPG Z390 Gaming Plus, enter the BIOS by pressing the Delete key during system startup, navigate to the "Settings" tab, select "Advanced," then "Windows OS Configuration," and toggle the Secure Boot setting to "Enabled." Ensure your system is in UEFI mode beforehand.
- Access the BIOS by tapping the Delete key immediately after powering on your PC.
- Secure Boot requires your system storage to be formatted with the GPT partition style.
- The Windows OS Configuration menu houses the specific toggle for Secure Boot activation.
- Always save and exit the BIOS using the F10 key to apply your security changes.
Understanding NVRAM and Boot Priority
BIOS settings persist in non-volatile memory, but the Windows OS Configuration is essentially a wrapper for specific variable flags. When you commit these changes, the UEFI firmware writes to its internal NVRAM to store the Secure Boot state. If you toggle this without configuring the boot order properly, the system may default to an unintended device. Verify your boot priority within the BIOS prior to exiting to ensure the primary drive remains the target. Neglecting this order creates an environment where the system attempts to boot from peripherals, bypassing the security handshake you just enabled.
The actual mechanism involves the firmware checking the signature of the bootloader against a database of authorized keys stored in the motherboard. This process happens during the initial milliseconds of power-on before the Windows kernel initiates its own loader. If the firmware finds no match for the signatures, it halts the boot process entirely to prevent unauthorized code execution. You should monitor the diagnostic indicators on the motherboard if the system hangs here. A warning light signifies that the diagnostic check failed, pointing you back to the firmware menu.
Verifying Drive Partition Style
Before modifying motherboard firmware settings, confirm your primary drive uses the correct partition scheme. Secure Boot mandates a Unified Extensible Firmware Interface (UEFI) environment, which strictly requires the GUID Partition Table (GPT) format rather than the legacy Master Boot Record (MBR).
You can check this within the Windows Disk Management utility. Right-click the Start button, select Disk Management, right-click your system disk (usually Disk 0), and choose Properties. Under the Volumes tab, verify the Partition style is listed as GPT. If your drive is MBR, converting it requires reformatting, which will erase all existing data on the drive. It is critical to ensure your drive is formatted with the GUID Partition Table (GPT) before proceeding to avoid boot failures.
Advanced Disk Verification Methods
Disk Management is the standard tool, but command line utilities offer a more granular view for complex storage setups. Using Diskpart requires higher administrative privileges but provides immediate confirmation of the Partition Table type for every attached drive. If you type the list disk command, look for an asterisk in the GPT column for your primary boot device. Any disk lacking this asterisk relies on the older partition scheme that the UEFI environment cannot use for a secure launch. This check is crucial for multi-drive configurations where the OS might be installed on a secondary volume.
Converting your drive architecture introduces risks to existing boot sectors and partitions if performed incorrectly. Windows provides the MBR2GPT tool, yet this utility necessitates a specific command-line environment to execute without damaging the file system. You must run this verification before enabling any firmware security feature to avoid locking yourself out of your own data. Relying on Disk Management alone might obscure complex hidden partitions that require manual identification. Always backup the complete partition structure before attempting any structural changes to the storage medium.
Accessing the MSI BIOS Interface
The MSI Click BIOS interface provides a graphical environment for hardware management. Power on your computer and look for the manufacturer logo splash screen. As the system initializes, repeatedly tap the Delete key until the BIOS screen appears.
Keep a spare USB keyboard connected to a rear I/O port if your primary keyboard is not detected during the initial POST phase.
If the system boots directly into your operating system, restart and try tapping the key more rhythmically as the power cycles. Once inside, you may need to press F7 to switch from the EZ Mode interface to the Advanced Mode, which provides the necessary granular control over security settings.
Input Timing and BIOS Stability
Timing the key press remains a point of contention for many users, as modern initialization happens rapidly. Many systems initialize USB controllers only after the splash screen appears, which can delay keyboard registration. If you find your attempts failing, try plugging the keyboard into a USB 2.0 port rather than a USB 3.1 port to increase compatibility. These older ports often initialize sooner during the power-on sequence than their faster counterparts. Waiting for the system to fully cycle allows the firmware to establish a stable communication bridge with your input hardware.
EZ Mode offers a simplified view, but it intentionally hides the deeper security parameters to protect novice users from configuration errors. Switching to Advanced Mode grants you access to the specific tree of menus needed for security, but also requires care. You should avoid modifying settings you do not recognize, as the Z390 chipset supports many complex memory and CPU timing configurations. Navigating these menus requires patience, as the interface relies on accurate mouse or keyboard polling. Misclicks in this mode can easily lead to instability, so apply changes systematically and one at a time.
Configuring UEFI Mode
Secure Boot cannot function if the motherboard is configured in Legacy or CSM mode. The Compatibility Support Module (CSM) is designed to support older operating systems and hardware, but it conflicts with the security requirements of modern firmware standards. Navigate to the Settings tab, select Advanced, then enter the Boot menu.
Inside the Boot menu, find the BIOS UEFI/CSM Mode setting. You must set this to UEFI to properly initiate the security handshake required for Secure Boot. If you previously had CSM enabled, ensure you save your changes before attempting to locate the Secure Boot toggle. You must disable the Compatibility Support Module (CSM) to satisfy the requirements for modern operating system security features.
CSM and Modern Hardware Compatibility
CSM acts as a bridge for legacy BIOS hardware, but its presence creates a conflict with the UEFI variable store. When CSM is active, the system essentially emulates an old-fashioned environment that lacks the capacity for cryptographic signature verification. Disabling this module is a fundamental step that forces the motherboard to interact directly with the modern GPT-based boot partition. You cannot enable security features while this emulation layer remains present. The firmware must operate in a pure UEFI state to authenticate the software signature chain during startup.
Changing the UEFI/CSM mode often triggers an automatic reconfiguration of the boot order. Once you save the settings and exit the BIOS, the system will verify the new environment against your installed hardware. If your graphics card or peripheral hardware lacks a UEFI-compatible GOP driver, the screen might remain black after you disable CSM. You must ensure your GPU supports UEFI mode before committing to this change. If the monitor signal drops, the hardware incompatibility usually stems from the video output rather than the motherboard firmware itself.
Locating Windows OS Configuration
Once the system is set to UEFI mode, the specific security toggles become accessible. From the main Advanced tab within the BIOS, look for the entry labeled "Windows OS Configuration." This sub-menu contains settings specific to operating system behavior and security protocols.
Within this menu, you will find settings related to TPM (Trusted Platform Module) and Secure Boot. This area is the primary location for managing your firmware security posture. Users often mistake the general security tab for the OS configuration, but for this specific board, you must locate the Windows OS Configuration tab to find the Secure Boot switch.
TPM Interaction and Security Toggles
The Windows OS Configuration sub-menu holds the keys to the interaction between the motherboard and the operating system security features. While Secure Boot is a distinct toggle, it is closely linked to the status of the Platform Trust Technology or the TPM module. Enabling Secure Boot without addressing the TPM setting can lead to incomplete security compliance within the operating system. You should scan this menu for any secondary toggles that might influence the security handshake. This area serves as the command center for all firmware-based operating system hardening.
Users occasionally overlook the significance of these granular settings, focusing only on the primary switch. Each toggle within this section communicates a specific instruction to the motherboard firmware regarding how to handle the OS loading sequence. You might find extra options here for specific key management that are not immediately obvious. These deeper parameters allow for fine-tuning the security posture based on your specific requirements. Always verify that each active toggle aligns with your security goals before exiting the interface.
Enabling Secure Boot and Managing Keys
With the Windows OS Configuration menu open, look for the "Secure Boot" entry. By default, this may be set to "Disabled" or "Standard." Change the Secure Boot setting to "Enabled." If the option is greyed out, verify that you have successfully saved the change to UEFI mode and rebooted the system before returning to this menu.
You may also see an option for "Secure Boot Mode," which allows you to toggle between Standard and Custom. For most users, the Standard mode is appropriate, as it uses the default keys provided by the motherboard manufacturer. Once you toggle Secure Boot to Enabled, the system will verify the signature of the bootloader during startup.
Secure Boot acts as a gatekeeper, verifying that only digitally signed, trusted software is executed by the firmware during the boot process.
Standard Mode vs Custom Key Enrollment
Standard mode leverages the factory-provided keys, which are pre-signed by the motherboard manufacturer for trusted hardware vendors. Custom mode, conversely, allows for the manual enrollment of platform keys, which is generally reserved for advanced users who require specific signing certificates. Selecting Custom mode without the proper keys will prevent the machine from finding a valid bootloader, effectively blocking the boot process. Stick to the Standard mode unless you have a specific, expert-level requirement to modify the key database. Most consumer use cases remain stable under the provided default keys.
The verification process initiates a cryptographic handshake between the UEFI and the bootloader files. If the firmware detects any unauthorized modifications to the bootloader signature, it will block execution immediately. This gatekeeper function operates silently until a signature mismatch occurs. If a mismatch does trigger a block, the screen will likely display a notification about an invalid security signature. Understanding this interaction explains why the system behaves differently during the initialization phase when Secure Boot is active.
Verifying Status in Windows
After saving your changes and rebooting, the system should load the operating system normally. To confirm that the firmware changes were applied, use the built-in system tools rather than relying solely on the BIOS display.
Press the Windows key + R, type "msinfo32," and press Enter. This command opens the System Information window. In the System Summary pane, scroll down until you find the "Secure Boot State" entry. It should read "On." If it reads "Unsupported" or "Off," check the System Summary to ensure your BIOS mode is also listed as UEFI, as a conflict here often points to a remaining CSM/Legacy setting.
Cross-Referencing Logs and System Data
While the System Information tool provides a quick overview, it does not detail the specific cause if the status is reported as off. You should cross-reference this information with the Event Viewer to look for specific errors related to the boot sequence. Navigating to the System logs will reveal any issues that occurred during the initialization of the secure boot services. These logs capture the handshake attempts that happen between the firmware and the kernel. If the status remains off despite correct BIOS settings, these logs provide the evidence needed to diagnose the underlying cause.
The msinfo32 utility reads the current state from the Windows Registry, which pulls its data from the BIOS variables upon boot. If the registry fails to sync these variables correctly, the tool might present inaccurate information. Refreshing the System Information panel can sometimes resolve discrepancies if the OS has recently resumed from sleep. Should the report continue to contradict the BIOS status, verify the kernel logs for any persistent security warnings. A discrepancy here usually indicates that the Windows boot manager encountered a conflict during the transition into the protected environment.
Troubleshooting Boot Configuration
If your system fails to boot after enabling these settings, it is likely due to a partition style conflict or a legacy driver that cannot load in a pure UEFI environment. Do not panic; the BIOS remains accessible. Restart the machine and re-enter the BIOS using the Delete key.
If the system fails to post after changing BIOS settings, you can force a reset by removing the CMOS battery for thirty seconds.
If you cannot enter the BIOS because of a black screen, you may need to clear the CMOS to restore factory defaults. Use the JBAT1 jumper located on the motherboard, or physically remove the CR2032 battery for approximately thirty seconds while the power supply is unplugged, then reseat it to reset the configuration.
Forcing Hardware Defaults
Clearing the CMOS physically resets the motherboard to its default factory state, which is far more comprehensive than any internal software reset. This procedure is your last line of defense when the firmware becomes unresponsive or fails to display a video output. You must remember to remove the power cable completely before attempting to bridge the pins or remove the battery. Providing power to the board while the battery is removed may prevent the capacitors from discharging completely. After the reset, you will have to re-enter the BIOS to reconfigure every setting you had previously established.
When the system fails to post after a change, do not assume hardware failure immediately. A simple configuration mismatch often prevents the board from completing its initialization, manifesting as a black screen. Removing the battery forces the firmware to reload its base code, effectively clearing out the conflicting settings. Keep a record of your hardware configuration on a separate device, as the reset will erase custom overclock profiles or memory timings. Once the firmware is back to its factory default state, you can begin the configuration process again with a clean slate.
Advanced BIOS Maintenance
Maintaining your motherboard firmware ensures compatibility with newer security standards and hardware revisions. If you encounter persistent issues with Secure Boot not working, check if a firmware update is available on the official MSI support page for your specific board model.
Updating the BIOS can resolve issues where the TPM module is not detected or where Secure Boot fails to initialize correctly. Always follow the manufacturer's specific instructions for the M-Flash utility to safely update your system. It is highly recommended that you flash your motherboard firmware to the latest revision to maintain optimal hardware interoperability.
Firmware Flash Integrity
The M-Flash utility operates within a dedicated environment that does not rely on the operating system for stability. You should always use a clean, FAT32-formatted flash drive to minimize the risk of data corruption during the update process. If the utility reports an error during the flash, do not restart or power down the system under any circumstances. A partial flash update can leave the BIOS chip in a state that requires professional recovery or hardware replacement. Ensure the system remains connected to a stable power source throughout the entire duration of the firmware writing process.
Firmware updates often include subtle optimizations that improve communication with storage controllers and modern CPU architectures. You might see better stability during the boot process or faster recognition of peripherals after installing the latest revision. MSI provides a version history on their site that details the specific fixes included in each update. You should review these notes to see if a particular update addresses the exact issue you are encountering with your configuration. Regular maintenance of the BIOS remains the best method for ensuring long-term compatibility with evolving software and hardware standards.
