-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Software and How To Questions
- HP BIOS Configuration Utility (BCU) 4.0.30.1 bug?

Create an account on the HP Community to personalize your profile and ask a question
05-14-2020 06:20 AM
Under Windows PE, BCU 4.0.30.1 was not able to set "Asset Tracking Number"
BCU 4.0.26.1 works fine!
Tested only with "HP EliteDesk 800 G2 DM 65W"
Command:
.\BiosConfigUtility64.exe /setvalue:"Asset Tracking Number","XXX01" /cspwdfile:"PWD.bin" /logpath:"E:\LEN\Set-AssetTag.log"
LOG:
2020/05/15 02:11:40.602868 | 1388|Setting|HP::Shared::StreamLog::StreamLog| Log Severity Level >= Info
2020/05/15 02:11:40.602868 | 1388|Info |HP::Shared::StreamLog::StreamLog| Begin.
2020/05/15 02:11:40.602868 | 1388|Info |BiosConfigUtility::InitInstance| *****************************************************
2020/05/15 02:11:40.602868 | 1388|Info |BiosConfigUtility::InitInstance| ** HP Bios Configuration Utility v. **
2020/05/15 02:11:40.602868 | 1388|Info |BiosConfigUtility::InitInstance| *****************************************************
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Platform: 8056 - HP EliteDesk 800 G2 DM 65W
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| BIOS version: 2.45 12/25/2019
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Manufacturer: HP
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Computer name: MININT-2VNVPUM
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Serial number: ************
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Unicode password supported: Yes
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| OS: Microsoft WinPE 64-bit
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| OS version: 10.0.18362
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| Command line: [.\BiosConfigUtility64.exe /setvalue:"Asset Tracking Number","XXX01" /cspwdfile:"PWD.bin" /logpath:"E:\LEN\Set-AssetTag.log"]
2020/05/15 02:11:51.569011 | 1388|Info |BiosConfigUtility::InitInstance| *****************************************************
2020/05/15 02:12:02.378976 | 1388|Info |biosconfig::Utils::ShowMessage| <SUCCESS msg="Successfully read password from file" />
2020/05/15 02:12:06.190577 | 1388|Error |biosconfig::Utils::ShowMessage| <ERROR msg="An operation failed" />
2020/05/15 02:12:06.190577 | 1388|Info |HP::Shared::StreamLog::~StreamLog| End.
Error From CMD Window:
<BIOSCONFIG Version="" Computername="MININT-2VNVPUM" Date="2020/05/15" Time="02:11:40" UTC="-21">
<SUCCESS msg="Successfully read password from file" />
<SETTING changeStatus="fail" name="Asset Tracking Number" returnCode="6">
<OLDVALUE><![CDATA[VV007766]]></OLDVALUE>
<VALUE><![CDATA[XXX01]]></VALUE>
</SETTING>
<ERROR msg="An operation failed" />
<ERROR msg="BCU return value" real="6" translated="6" />
</BIOSCONFIG>
05-14-2020 07:09 AM
Hello
according to https://ftp.hp.com/pub/caps-softpaq/cmit/whitepapers/BIOS_Configuration_Utility_User_Guide.pdf
Error code 6 means :
Access DeniedWMI result code – Setting modification failed due to BIOS permissions.
you you try the same command , with another BIOS setting . will it work or you still get an error ?
bye
05-14-2020 07:34 AM
Thank you for fast response.
Made another test with newest BCU and seems like same answer with every setting: /setvalue:"setting","value"
/set:"Filename" works, exported current settings and only changed "Asset Tracking Number".
05-14-2020 07:42 AM
Hello
in WinPE
if I well understood , it fails every setting using /setvalue:"setting","value"
it works if you use /set:"Filename".
I don't have any PC like yours, I could try , don't know when, with a 600 G1 DM or 800 G3 DM.
I have a WInPE base on 1903 or 1909 ( IHave to check) , in my WInPE I also added HP Powershell script libray and I'm able to run also HP cmdlet to change BIOS setting. Obvioulsy I wil l try BCU 4.0.30.1.
In any case , even if I will see the same issue , I'm not able to influence HP to fix it, but I could just add a second person having the same issue.
I'll update the post after my tests.
bye