Version 5.1 updates

Author: texhex

BCU-4.0.24.1/BIOS Configuration Utility User's Guide.url

@@ -26,7 +26,7 @@ param(
 
 
 #Script version
-$scriptversion = "5.0.6.BETA"
+$scriptversion = "5.1.0"
 
 #This script requires PowerShell 4.0 or higher 
 #requires -version 4.0

BCU-4.0.24.1/GetAllBiosSettings.bat

@@ -89,7 +89,7 @@ When starting BiosSledgehammer.ps1, the following will happen:
 * If the file **ME-Update.txt** is found, it is read and checked if a Management Engine (ME) firmware update is required. If so, the ME firmware files are locally copied and an update is performed. Any **.log* file generated by the update tool is attached to the BIOS Sledgehammer log file.  Finally, a restart is requested because the actual update is performed during POST. See [ME Update](#management-engine-me-update) for more details.
 * If the file **TPM-Update.txt** exists, it is read and checked if a TPM update is required. This happens by checking if the TPM specification version (1.2 or 2.0) or the TPM firmware are below the configured versions. If so, the TPM updates files are locally copied and executed. Any **.log* file generated by the update tool is attached to the BIOS Sledgehammer log file.  Finally, a restart is requested because the actual update is performed during POST. See [TPM Update](#tpm-update) for more details.
 * If the file **BIOS-Password.txt** is found, it is checked if the device is already set to use this password. The password is not specified directly (clear), but by using a *.bin file name that stores the password encrypted. If the passwords differ, the configured *.bin file is read from the [PwdFiles folder](#pwdfiles-folder) and the password is changed. See [BIOS Password](#bios-password) for more details.
-* If the file **BIOS-Settings.txt** exists, it is read and each entry is the name of a BIOS setting that needs to be changed. Each entry will be performed as single change (not all in a batch) to detect faulty settings more easily. See [BIOS Settings](#bios-settings) for more details.
+* If the file **BIOS-Settings.txt** exists, it is read and each entry is the name of a BIOS setting that needs to be changed. Each entry will be executed as a single change in the exact order they are defined; this makes detecting faulty settings (if any) easy. See [BIOS Settings](#bios-settings) for more details.
 
 Starting with Windows 10 1703, you can in-place convert from BIOS legacy (MBR) to UEFI boot mode (GPT); this is supported by BIOS Sledgehammer using the parameter ``-ActivateUEFIBoot``. This parameter will result in BIOS Sledgehammer only apply the BIOS settings defined in **Activate-UEFIBoot.txt**, which are one or two settings to change the boot mode to UEFI. Please see [In-place BIOS to UEFI boot mode conversion](#in-place-bios-to-uefi-boot-mode-conversion) for more details.