My computer is a HP 15 Notebook PC, and I use Microsoft Windows 8.1 (64-bit). I recently received notice of a important update regarding an HP Notebook System BIOS Update (AMD Processors). I tried doing the update, but it seems to behave strangely. Creating a restore point, checking available space, connecting to HP servers, and the downloading itself are all marked with a green check, but when it goes to installing, after a few seconds of it, a gray X box shows up beside installing, and all I can do is click 'next', and it leaves. What am I supposed to do? Is this update supremely necessary to keep using my computer as is?
Here is a link to the HP Support Assistant if you need it. Just download and run the application and it will help with the software and drivers on your system that might need updating. This is the only way I would do updates as they are made for your HP Notebook.
I'm having an issue with an update. HP support assistant keeps prompting me to install an update on my HP Pavillion laptop with windows 10. The update is HP notebook system BIOS update (AMD Processors). I have downloaded and installed this update twice and nothing indicated that anything had gone wrong with the update. It went through all the steps without any issues at all. However HP support assistant keeps telling me that I need to do the same update. As I said I've done it already and it said it was successful so I dont understand why Support assistant keeps telling me I still need to do it. I would appreciate any help you could give me with this matter as I'm not 100% sure if the update was successful nor do I know how important it is if it wasn't successful.
Hey Bradley, there are a few known issues with the most recent BIOS updated being rolled out and it is not extremely important to have it installed (Just a few minor bug fixes). To disable HP support assistant from giving you constant notifications and to pause installation of updates, open HP support assistant and click on settings -
If you are having issues booting up after the update then shut down the pc and once it is off press the windows & B key together and then hit the power button - This will rollback the most recent update that is causing issues.
The issue you describe doesn't seem to be related to the Intel Management Engine on your system. First of all you want to make sure that your system is AMT capable, otherwise there is no ME present at all. In case your computer is AMT capable but if has never been provisioned for remote management then the ME is inactive thus not causing any kind of issues. Based on your description seems plausible your computer might have overheating issues making it to shut down around 30 mins to prevent damage. In this kind of cases you want to contact the laptop manufacturer support to get the hardware troubleshot and evaluate possible warranty replacements.
In regards to the AMT/ME I believe this laptop is capable due to the Core I5 vPro sticker. Now the interesting part is that I cannot find any trace of ME install in device manager under system devices.
You need to install the BIOS update (which should be latest available, BTW) in whatever BIOS Recovery Mode Lenovo supports/supported, This is necessary to support updating the ME Firmware when the ME is not running to assist.
Since I am not very familiar with the architecture of the Lenovo BIOSs or their updates, I really can't help you with this. Hopefully Lenovo will assist (though I am not getting my hopes up considering the age of this laptop).
I see the laptop is still running the W7 image, please update to the W10 licence you were using before; use the upgrade tool (click the 'Update Now' button) and you should retain the W10 digital licence you were using previously. Please alert me if the Windows version you are using is 32-bit - for the most reliable and replicable environment the 64-bit version is recommended. Version can be found at the Run box, (hold [WIN] key & hit [R] key), type winver and hit OK. Advice here.
For completeness' sake, before you do the update, please download the Intel SA-00086 Detection Tool (use the Major Geeks link provided below, select the second link below 'Download Now' - 'Download@MajorGeeks', the 'Download@AuthorsSite' link redirects to the CSME VDT and is not the correct tool for your system. Please post the output of the tool here.
All the bios updates Lenovo offers don't contain a configured (non- initialized) ME region but just the bios region, and the ME updates Lenovo offers contain only unconfigured update images. Since these updates are performed by the ME firmware itself they won't work if the the firmware is corrupted. So there's no help for your problem from Lenovo there.
Any error dialogs post back here (there may be one, but hopefully not) then when the system has restarted run the CSME Validation and Detection Tool once more. Hopefully it will be successful and the system should no longer shut down.
The updates triggered via Fwupdlcl are performed by the ME firmware itself. Fwupdlcl sends the new (unconfigured) firmware parts to the ME which then itself will run the update process This way one can update the code partitions of the ME firmware but not the data partitions. But the latter are most often the part which is corrupted.
Since there's no ME interface in device manager the win32 version of Fwupdlcl probably won't work even with updated drivers. There's still a DOS version of the tool, but because of the reasons already mentioned this probably won't work either.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
If the USB option is not showing in the boot menu that means you have to disable the secure boot and enable the CSM support in bios, that will enable the boot option in the boot menu. Here is a video tutorial as well: =PVlgCe1fAcw
I have a toshiba c655d-s5518, on that computer there is a jumper labeled xxx just above the DDR3 memory modules (towards battery), if you short the jumper while powering on it clears the BIOS password. on Some other C655D the jumper is labeled B500.
there are 2 pins next to either the ram or the cmos battery. mine was next to the ram. youll see them next to the ram all alone. turn the computer off. take a flathead scredriver and touch the two pins. hold it there while you power on the computer. the computer should turn on and then shut down. now power it on normally and the password should be gone. ive done this in a dozen c655 and c855s
pull out the bios ic name with winbond with 8 pins put it in the programmer download the bios file from toshiba webste extract the file there will be file with extension rom or bin try to make me picture i will guide you then programme the ic it will be claire i am very familiar with this
1. Starting with the computer fully off, turn it on by pressing and releasing the power button. Immediately and repeatedly tap the Esc key, until the message "Check system. Then press (F1) key" appears on the screen.
For some reasons it could happen that no PC Serial No. and Challenge Code will displayed instead of "Not Certified" appears. In this case remove the AC-adapter and the battery for a short time and try it again.
The BIOS in older PCs initializes and tests the system hardware components (power-on self-test or POST for short), and loads a boot loader from a mass storage device which then initializes a kernel. In the era of DOS, the BIOS provided BIOS interrupt calls for the keyboard, display, storage, and other input/output (I/O) devices that standardized an interface to application programs and the operating system. More recent operating systems do not use the BIOS interrupt calls after startup.[6]
Most BIOS implementations are specifically designed to work with a particular computer or motherboard model, by interfacing with various devices especially system chipset. Originally, BIOS firmware was stored in a ROM chip on the PC motherboard. In later computer systems, the BIOS contents are stored on flash memory so it can be rewritten without removing the chip from the motherboard. This allows easy, end-user updates to the BIOS firmware so new features can be added or bugs can be fixed, but it also creates a possibility for the computer to become infected with BIOS rootkits. Furthermore, a BIOS upgrade that fails could brick the motherboard.
The last version of Microsoft Windows to officially support running on PCs which use legacy BIOS firmware is Windows 10 as Windows 11 requires a UEFI-compliant system (except for IoT Enterprise editions of Windows 11 since version 24H2[7]).
Unified Extensible Firmware Interface (UEFI) is a successor to the legacy PC BIOS, aiming to address its technical limitations.[8] Since 2019, all PCs for Intel platforms no longer support Legacy BIOS.
The term BIOS (Basic Input/Output System) was created by Gary Kildall[9][10] and first appeared in the CP/M operating system in 1975,[4][5][10][11][12][13] describing the machine-specific part of CP/M loaded during boot time that interfaces directly with the hardware.[5] (A CP/M machine usually has only a simple boot loader in its ROM.)
Versions of MS-DOS, PC DOS or DR-DOS contain a file called variously "IO.SYS", "IBMBIO.COM", "IBMBIO.SYS", or "DRBIOS.SYS"; this file is known as the "DOS BIOS" (also known as the "DOS I/O System") and contains the lower-level hardware-specific part of the operating system. Together with the underlying hardware-specific but operating system-independent "System BIOS", which resides in ROM, it represents the analogue to the "CP/M BIOS".
With the introduction of PS/2 machines, IBM divided the System BIOS into real- and protected-mode portions. The real-mode portion was meant to provide backward compatibility with existing operating systems such as DOS, and therefore was named "CBIOS" (for "Compatibility BIOS"), whereas the "ABIOS" (for "Advanced BIOS") provided new interfaces specifically suited for multitasking operating systems such as OS/2.[14]
d3342ee215