DISM.exe cannot restore health (open handle?)

I tried to to a Windows Update. There was an error 0x800f0922. I ran sfc /scannow and there were errors reported that according to sfc Windows could not repair.
The Windows update troubleshooter did not find any problems.

I ran dism.exe. It reported that "the component store is repairable". However, dism.exe /Online /Cleanup-image /Restorehealth reported an error 6815 and that "the handle has been invalidated by a transaction. The most likely cause is an open handle when the transaction ended or rolled back to savepoint."

I would appreciate some help on how to fix this problem.

Try DISM with a clean boot or with a Safe Boot (try Clean boot first - I'm unsure about how it works in Safe Mode :):
Clean: https://support.microsoft.com/en-us/...oot-in-windows
Safe: https://support.microsoft.com/en-us/...c-in-safe-mode

Thank you for the suggestion. Finally after reading some postings in Tenforums I followed the steps to do a repair-install of Windows with an in-place upgrade (link: Repair Install Windows 10 with an In-place Upgrade).

One of the two problematic Windows updates was fixed after the whole lengthy process, but the other one was not automatically updated and when I try to install it in Windows Update it ends with a message that "2019-07 Cumulative Update for .NET Framework 3.5, 4.8 for Windows 10 Version 1903 for x64 (KB4506991) - Error 0x80071a9f". I cannot find anything relevant about this error code. Even installing the update directly from the Windows updates catalog fails.

Try the .NET repair tool: https://www.microsoft.com/en-us/down....aspx?id=30135
If that doesn't work, uninstall .NET 4.8 and remove .NET 3.5 using the "Turn Windows Features on or off" in the left sidebar of appwiz.cpl

Did you try DISM w/a clean boot?

Hello, in your case I would try uninstalling .Net frameworks, if possible.

Here's one find on doing it:

How to remove and reinstall the Microsoft .NET Framework | AutoCAD | Autodesk Knowledge Network

That .Net framework repair tool: good idea!

More that might help:

4 Ways to Repair or Remove Microsoft .NET Framework • Raymond.CC

I tried Dism with a clean boot. The parameters that I mentioned earlier (

/Cleanup-image /Restorehealth) which I found on a website do not appear on the command line help for dism (dism /?). So I'm not sure if it worked correctly. Anyway, it reported the same error as before, that is "Error: 6815The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint."

Trying to uninstall .Net by disabling it in Windows Features does not work and I get an error about it.0x800F0922. There are instructions here https://support.microsoft.com/en-gb/help/2734782/net-framework-3-5-installation-error-0x800f0906-0x800f081f-0x800f0907, but I don't know where the .Net Framework installation files are located!

DISM should be run with this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

As for the installation files - Search the hard drive for a folder named "Sources" (without the quotes)
I only seem to have them in the Windows Kits folders (where I installed Debugging Tools and the ADK).
Dunno if that'll help.

Found v4.5 installation folders here (on my system): C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\ (there'll be other folders than the v8.1A - as I have multiple installed versions on my system)
Didn't find any install stuff for v3.5 - even though it's on my system (I suspect that's because it was a part of the original installation of Windows)

Thanks for the assistance.

I couldn't locate a Sources folder on my PC. I have a Microsoft.NET directory in C:\Windows with many subdirectories in but none of them is named "Sources".

- - - Updated - - -

Good news!

Although I didn't expect it the problem was caused by ReHIPS. I had it disabled, yet the problem with Windows Update persisted as I described earlier. After I uninstalled ReHIPS and did a Windows Update, I rebooted the computer and everything is in order.

Now, back to reinstalling reHIPS.

Good to know. Glad you located it!!!

FYI - when you install a program such as reHIPS, it installs drivers.
Drivers load when Windows starts. Then, after a bit, any that you have disabled are disabled - but they are still resident in memory. Although it's not very common, they can still cause problems even when they are disabled.