• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
HP Recommended
HP Desktop 600 G3
Microsoft Windows 7 (64-bit)

I hope that you can help as I have read through the PDF that comes with the BCU and I can't get the BIOSConfigUtility.exe to work.

 

I have done the first stage and create the Config Text File " config\HP600g3.txt" but when I run the command within SCCM TS I am getting the following

 

 

Executing command line: Run command line InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
CreateProcess( NULL, (LPWSTR)m_sCommandLine.c_str(), NULL, NULL, TRUE, bNT ? CREATE_UNICODE_ENVIRONMENT : 0, m_pEnvironmentBlock, pszWorkingDir, &si, &pi ), HRESULT=80070134 (e:\nts_sccm_release\sms\framework\core\ccmcore\commandline.cpp,1019) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
CreateProcess failed. Code(0x80070134) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
Command line execution failed (80070134) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
clCommandLine.Execute( uOptions, pszWorkingDir, lpDesktop ), HRESULT=80070134 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\runcommandline.cpp,562) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
Failed to execute command line '"C:\_SMSTaskSequence\Packages\P01000D5\BIOSConfigUtility.exe"  /SetConfig:"config\HP600g3.txt" /verbose' .
The subsystem needed to support the image type is not present. (Error: 80070134; Source: Windows) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
ReleaseSource() for C:\_SMSTaskSequence\Packages\P01000D5. InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
reference count 1 for the source C:\_SMSTaskSequence\Packages\P01000D5 before releasing InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
Released the resolved source C:\_SMSTaskSequence\Packages\P01000D5 InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=80070134 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,372) InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
Install Software failed to run command line, hr=0x80070134 InstallSoftware 26/01/2018 11:48:34 1260 (0x04EC)
Process completed with exit code 2147942708 TSManager 26/01/2018 11:48:34 1116 (0x045C)
!--------------------------------------------------------------------------------------------! TSManager 26/01/2018 11:48:34 1116 (0x045C)
Failed to run the action: Set HP DeskPro 600 G3 Hardware.
The subsystem needed to support the image type is not present. (Error: 80070134; Source: Windows) TSManager 26/01/2018 11:48:34 1116 (0x045C)
MP server http://SERVERNAME.DOMAINNAME.local. Ports 80,443. CRL=false. TSManager 26/01/2018 11:48:34 1116 (0x045C)
Setting authenticator TSManager 26/01/2018 11:48:34 1116 (0x045C)
Set authenticator in transport TSManager 26/01/2018 11:48:34 1116 (0x045C)

 

I have even tried it with the black text file but I still get the same error.

 

looking at the PDF I see the below referance to a WMI class, but I don't see one within the BUC package

 

BCU requires HP custom WMI namespace and WMI classes (at the namespace root\HP\InstrumentedBIOS)

provided by BIOS. BCU will only support models with a WMI-compliant BIOS, which are most commercial HP

desktops, notebooks, and workstations.

Before running BCU, it is helpful to make sure that the HP BIOS WMI classes are in the namespace root\HP

\InstrumentedBIOS. When using BCU in WinPE, ensure that the WMI component is added to the boot image

using Microsoft® Deployment Image Servicing and Management (DISM) tool.

 

I look forward to you hearing from someone to whom can help

Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.