Solved Win 11 - The component store is repairable.

fwshaw · Jan 10, 2024

It very likely the answer is here in this forum...I have search and looked, but I need some help understanding how to resolve the "The component store is repairable." message that appears after running DISM /Online /Cleanup-Image /RestoreHealth.

I've read posts and "solutions" here and at Microsoft Community forum. I get the concept, but I can "connect the dots" as what to do...I need some very simple directions.

Three months old laptop Intel CPU (13900HX), Nvidia 3040-4060 GPU, WD black SSD, Windows 11 23H2.

Any help would be greatly appreciated.

oldschool · Jan 10, 2024

Did you first use the CheckHealth and ScanHealth options prior to RestoreHealth? :think:

fwshaw · Jan 10, 2024

@oldschool - Yes, did CheckHealth then ScanHealth, followed by RestoreHealth.

oldschool · Jan 10, 2024

fwshaw said:
@oldschool - Yes, did CheckHealth then ScanHealth, followed by RestoreHealth.

Hmmm ...Did you first try

Code:

sfc /scannow

? Have your tried running DISM again?

fwshaw · Jan 10, 2024

I first ran sfc /scannow.
Then I ran DISM /Online /Cleanup-Image /CheckHealth
Then I ran DISM /Online /Cleanup-Image /ScanHealth
Then I ran DISM /Online /Cleanup-Image /RestoreHealth

After /RestoreHealth I got the "The component store is repairable." message.

I waited a couple of days and reran the same sequence... sfc, the the three DISM options. And, got the same "...repairable" Message.
The laptop operated normally during the 2 to 3 day interval between the first and second sequence. (It is operating normally now.)

I also read about the message and am a bit confused as how to proceed.

oldschool · Jan 10, 2024

fwshaw said:
I also read about the message and am a bit confused as how to proceed.

Indeed, that message usually will appear with the ScanHealth option. Sorry, but I'm stumped as well. Maybe other members will help out.

fwshaw · Jan 10, 2024

@oldschool - Apparently I was not very observant. I ran DISM /Online /Cleanup-Image /ScanHealth and it does report the message "The component store is repairable."

Any thoughts?

glasskuter · Jan 10, 2024

Does SFC run clean? If so I would not think there is anything for DISM to repair.Possibly the message is a misnomer actually meaning the component store was repairable IF there was something that needed repair.

Are you having issues? If so and DISM can't repair something, go to a repair install.

fwshaw · Jan 10, 2024

Yes, SFC is clean. No issues I'm aware of at this time. I'll look into "repair install" as I'm not familiar with the function. And, your thought about an misnomer interesting.

Rollback_Jockey · Jan 11, 2024

fwshaw said:
I first ran sfc /scannow.
Then I ran DISM /Online /Cleanup-Image /CheckHealth
Then I ran DISM /Online /Cleanup-Image /ScanHealth
Then I ran DISM /Online /Cleanup-Image /RestoreHealth

After /RestoreHealth I got the "The component store is repairable." message.

I waited a couple of days and reran the same sequence... sfc, the the three DISM options. And, got the same "...repairable" Message.
The laptop operated normally during the 2 to 3 day interval between the first and second sequence. (It is operating normally now.)

I also read about the message and am a bit confused as how to proceed.

In that case use this in an elevated CMD prompt and go make some coffee

DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase

x BlueRobot · Jan 11, 2024

oldschool said:
Did you first use the CheckHealth and ScanHealth options prior to RestoreHealth?

/RestoreHealth implicitly runs /ScanHealth and then attempts to make repairs. The /CheckHealth option just checks for two values on the CBS subkey. You don't need to run all three separately from each other.

fwshaw said:
After /RestoreHealth I got the "The component store is repairable." message.

It would be difficult to comment without first checking the CBS log(s), which should be available in the following directory:

Rich (BB code):

%systemroot%\Logs\CBS

Please make sure you place all the files inside of that directory into a .zip file and then attach it to your next post.

glasskuter said:
Possibly the message is a misnomer actually meaning the component store was repairable IF there was something that needed repair.

It shouldn't appear at all if there wasn't anything to repair. However, the repairs could be something as trivial as some orphaned packages.

glasskuter said:
Does SFC run clean? If so I would not think there is anything for DISM to repair.

SFC and DISM serve different purposes, it isn't uncommon for SFC to report no errors and then for DISM to report corruption. Essentially, SFC just scans the WinSxS directory for corrupt files and any missing hardlinks; DISM will also scan the COMPONENTS hive and CBS subkey, however, it isn't the most reliable and can report no problems when there actually is.

fwshaw · Jan 11, 2024

Attached are the DISM logs as mentions by x Blue Robot. Hopefully I have the right files.

fwshaw · Jan 11, 2024

I had a few minutes this morning so I ran (as recommended by Rollback Jocky): DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase

After running /ResetBase I again ran: DISM /Online /Cleanup-Image /ScanHealth

At the conclusion of /ScanHealth the "The component store is repairable" again was present.

See attached screenshot and logs.

Really appreciate the help and advice. Thank you all very much.

x BlueRobot · Jan 12, 2024

