03-22-2020 08:08 PM
I recently upgraded my HP DeskPro 6200 MT to Windows 10 and decided to update the BIOS too.
It had the original J01 2.06 BIOS and I found on the HP Site version 2.33. Of course I downloaded it
and installed it.
The PC now takes 2-3 minutes to boot. And I was upset to discover someone else had this
issue and was told not to go past version 2.28!!!
Here is the solution from Paul
It is completely unacceptable that it should take this log to boot. Please tell me there is a way to go back to a previous
version. Why does HP provide V2.33 if its defective?????
Solved! Go to Solution.
03-22-2020 08:13 PM
The BIOS update is not defective.
It is only on W10 where that happens.
You have two choices...reinstall W10 in UEFI mode. Someone on the forum said that fixes the problem.
Or, if you don't use Bitlocker, you can hide the TPM device in the BIOS' security menu.
Restart the PC, then start tapping the ESC key until you are presented with the boot option menu.
From there, select SYSTEM SETUP.
Once inside SYSTEM SETUP, select SECURITY, inside that menu select DEVICE SECURITY.
Once inside that menu, select EMBEDDED SECURITY DEVICE ---> DEVICE AVAILABLE, change this setting to DEVICE HIDDEN.
Press F10 to save, and then go back in to double check it is HIDDEN.
Exit BIOS by saving all changes.
Rolling back the BIOS is definitely not an option.
03-22-2020 08:23 PM
I am blown away that you posted a reply so quickly. You're the best!!
I downloaded 2.28 and was able to downgrade as you mentioned
but that still didn't fix the problem. Again 2-3 minute boot times.
And I don't even get the screen that allows me to look at the BIOS!
I will try the other options you mention and let you know.
Out of curiosity, if 2.33 is not defective yet doesn't work with Windows 10,
who is it for? The FAQ says something about updated microcode but what's
Thanks again so much.
03-22-2020 09:08 PM - edited 03-22-2020 09:18 PM
You're very welcome.
I think the microcode update had something to do with processor security...some Intel security patch.
The 6200 Pro is not supported by HP for W10, which is why you don't see any drivers for it on the support page.
HP supports no PCs for W10 that were made prior to August of 2013.
The 6200 Pro was made in 2011.
If you read the list of supported operating systems for any of the 6200 Pro BIOS updates, you will not see W8/8.1 or W10.
The BIOS update can't be defective if you are not supposed to be running any OS newer than W8 on your model PC, according to HP.
So, when you install a BIOS update when running an unsupported operating system, anything can happen.
This problem is minor considering there are two ways you can fix it, or you can install W7.
Sometimes you end up with an expensive doorstop when you experiment with BIOS updates.
03-22-2020 09:27 PM
I really liked Windows 7 but with MS no longer supporting it I had to move to Win10.
As for the 6200, it cost me nothing. I got it from an company that had no use for it.
I put an i7-2600 in it (originally had an i3-2100) for $25, an additional
8GB of RAM for 16GB total (from 8GB) for $15 and a new 500Gb drive SSD drive for $60.
For $100 this PC still has YEARS ahead of it and is plenty fast. Boots from BIOS to Desktop
in about 8 seconds..
By the way, disabling the TPM solved my issue with V2.33.
No need to go back to 2.28 as I never use BitLocker anyways.
Thanks again Paul. Have a good night.
03-22-2020 09:41 PM - edited 03-22-2020 09:43 PM
Glad to have been of assistance.
I have two 8200 Elite CMT's with the i7-2600, 32 GB of memory, nVidia GT1030 graphics cards and 240 GB SSD's.
Both running W10 Pro with BIOS v02.28
I cannot justify buying a new PC, because these things run so well.
03-23-2020 10:13 AM
I decided this morning to try again and revert back to BIOS V2.28
but no luck. I tried with the HPQFlash utility (twice) and the DOS version
from the BIOS and neither worked. with the HPQ utility, it showed me
that its backing up the original BIOS then installing 2.28 then restarted the
PC but nothing happened during POST. Just launched Win10.
In the case of doing it from the BIOS, it finds the BIN file but when I select it, it does nothing.
I suspect you cannot revert back unfortunately. Any ideas?
03-23-2020 10:18 AM
You can't revert back. It may go through the motions, but that is all it will do.
If you look at the release notes for most of the BIOS updates including 02.33 they have this statement...
NOTE: Due to security changes, after loading this BIOS, older versions cannot be installed.
I highly recommend that you don't persist in trying to update the BIOS because you may eventually succeed in wrecking the PC.