[SOLVED] Windows Update, SFC & DISM not working and booting takes minutes, Windows 10 Pro 22H2 x64 (10.0.19045.2965)

BikeHelmet

New member
Joined
Apr 19, 2025
Posts
2
Hi,

We've got a computer at our office with exactly the same problem as this thread: (Running Win10 Pro v22H2 x64 (10.0.19045.2965))

Fixes tried:

sfc /scannow - Error “Windows Resource Protection could not start the repair service.”
DISM /Online /Cleanup-Image /RestoreHealth - Error "0x80004002 No such interface supported"
Tried both of these with Safe Mode as well but got the same result
SFC and DISM from Windows Recovery with multiple different ISO (matching the Windows version and edition) - SFC showed that there are corrupt files but couldn't be fixed and DISM couldn't find the corruption
In place upgrade - which ends up just failing when reaching around 70% with message "Installer couldn't finish"
An upgrade to Windows 11, which also fails and rolls back, leaving an unbootable Win11 in the boot menu.
Farbar Recovery Scan (without any fix lists) - which showed no errors/corruptions
The SFCFIX tool from sysnative (without any fix lists) - which showed no errors/corruptions
SFCFIX using the fixlist from the above thread, which had no success either.
Windows Defender full scan and offline scan - nothing found
Malwarebytes full scan - nothing found
I do have System Restore points, but they don't go back far enough (I am guessing due to the windows version, whatever went wrong happened in early 2024 or late 2023 and went unnoticed until now, when updating Microsoft Office failed.) Also, system restore closes instantly. (No error message.) The instant close happens in both Windows and the Recovery Environment.


Additional observations:
The Installed Updates screen reports nothing.

At this point I'm at a loss for what's wrong. I compared the services list to another functional computer, and it seemed normal. If anyone has any suggestions, I'm all ears. Cheers.
 

Attachments

  • image_2025-04-19_134512559.webp
    image_2025-04-19_134512559.webp
    22.1 KB · Views: 1
  • image_2025-04-19_135215433.webp
    image_2025-04-19_135215433.webp
    30.6 KB · Views: 1
  • ComponentsScanner.txt
    ComponentsScanner.txt
    1.4 KB · Views: 2
  • CBS.zip
    CBS.zip
    632.5 KB · Views: 1
  • image_2025-04-19_140120175.webp
    image_2025-04-19_140120175.webp
    7 KB · Views: 1
Last edited:
Hi @BikeHelmet,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi and welcome to Sysnative,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi Maxstar,

We got around the problem with some manual effort. Being partially incapacitated (No Microsoft Office) was causing trouble. On Wednesday we found an old backup from 2023 made with third party backup software, and on Thursday we decided to restore it after backing up our files, email and other stuff. We then spent part of yesterday and today reinstalling and reconfiguring software (which had changed over the past 2 years) to get roughly to where we were, but with healthy system files. I don't think I can try your Fixlist now due to that. I appreciate the response though. It may have done it, but we got impatient and went the manual route!

Thank you though. This Fixlist is for v10.0.19045.2965? That's likely why the one in the other thread didn't work for us?

Cheers, and thank you for your time.
 
Hi,

You're welcome. Glad to hear you could restore the system with backups. The Fixlist I provided was just a script to get more information about the Servicing Stack so it won't fix anything yet.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top