Rich (BB code):

2024-01-11 10:59:04, Info                  CBS    (p)    CBS Catalog Missing    (n)            Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1
2024-01-11 10:59:04, Info                  CBS    (w)    CBS Package CurrentState Missing            Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1
2024-01-11 10:59:04, Info                  CBS    (w)    CBS Package Visibility Missing            Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1
2024-01-11 10:59:04, Info                  CBS    (w)    CBS Package Owner Missing            Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

Could you please open an command prompt window and then enter the following command:

Rich (BB code):

dir "%systemroot%\servicing\packages\Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1.cat"

Please post the output of the command in your next post.

fwshaw · Jan 12, 2024

x Blue Robot - See attached screenshot of CMD result.

x BlueRobot · Jan 12, 2024

Thanks, could you please perform a registry search using FRST, please see the full instructions below:

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

fwshaw · Jan 12, 2024

Ran FRST64 as administrator. See result in attached file.

x BlueRobot · Jan 12, 2024

Thanks, please run the following fix script using FRST:

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

For transparency, here's the script contents:

Rich (BB code):

SystemRestore: On
CreateRestorePoint:
cmd: DISM /Online /Remove-Package /PackageName:Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

fwshaw · Jan 12, 2024

Ran FRST64 per instructions. Note: I did not notice a "restart". See attached files.

x BlueRobot · Jan 12, 2024

Thanks, could you please enter the following command from command prompt:

Rich (BB code):

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1" /s >> %userprofile%\Desktop\Package.txt

Please attach the package.txt file to your next post.

DISM.log Excerpt:

Rich (BB code):

2024-01-12 07:33:49, Info                  DISM   DISM.EXE: Executing command line: DISM  /Online /Remove-Package /PackageName:Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 physical location path: C:\ - CDISMManager::CreateImageSession
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Event name for current DISM session is Global\{AD4778DE-4C4F-4245-839A-381A276B6B7C} - CDISMManager::CheckSessionAndLock
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Create session event 0x54 for current DISM session and event name is Global\{AD4778DE-4C4F-4245-839A-381A276B6B7C}  - CDISMManager::CheckSessionAndLock
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadRemoteImageSession
2024-01-12 07:33:49, Info                  DISM   DISM Image Session: PID=15956 TID=12744 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2024-01-12 07:33:49, Info                  DISM   DISM OS Provider: PID=15956 TID=12744 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2024-01-12 07:33:49, Info                  DISM   DISM OS Provider: PID=15956 TID=12744 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2024-01-12 07:33:49, Info                  DISM   DISM Provider Store: PID=15956 TID=12744 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2024-01-12 07:33:49, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2024-01-12 07:33:49, Info                  DISM   DISM Provider Store: PID=15956 TID=12744 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2024-01-12 07:33:49, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2024-01-12 07:33:49, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Image session successfully loaded from location: C:\Windows\System32\Dism - CDISMManager::CreateImageSession
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.22631.3007, Image architecture=amd64
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: Image session version: 10.0.22621.1
2024-01-12 07:33:49, Info                  DISM   DISM Transmog Provider: PID=15956 TID=15220 Current image session is [ONLINE] - CTransmogManager::GetMode
2024-01-12 07:33:49, Info                  DISM   DISM Transmog Provider: PID=15956 TID=15220 Audit Mode: [No] - CTransmogManager::Initialize
2024-01-12 07:33:49, Info                  DISM   DISM Transmog Provider: PID=15956 TID=15220 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2024-01-12 07:33:49, Info                  DISM   DISM Transmog Provider: PID=15956 TID=15220 Product Type: [WinNT] - CTransmogManager::Initialize
2024-01-12 07:33:49, Info                  DISM   DISM Transmog Provider: PID=15956 TID=15220 Product Type ServerNT : [No] - CTransmogManager::Initialize
2024-01-12 07:33:49, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-01-12 07:33:49, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_SUCCESS
2024-01-12 07:33:49, Info                  DISM   DISM Driver Manager: PID=15956 TID=15220 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession
2024-01-12 07:33:49, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-01-12 07:33:49, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_SUCCESS
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Processing the top level command token(remove-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Encountered the option "packagename" with value "Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 Failed opening package Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 The specified package is not valid Windows package. - GetCbsErrorMsg
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 Failed opening package with the name "Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1" - CPackageManagerCLIHandler::Private_GetPackageNameFromCommandLine(hr:0x800f0805)
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 Failed to get the count of packages from the command line. - CPackageManagerCLIHandler::ProcessCmdLine_RemovePackage(hr:0x800f0805)
2024-01-12 07:33:49, Error                 DISM   DISM Package Manager: PID=15956 TID=15220 Failed while processing command remove-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0805)
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=15220 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2024-01-12 07:33:49, Info                  DISM   DISM Package Manager: PID=15956 TID=12744 Finalizing CBS core. - CDISMPackageManager::Finalize
2024-01-12 07:33:49, Info                  DISM   DISM Manager: PID=15116 TID=10924 Closing session event handle 0x54 - CDISMManager::CleanupImageSessionEntry
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: 
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2024-01-12 07:33:49, Info                  DISM   DISM.EXE: