-
×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 Operating Systems and Recovery
- invalid feature byte-CRC failed

Create an account on the HP Community to personalize your profile and ask a question
04-24-2024 09:17 PM
It seems my featurebyte not working with a virgin motherboard which already accept to save serial,product,build id,CTnumber etc.
I tried uppercase-lower case combination, bios update but no luck
could any one have any idea on it
Feature byte=3Q3X476J6S6b757H7M7Q7W7m7s8uaBaEapaqauaw
ps: I copied it from partsurfer and it is matching with the sticker on body as well
04-25-2024 05:42 PM - edited 04-25-2024 06:28 PM
Hi @siva55
Welcome to the HP Forum.
it sounds like you replaced a HP MB.
I have no idea why you cannot add the required feature byte info to the BIOS.
You tried a BIOS update using the correct BIOS for your MB. Did you do this BIOS update within Windows?
The following suggestion is a long shot and the BIOS update you used would have to be a fairly recent version.
Try creating a HP USB BIOS Recovery flash drive within Windows on your PC, if operable, or on a different PC. Try to use, if possible, a recent HP BIOS update file for your MB.
Check this HP video on how to flash the BIOS outside of Windows using a HP USB BIOS recovery drive.
I can't say it will work but you never know.
You might also be able to add the required info using the Aptio V Firmware Update Utility at this Site if your MB has an AMI BIOS. This would be a second shot at this if you can't flash the BIOS outside of Windows.
Proceed at your own risk. A mistake when using Aptio could mess up the BIOS.
Or maybe a local PC Tech could get this done using an ISP Serial Programmer.
Opinions or troubleshooting suggestions in this response are provided independently. I am not employed by: HP, Inc. or the HP Forum.
Regards