Intel exited the Desktop Boards business soon after the release of the 8 Series boards. Once the standard (3 year) warranty period was over, the support team was disbanded and all maintenance work on the BIOS was terminated. The update that you recently saw released was put together by an emergency response team as a result of some serious security issues being found in the Intel Management Engine (ME) firmware. No other parts of the firmware package (BIOS or otherwise) were updated in this process. Unfortunately, due to the business exit, no other type of issue will be considered just-cause to receive similar attention. Do not expect these issues that you are seeing to be fixed in the future; they will not.
It is certainly in the realm of possibility that the problems that you are seeing were introduced after the original production BIOS was released (i.e. were bug(s) introduced in some subsequent BIOS update(s)). Unfortunately, whether you will be able to back your way through these updates (and possibly locate one that doesn't exhibit the issue(s)) is going to be limited by the ME firmware. It simply may not allow you to go back beyond a certain point. If this is the case, you will have to stick with what workarounds you have in place.
My only suggestion is for you to investigate whether the use of (or disabling of, as the case may be) UEFI support makes a difference in boot order handling.
Hope this helps,
One of my coworkers figured out (about a year ago and didn't share until recently) that 142 still works, so I guess we are going to downgrade to 142. None of the other things I tried in the old thread really worked consistently. You can't even go to 142, then upgrade to 152 and have it work, so Intel must have broken something in between.
I knew they got rid of all their engineers and such, so I figured there must have been a pretty bad issue for them to release a new BIOS, especially this late after it was last updated. I was just hopeful they may have fixed the issue I was running into. That does happen sometime.
Back when I posted the original thread, they PCs were in classrooms and not really under my purview to push for a fix. Now that they are being redeployed to offices, we have to deal with what others never bothered to do. I guess we are fortunate that this guy figured out which version to go back to for the fix.
Anyway, if anyone is having issues with the boot order and boot devices on the DQ87PG, you can revert back to 142 without having to do a recovery BIOS install.
Intel is uncompromising when it comes to security issues. If a security issue is discovered, regardless of the pedigree of the systems, the production of a fix will be mandated. A few months back, a 3rd-party security expert discovered two security holes in the Management Engine (ME) interfaces. Updated ME firmware - for all versions of the ME ever produced - was developed and released.
So they went all the way back to 35s and 45s...
Too bad the didn't fix other lingering issues. It kind of makes it pointless in the 87 since it's boot order broke sometime between 142 & 148. Now I get to choose between not being able to choose my boot devices or closing some obscure security hole that we'll probably never have to deal with.
1 of 1 people found this helpful
Actually, they released the ME firmware update with an installer that is independent of the BIOS. This means that you can install whatever BIOS version you prefer and then install the updated ME firmware over top of the version installed with that BIOS. Bottom line, regardless of which BIOS version you prefer, you can have the fixes for the ME security issues.
I noticed that after a bit. I was thinking that you might be able to do that.