Solved Sfc and Dism errors , wont run (Class not registered & 0x80040154 )

Hi.
I have a new laptop , purchased a month ago. I bought it with DOS , I did it clean install Windows , drivers etc.

Now , when i run sfc & Dism i m taking errors and commands wont run :



I tried some solutions that I saw on the internet but they didn't work.
Any ideas to avoid clean or repai install ?
Thanks.:)

Have you make sure the Windows Modules Installer is not disabled.

Type services in the Windows search bar and open the Services application.

Scroll through the list of services and find Windows Modules Installer.

Double-click on the Windows Modules Installer and set the Startup type to Manual if it’s disabled.

FreeBooter said:

Have you make sure the Windows Modules Installer is not disabled.

Type services in the Windows search bar and open the Services application.

Scroll through the list of services and find Windows Modules Installer.

Double-click on the Windows Modules Installer and set the Startup type to Manual if it’s disabled.

Click to expand...

It is running and manual startup type. No changes , the same problem.

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type the below command into Command Prompt and press the Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.




Please replace partition letter C: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

You are executing SFC command wrong, please follow my instructions on how to execute SFC command.

FreeBooter said:

You are executing SFC command wrong, please follow my instructions on how to execute SFC command.I had

Click to expand...

I have a WinRE USB stick. I boot from it to specify the OS parttion cause i think i did it wrong.
But i fail to run bcedit. Screenshot : bcedit.jpg
Also i dont have any file that contains bcedit at my system (search with everything). Where is the file of command location ?

You are executing bcdedit command wrong.

I would suggest you perform in-place upgrade to repair Windows 11.

FreeBooter said:

I would suggest you perform in-place upgrade to repair Windows 11.

Repair Install Windows 11 with an In-place Upgrade

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Click to expand...

I solved it. The steps :
1) I had 3 image backups. One clean (just with Windows) , and 2 at 28 June (before 4 days). One "dirty" backup is with Macrium Reflect and the 2nd "dirty" with Windows.
2) I restore the image of Macrium reflect. Problem remained.
3) I restore the image of Windows. Problem solved.
The 2 images had 2 hours difference (8 and 10).
So , no clean install or repair install.

Good, you should have tried your backup first.

FreeBooter said:

Good, you should have tried your backup first.

Click to expand...

I just didnt want lose the adds of the 4 days. E.g i lost some programs , settings , and games. For example, I only had a game of pc game pass which was 60GB download and now it doesn't work.
I guess at least the current version of Windows has problems with third-party backup programs. For example, I also have EaseUS and it cannot do image recovery because it does not show the disks where the images are located (source).
Right now on my system, out of the three programs, only Windows is working properly.