Restorehealth Error 800F0915

Sir_George said:

concerned it may cause some problem if left in the current state. Do you know of any issues it may cause?

Click to expand...

I have not heard of any issues created as a result of /RestoreHealth failing.

If your system is running well, I would not be concerned.

However, if you do experience additional issues, your next step should be to do an in-place upgrade (repair install), which re-installs Windows without losing your apps, settings, and personal data.

Hey,hey,hey, A bit ago I decided to try a (Settings/Recovery/Reinstall-Now) repair install and MS must have fixed something because this time it fixed my DISM 0x800f0915 Restorehealth error on build 26300.9278. Last time I tried to run this it downloaded the experimental 26340.XXXX build and I had to cancel it but this time it just did a 26H2 restore. Imagine my surprise to see Restorehealth actually complete with no error this time. One thing I should point out is the reboot took a "looong" time with just a black screen showing for awhile. I started to worry for a bit but it eventually finished the install. Also as a side note it reinstalled Onedrive yet again which I promptly disabled and removed.

​

Ramesh Sharma said:

wmic runs from Recovery Drive in WinPE environment.

Click to expand...

Not on the latest build as it has been removed.
You must have an older build of recovery drive.

Sir_George said:

I have been trying to correct this for a few hours using ChatGPT and nothing has worked. Outside of trying to fix the problem, I was concerned it may cause some problem if left in the current state. Do you know of any issues it may cause?

Click to expand...

I went down all those rabbit holes a couple weeks back. We're just going to have to wait for Microsoft to fix this. Since a repair install doesn't change the symptoms, my feeling is that the component stack is fine, it's some other data that isn't replaced by a repair install that is causing the issue. SFC runs clean on mine, and three different sources for a repair install didn't fix it.

Don't beat your head against a wall trying to fix this, I've already done that for you!

gunrunnerjohn said:

I went down all those rabbit holes a couple weeks back. We're just going to have to wait for Microsoft to fix this. Since a repair install doesn't change the symptoms, my feeling is that the component stack is fine, it's some other data that isn't replaced by a repair install that is causing the issue. SFC runs clean on mine, and three different sources for a repair install didn't fix it.

Don't beat your head against a wall trying to fix this, I've already done that for you!

Click to expand...

Did you see my post above a bit ago?

On the Insider ISO's (ie. Windows11_InsiderPreview_Client_x64_en-us_26300_9212.iso), WMIC is gone from boot.wim.

Yeah, the end is happening all over the place.

FrancoDT said:

Did you see my post above a bit ago?

Click to expand...

Yep, if I get time I'll try the repair install one more time. OTOH, Windows is running fine, so maybe I'll just wait and see if MSC figures it out.

gunrunnerjohn said:

Yep, if I get time I'll try the repair install one more time. OTOH, Windows is running fine, so maybe I'll just wait and see if MSC figures it out.

Click to expand...

I'm thinking they fixed something as it actually worked this time and had an odd reboot.