BCU bricked 3 laptops

[HashBrowns]

So I am testing using HP's BCU tool to standardise settings across all our HP machines (170 so need to make use of client management tools) and everything was going ok.  I created a settings file from backing up existing models (mainly ProBook 450 G0 though to G5) and comparing the settings.  I noticed some have different settings which is to be expected as new features are introduced etc.  I wished to create one master config file that would cover all the models but since the manual states "By creating a configuration text file with only the setting you want to change, you can deploy it to all systems in the enterprise. If a particular system does not support the specified setting, it will be ignored." I didnt worry about a specific setting not being supported on a particular model.I tested on a couple of machines in the lab and it worked without a hitch.  Simply ignored settings with a warning in the log as expected.  So I ran it on my group of "Targeted production users" yesterday.  All seemed ok, until this morning when they turned on their laptops and all 3 ProBook 450 G3's were bricked.  Symptoms are: 

1. When powering on,  Light is white on power button
2. "Wifi" button is oranage and "Mute" button is white
3. No display on screen at any point or on VGA output
4. No beeps or no diagnostic LED on CAPs lock key. 
5. After about 15 secs the fan on the CPU comes on full power.

Went through the various troubleshooting of:

1. Remove power and battery - press and hold power button to clear power
2. Attempt BIOS recovery in crisis mode by using USB drive with BIOS installed and using "windows-B" to initiate BIOS recovery
3. Disassemable laptop (could you make it any more difficult to access the battery!!) and remove BIOS battery to try to clear settings

None of the above worked.So opened a support case with HP.  Of course the laptop is out of warranty so am advised that it is a £342 cost for repair.   Now I understand that warranties can't last forever and HP can't continue supporting old machines but I dont believe this is reasonable in this case.  The issue is caused by BCU but I cant open a support case against BCU, so I have to use the serial of 1 of the 3 laptops and all the warranties are up.  I would consider paying the money if I could get to the root of the issue with BCU but I am not paying just for a new motherboard for 1 of the laptops and then be back to square 1 with my BCU issue.  Right now I dare not use it again.  How is it possible that configuring settings over the network can completely brick a laptop??  This is ridiculous.   I am almost certain the fault is reproducible but for obvious reasons, I dont want to try.

Now unfortunately I can not tell you what version BIOS was running on the G3's as I can no longer check that info. I know it wasnt the most up-to-date release though as I am also in the process of testing SSM to update BIOS and drivers but hadnt run this yet against these machines.  I am running the latest version of BCU 4.0.25.1 and it was running on Windows 10 x64 build 1803.  

Here is the REPSET file I used to change the settings.

BIOSConfig 1.0
;
Ownership Tag
	London Square Developments Ltd
Prompt for Admin password on F9 (Boot Menu)
	Disable
	*Enable
Prompt for Admin password on F11 (System Recovery)
	Disable
	*Enable
Prompt for Admin password on F12 (Network Boot)
	Disable
	*Enable
Password Prompt On F9 & F12
	*Disable
	Enable
NumLock on at boot
	Disable
	*Enable
Fast Boot
	Disable
	*Enable
Floppy boot
	*Disable
	Enable
CD-ROM Boot
	*Disable
	Enable	
USB Storage Boot
	*Disable
	Enable
USB device boot
	*Disable
	Enable
SD Card boot
	*Disable
	Enable
Network (PXE) Boot
	Disable
	*Enable
Legacy Boot Options
	*Disable
	Enable
Boot Mode
	Legacy
	UEFI Hybrid (With CSM)
	*UEFI Native (Without CSM)
UEFI Boot Options
	Disable
	*Enable
Configure Legacy Support and Secure Boot
	Legacy Support Enable and Secure Boot Disable
	*Legacy Support Disable and Secure Boot Enable
	Legacy Support Disable and Secure Boot Disable
SecureBoot
	Disable
	*Enable
Wake On LAN
	Disabled
	Boot to Network
	*Boot to Hard Drive
LAN / WLAN Auto Switching
	*Disabled
	Enabled
Virtualization Technology (VTx)
	Disable
	*Enable
Virtualization Technology for Directed I/O (VTd)
	Disable
	*Enable
Trusted Execution Technology (TXT)
	Disable
	*Enable
Update BIOS via Network
	Disable
	*Enable
Launch Hotkeys without Fn Keypress
	*Disabled
	Enabled
Wireless Manageability
	Disable
	*Enable
System Management Command
	Disable
	*Enable
TPM Device
	Hidden
	*Available
TPM State
	Disable
	*Enable
Reset of TPM from OS
	*Disable
	Enable
OS Management of TPM
	Disable
	*Enable
Clear TPM
	*No
	On next boot
TPM Activation Policy
	F1 to Boot
	Allow user to reject
	*No prompts
OS management of Embedded Security Device
	*Enable
	Disable