A company that does not know their suggested solutions have no chance in Hell of running on the computer they say it is designed to fix is not a company I am ever going to do business with ever again.
I am posting a solution found for own business laptop (HP 8540W & 8760W) so WebSearch engines index/register it in a few days - future sufferers come here and get a SOLUTION, finally. Disreagrd previous "experts" advises, they don't work 100% & pity on TechSupport folks who get HP paychecks yet don't know products their co. designs/manufactures (on deep Technical level):
Rerun BIOS updater, choose option for "Within Windows" or something to that effect (using HPQ/ROMpaq updater), rather than "create USB BootDisk on Key", this time it should work without the hassle of a BootDisk creation.
Should work from within Windows environment.
Notes:
a) Likely only one (1) service is responsible - namely "HP Software Framework" for HPQ Updater to fail, but doesn't hurt to reenable/restart both services.
I in fact am responding to other customers who elect to Update BIOS within Windows, perhaps oldfashioned but to me Boot Updater is more natural & always works regardless of WMI Support.
b) After done, don't forget:
**) Go BACK into Windows-->Services.msc & redisable both aforementioned Services if were originally disabled; or you're a computer Pro, you know what you're doing & like me keep all HP services disabled. The ones we got on EliteBook 8760W are pests consuming system resources, you just enable "Software Framework" when occasional issues emerge with HP softupdate (typically no issues) & redisable after use, rest of services are bloatware - some attempt to overrun Windows Wireless console, some seekout HP Networked printers (Ethernet, Wireless, but not USB), some do this & that - I study/know which one does what and decided to disable all. This is called a "minimalist" philosophy & turns your machine into a fast beast, I recently sold a very obsolete 4-year laptop which however handles 3DMCAD & complex designs/simulations, better new machines out fo a store, as new machines are loaded w/bloatware chocking down resources.
BUT nobody is requiring you to disable anything though.
The solution merely states the fact:
BELOW ARE IMPORTANT WARNINGS:
1) IF YOUR BIOS UPDATE STILL FAILS, SOME OTHER PIECE IN WMI SUPPORT IS MISSING - IN MY CASE WAS THESE 2 SERVICES, BUT THERE'S REMOTE POSSIBILITY SOMETHING ELSE MIGHT BLOCK UPDATER. DON'T WASTE TIME & CHOOSE "USB/BootDisk" options instead
2) Once BIOS updater does its job, will ask to auto-restart - let it go on & complete, it will self-shutdown (click "Next" to skip 60-second timer), then do NOT turn it on manually!, wait - it'll turn on by itself in 15 seconds, let it boot into Windows, you're done!
3) WARNING: close other apps before proceeding, be 100% sure your ACpower won't be interrupted or better yet - make sure battery is in/charged (so if ACpower accidentally disconnects, you're autoswitched onto battery) b/c power loss may result in severe damage to internal hardware. In the old days it'd result in fatal damage, these days powerloss would still result in a major repair (ROM chip corruption).
I had a Ubuntu/Windows 7 dual boot set up on my laptop. An updater tried to install Windows 10 in the middle of the night and now when I start the laptop, I get the grub rescue prompt. I tried this solution but ls into any partition gives me unknown filesystem.
I installed the boot-repair utility with a Live USB and ran a "Recommended Repair", which after a few minutes reported it had ran successfully but the grub prompt was there waiting for me when I restarted the laptop. Incidentally, most of the advanced options are grayed out. Here's the boot info summary.
You only want the syslinux boot loader as it is a Windows type boot loader that looks for more boot information in the partition with the boot flag. You do not want syslinux putting its additional boot data in the Windows partition, but want syslinux just to boot & pass boot to Windows code in the partition boot sector.
The BIOS update should take 5-10 minutes and there would be a splashscreen saying that the BIOS update is happening along with a progress bar. Afterwards, it should just reboot as normal. From what others have mentioned, if the BIOS updater has failed, it should spit out an error code.
I think OP should consider an in-place upgrade re-install, with all of her settings and programs saved, so no re-installs will be necessary. The system files and the drivers will revert to the standard ones MS used in the install.
@Wisewiz Hi. Unless they can boot their pc then an in-place repair cannot be done as this needs to be done with Windows running. It cannot be done within safe mode.
If they cannot boot the pc then a custom install is required. This will keep files but not programs/apps.
Thank you guys. At first Windows could be booted in safe mode. However was not respinding to clicks. After trying some stuff in commando prompt the user accounts were not accesable anymore. Ive manage to make a personal file backup disk with hp recovery manager. Now i believe the only way is a clean win install. Unfortunately. Since all of the programs and settings Will be gone. Only the blue Windows repair area is available with commando prompt eg but systems restores etc Wont work. All errors.
Yvi, I wish I had read your message before buying Pro in August 2023. I at the very least would have created a Windows 10 Restore Point, as I foolishly assumed the CCleaner Pro had a go back feature. Driver updater has destroyed my computer, for all practical purposes. Half the time on boot, I get a blue screen ("Please wait while we gather information to ignore.") Otherwise, BSOD's are unpredictable at any time. Especially if I happen to leave the computer on overnight. It's November now, but after several Windows 10 updates (my PC is not W11 compatible), it's still totally unreliable. What's more, I have auto renew turned on, although I don't remember opting for that, and I can't find a place to turn it off, so next August I'll have to contest a charge on my credit card. I've used CCleaner free version off and on for years. Pro is a huge disappointment. Yvi, I wish you the best, but I think you're worse off than I am. I would get a USB external hard drive holder and copy all my data to another computer, then start over with a new Windows install. Be sure you have all your user names, program installation keys, etc.
I don't particularly know about "borked" drivers being installed as has happened here though (I've only ran into that once with Intel iGPU drivers that corrupted a ton of stuff), so uninstalling those first may or may not help.
Hello everyone, i just read her post and it saved me from buying the Pro version although the price is very seducing..I might not do the update of a driver as its such a RISKY thing..Tho i'm having a problem with sound device..Thought it might help, but reading such feedbacks made me reconsider buying it.. but what about other features of Pro version? Like the Health Check and Software updater..Are they also RISKY? I have another such app for it..
I think you have to manually run the fwupdmgr command
sudo fwupdmgr refresh && sudo fwupdmgr get-updates will tell you what updates are available.
sudo fwupdmgr update will actually perform the update.
sudo fwupdmgr refresh ; sudo fwupdmgr get-updates and later on sudo fwupdmgr update. but I guess I broke something in my system because now I cannot access any of the Fedora kernels, and it gives this error.
Formatting/recreating EFI partition and reinstalling Fedora should have cleaned that up (so would removing windows files and regenerating grub config). After that, removing windows entry in UEFI setting should work.
[Impact]Some specific system (listed in upstream thread at -devel/2019-10/msg00104.html)Mostly ASUS systems, but also reported on some Dell systems.The affected systems are used to boot in UEFI mode and...
Why that happened after dbx update?
New entries filled some memory?
Something got blocked? You could compare hashes from dbxtool -l with find /boot/ -type f -exec sha256sum \; (for example using conditional formatting of duplicates in LibreOffice Calc).
I have been using CrapCleaner for over 20 years and never had a problem with it UNTIL I decided to the try the 14 day Professional version this morning and let the Driver Updater do its thing. As a result, I have a bricked desktop! The Windows Boot Manager says "...... Windows failed to start......". Booting into Safe Mode using F8 results in the same screen. Restore to a Previous Version results in the same screen. I have spent the last two hours researching online and have tried everything suggested and can't get past that same screen. This is a nightmare! Piriform should be held responsible for this disaster. I will never touch CrapCleaner again!
Same happened to me too. It took ages to run the Driver updater for the 5 drivers announced, next thing I see is that a new start was started (without my ok) and then a blue screen, which I couldn't get out of.
d3342ee215