It accepts my choice for vPro, when branding (1 - to pick vPro, 9 - to finish with a little warning : this platform is in MPM lock state) but on the next reboot I still see 'machine is not in the committed state' and tool does not confirm the commit, shows the following: Repoaps DMI Tools.zip (3.55 MB, 4204 views)Īre there any updates to the latest version of this tool, having issues 'branding' the EliteBook 840 G3.

I can boot into FreeDOS just fine, but running NbDmiFit.Manufacture Programming Mode in Unlock mode MPM.zip (3.03 MB, 5763 views) In the BIOS, I have disabled Secure Boot and enabled Legacy Boot.ĥ. run 'dd' on FreeDOS.img instead of Rufus.exe to create a bootable USB media).Ĥ. A lot of instructions I've found thus far are for a Windows machine fixing this problem and I've had to adapt those instructions for Linux (e.g. It's an HP Elitebook running Ubuntu 18.04 LTS. I have an additional laptop that I'm using to help fix the PC.

As stated, only the System Board CT Number is missing from the BIOS.ģ. My desktop PC is an HP ENVY 750-437cb running Windows 10 Home (build 1903 or 1909, I don't remember which).Ģ. I'm hoping someone on here can help me fill in the gap of what I'm missing.ġ. This is the only Windows machine I have at home. I'm not so much concerned with WHY this happened as getting this fixed. I haven't updated the BIOS recently, and I haven't done Windows updates this week (and the PC has been rebooted several times since the last updates were applied). I'm not sure why this happened as I wasn't messing with the hardware of this pre-built machine at the time of the error. However, I don't think I'm even there yet since the error I'm receiving in the NbDmiFit script indicates I'm missing the necessary HPyyxxxx.exe file (If I understand the process correctly). I see references in this thread to unlocking the MPM, but I'm unfamiliar with that term so I assume I haven't done that. I have tried making a bootable FreeDOS USB drive and copied over the contents of NbDmiFit versions 2.09, 2.10, and 2.13 (each version was a separate attempt), all resulting in the same error message: 'Vendor code not supported in this package' This is my first go-around with an HP hardware issue of this nature, but I am a systems engineer by trade, so I'm not afraid of poking around. Going through the BIOS, I can see the SKU and Serial Number are still intact and I have the CT number recorded on a sticker inside the OEM case. I own an HP ENVY 750 that randomly lost its System Board CT Number. If I need to create a separate post, or post in another thread/area, please just let me know. I am struggling, but I feel this thread has information I need to put me on the right track.

Hp dmi tool nbdmifit