All Windows Troubleshooters will not open

[Hugger1]

Hi........

My problem is that none of the Window Troubleshooters will open or run.  When I click the "Run" button I get two quick brief flashes from the touchpad cursor, but nothing happens.  The original reason I had to use the troubleshooters is that I had trouble getting update KB5086672 -26200.8117 to install.  But I was able to get the update to install after I ran an In-place Upgrade.

I've tried a lot of suggested solutions, but nothing. as of yet. has brought the troubleshooters back to life.  In two days last week I tried the following suggested solutions from various sources:

Check Path for Temp Folder

Restart Cryptographic Service

Run SFC and DISM Scan

Run Disk Cleanup

Check Group Policy

Try to run Troubleshooters in Clean Boot State

Enable or Restart Required Services

Flush the DNS Cache and Reset the Winsock Catalog

Disable Third-Party Security Software and Firewalls

Rename the Catroot2 and SoftwareDistribution Folders

Modify TEMP and TMP Environment Variables

Enable Troubleshooters in Group Policy Editor

Performed an In-place Upgrade.

Used a System Restore Point.

It was suggested a few days ago that I run the Command Prompt as an administrator, execute the commands `regsvr32 /i mshtml.dll` and `regsvr32 /i shdocvw.dll` to re-register the system DLL files, then restart my computer.  It was also suggested to do a clean install.   So since yesterday I ran the administrator command prompt on each of those two commands and I got an error message along the lines of "The module 'mshml.dll' / 'shdocvw.dll was loaded but the entry point DllRegisterService was not found.  Make sure that 'mshml.dll' / 'shdocvw.dll is a valid DLL or OCX file and then try again."  So, no luck there.

So then I thought I'd have better luck with a clean installation.  Wrong again.  I attempted to do a clean install of Windows 11 using the latest Windows 11 media creation tool method  from Microsoft.   I only got so far and the installer stopped at a "Install driver to show hardware where to install Windows" error screen with no indication of what kind of driver is needed.

The couple of times I could get past the error message using the administrator command prompt (& no further) a screen popped up asking me what drive / partition I wanted to install Windows on.  That's not the strange part.  Below the question was a listing of the storage in the SSD drive and its partitions.   Now when I bought this laptop it had 512 Gb of storage available.  Now I was being told I had only 45 Gb on the SSD drive.

Does anyone have any thoughts on what I can try to fix this after all that i've tried?  It's just getting me more frustrated.  

[Venom21]

I suggest you to back your important data in external driver or pen driver and perform cloud factory reset.  Keep one bootable usb ready as reset may fails if windows files is corrupted. You have already tried many things. Trying solved it is just a waste of time. It's better do clean windows install and update. First do cloud factory reset from windows settings. If that fails, then do clean windows install using bootable usb.

[Hugger1]

Thanks for the suggestion VENOM21.   But I've already tried the cloud reset of Windows 11.   It worked up to a certain point.  I'll get into that a little farther along..

So, to keep the soap opera going..... I've had other suggestions.

Someone suggested  that I "Run Command Prompt as an administrator, execute the commands `regsvr32 /i mshtml.dll` and `regsvr32 /i shdocvw.dll` to re-register the system DLL files, then restart your computer."  I tried that and received  an error message along the lines of "The module 'mshml.dll' / 'shdocvw.dll was loaded but the entry point DllRegisterService was not found.  Make sure that 'mshml.dll' / 'shdocvw.dll is a valid DLL or OCX file and then try again."  So, I had no luck with that one.

So then I thought that I might have better luck with a clean installation.  Wrong again.  I attempted to do a clean install of Windows 11 using the latest Windows 11 media creation tool method  from Microsoft.  I only got so far and the installer stopped at a "Install driver to show hardware where to install Windows" error screen with no indication of what kind of driver is needed.  The couple of times I could get past the error message using the administrator command prompt (& no further) a screen popped up asking me what drive / partition I wanted to install Windows on.  That's not the strange part.  Below the question was a listing of the storage in the SSD drive and its partitions.  Now when I bought this laptop it had 512 Gb of storage available. Now I was being told I had only 45Gb on the SSD drive.

So, then I thought like you did VENOM21, I'd do a cloud factory reset.  It worked up to a certain point.  But all the troubleshooters will still not open or run.  but the laptop is back to 512Gb of storage

Therefore what I'm asking now is if anyone has any suggestions on how to deal with and clear out the error that says "Install driver to show hardware where to install Windows" error.   If I can get rid of that error message I'm more than willing to do a clean installation to get the laptop back to where it should be.

I've copied below some of the specs for the laptop, as I know from time to time that what brand, etc can have an effect on what the solution may be.

HP Laptop 15-dy2048ca (2L7J7UA)

Windows 11 Home 25H2 OS Build 26200.8117

Intel® Core™ i5 processor

Installed RAM 8.00 Gb

[Hugger1 · Accepted solution]

Hi again;

So after some digging, and a lot of pure luck, I finally found a solution to the troubleshooters on my HP laptop not opening or running.  It's not a total solution, but it will get you to where you can use the troubleshooters again.  I found it on another community forum, just by pure luck.  It wasn't there when I posted the question initially and it definitely wasn't there yesterday.  The solution is from July 2023, so it's about 3 years old.

The solution involves running the troubleshooters from a command line prompt.  I checked a few of them out and they work just fine.

The solution can be found at: https://www.kapilarya.com/run-troubleshooter-from-command-line-in-windows-11  .