Hphwdiaga.exe/hpdiags.exe runs in win 10 at boot time for NO valid reason

Topic

New Reply

Hphwdiaga.exe/hpdiags.exe runs in win 10 at boot time for NO valid reason as there are NO disk errors on my C drive.   Wastes 45 minutes to boot up.

Reply | Quote

Replies

Run MS Sysinternals Autoruns. It will show you everything that starts with your machine.
Search for HP diags and disable it.

cheers, Paul

Reply | Quote

lkeeno wrote:

for NO valid reason

Why no valid reason ? HP software checks for hardware problems on boot. It is part of HP Hardware Diagnostics Windows.

Our diagnostic tools are used to determine if your computer’s hardware is functioning properly. HP PC Hardware Diagnostics Windows come pre-installed on new HP computers

The HP PC Hardware Diagnostics Windows tool offers driver checks and updates on select components while also providing the ability to test the hardware components of your computer, quickly diagnoses hardware failures, streamlines support calls to HP, and can help avoid returns of working hardware. Supports Windows 10 and 11 Operating Systems..

Reply | Quote

Could be a recent driver update is causing Windows to crash into a power off state tather than shutting down properly, which would leave the file system dirty and cause the recovery options to engage.

Probably worth checking to see if any updates for your drivers or firmware have recently installed – it could be a transient issue caused by then being “out of step”. I’d also check with Crystaldiskinfo just to get a second opinion on the drive and maybe reseat all the connectors as the last bit of shutdown is fairly intensive, it could just be stressing something enough for a problem to show.

Specifically what I’m driving at is the sort of situation where you have a mechanical drive and Crystaldiskinfo notes “pending sectors”. These are ones which are set aside to be resolved as useable or bad when the drive next gets to trying the area. The thing is though the problem is detected and noted on the fly, it means the firmware on drive has to find somewhere it can stash that LBA of data and set the translation tables so the data still appears at the LBA Windows expects it to be located when the machine next powers up – all that before the power goes off – as the problem might be occurring as the drive clears it’s on board cache before going to low power. Could even be worth looking for drive firmware at the HP site.

Reply | Quote

If you do not need or want your HP Windows diagnostics utility you can uninstall them in the Settings>Apps section.

Look in the HP diagnostic settings dialog for unwanted options to disable.

The obnoxiously configured HP startup tasks can be disabled, the main diagnostics program will still work but your computer will be more responsive.

Autoruns is the most efficient solution, but here is another way without downloading a program to stop unwanted scheduled tasks:

Login as Administrator and open an elevated command prompt/PowerShell window as Administrator and type ‘taskschd.msc’, then look for all tasks labeled HP.

1 user thanked author for this post.

windbg

Reply | Quote

You might have to dive deeper depending on how the diagnostics are integrated as they can be bolted into the on disk recovery environment – though its also possible an errant Windows setting is firing them up..

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-tool-to-the-windows-re-boot-options-menu?view=windows-11

 

1 user thanked author for this post.

windbg

Reply | Quote

should anyone be interested..

had  a back burner thought on this one.

I’ve seen this before – some older BIOS implementations support EFI (and thus UEFI) but if they can’t resolve how to boot, or a boot device doesn’t perform in POST interrogation as the BIOS expects, the BIOS can assume the OS is “legacy” booting and revert to CSM for that boot , with the accompanying change in disk controller presentation.. which would upset Windows a bit. (the situation usually reverting to normal after repairs due to an inverted case of sod’s law as you can only see a fault when it’s present at observation)

So basically, I can only suggest you disconnect any optical drives and USB media (including card readers), set the BIOS to boot hard disk first and only, and see if the problem is resolved. Should that fix it work backwards adding removed devices and retesting…

Reply | Quote