[SOLVED] DISM /ScanHealth file not found stopping windows update

jbholtz

Member
Joined
May 1, 2020
Posts
12
I've been essentailly reading the entire internet trying to figure out my issue. I've finally run across this site and found a couple of threads that look very close to the issue that I've been having. Although all the solutions seem to tailored to the users specific issue. So hopefully someone will have the time and capability to help me though the issue as well.

Original Issue: Cannot perform the latest Windows Update w Cumaltive updates. I get an error code 0x800736b3

This led me to search and find the suggestion to inspect the Component Store as a potential issue. The commands that people have suggested are:
  1. Dism.exe /online /Cleanup-Image /AnalyzeComponentStore
  2. Dism.exe /online /Cleanup-Image /StartComponentCleanup
  3. Dism.exe /online /Cleanup-Image /ScanHealth
  4. Dism.exe /online /Cleanup-Image /RestoreHealth
The first item (AnalyzeComponentStore) works and indeed it shows that I should perform a cleanup. 4 reclaimable Packages
All the remainder of the commands though fail with the following error messages:

Code:
PS C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /StartComponentCleanup                                                                                                                                                                                                       
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[=====                      10.0%                          ]
[=============              23.5%                          ]

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS C:\WINDOWS\system32>


Here is the log in dism.log:
Code:
2020-05-01 12:00:19, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2020-05-01 12:00:19, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2020-05-01 12:00:19, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2020-05-01 12:00:19, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 CBS session options=0x400100! - CDISMPackageManager::Internal_Finalize
2020-05-01 12:00:44, Info                  DISM   DISM Package Manager: PID=12636 TID=2768  Error in operation: (null) (CBS HRESULT=0x80070002) - CCbsConUIHandler::Error
2020-05-01 12:00:44, Error                 DISM   DISM Package Manager: PID=12636 TID=7292 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2020-05-01 12:00:44, Error                 DISM   DISM Package Manager: PID=12636 TID=7292 Failed processing package changes - CDISMPackageManager::StartComponentCleanupEx(hr:0x80070002)
2020-05-01 12:00:44, Error                 DISM   DISM Package Manager: PID=12636 TID=7292 Failed to start component cleanup. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070002)
2020-05-01 12:00:44, Error                 DISM   DISM Package Manager: PID=12636 TID=7292 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2020-05-01 12:00:44, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2020-05-01 12:00:44, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2020-05-01 12:00:44, Info                  DISM   DISM Provider Store: PID=12636 TID=7292 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-01 12:00:44, Info                  DISM   DISM Provider Store: PID=12636 TID=7292 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-01 12:00:44, Info                  DISM   DISM Provider Store: PID=12636 TID=7292 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-01 12:00:44, Info                  DISM   DISM Provider Store: PID=12636 TID=7292 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-05-01 12:00:44, Info                  DISM   DISM Package Manager: PID=12636 TID=7292 Finalizing CBS core. - CDISMPackageManager::Finalize

This finally letd me to this site where I have attempted the SFCFix.exe. I received the same "cannot find the file" in the command window. It finally continued though and shows the following output SFCFix.txt:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-05-01 11:24:12.266
Microsoft Windows 10 Build 18363 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Very appreciative to any and all help here
 
Wanted to also post my CBS.log Errors:

Code:
2020-05-01 13:14:13, Info                  CSI    00000029 Scavenge: Planning Complete.
The following actions will be performed:
    Regeneration Candidates: 0
    Removal Candidates: 0
    Superseded/LDR (Delta Compression) Candidates: 0
    Null-Delta Compression Candidates:
        Mutable file Candidates: 0
        Boot-Recovery Candidates: 153
    Backup regeneration candidates: 0
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 0
    WinSxS Orphaned Objects Candidates: 0
    Manifests Orphaned Objects Candidates: 0
2020-05-01 13:14:13, Info                  CSI    0000002a MultiThreadExecQ: Maximum number of threads: 7
2020-05-01 13:14:13, Info                  CSI    0000002b Beginning Null-Delta compression of boot-recovery components
2020-05-01 13:14:13, Error                 CSI    0000002c@2020/5/1:17:14:13.351 (F) onecore\base\wcp\sil\ntsystem.cpp(5237): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20200501160019.cab to WER report.
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20200430220702.cab to WER report.
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20200430220407.cab to WER report.
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20200430103333.cab to WER report.
2020-05-01 13:14:13, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20200430041524.cab to WER report.
2020-05-01 13:14:13, Info                  CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:13, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:13, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:13, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:13, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:13, Error                 CSI    0000002d (F) STATUS_OBJECT_NAME_NOT_FOUND #1288422# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0xda77ffaab8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[196]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.18362.710 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_ru-ru_7d1c10cf261365ce'; a:(OBJ[gle=0xd0000034]
2020-05-01 13:14:13, Error                 CSI    _CASE_INSENSITIVE)}, disp = Unmapped disposition: 2013243192)[gle=0xd0000034]
2020-05-01 13:14:13, Error                 CSI    0000002e@2020/5/1:17:14:13.574 (F) onecore\base\wcp\sil\ntsystem.cpp(5237): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2020-05-01 13:14:13, Error                 CSI    0000002f (F) STATUS_OBJECT_NAME_NOT_FOUND #1288421# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0xda77ffaab8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[196]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.18362.710 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_ru-ru_7d1c10cf261365ce'; a:(OBJ_CASE_INSENSITIVE)[gle=0xd0000034]
2020-05-01 13:14:13, Error                 CSI    }, disp = Unmapped disposition: 2013245048)[gle=0xd0000034]
2020-05-01 13:14:13, Error                 CSI    00000030 (F) STATUS_OBJECT_NAME_NOT_FOUND #1288420# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0xda77ffb188, key = NULL, disp = (null))[gle=0xd0000034]
2020-05-01 13:14:19, Error                 CSI    00000031 (F) STATUS_OBJECT_NAME_NOT_FOUND #334# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd0000034]
2020-05-01 13:14:19, Error                 CSI    00000032 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #231# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80070002]
2020-05-01 13:14:19, Error                 CSI    00000033 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #229# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 22, pSink = NULL, disp = 0)[gle=0x80070002]
2020-05-01 13:14:19, Error                 CSI    00000034 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #228# 9928435 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000016, pSink = NULL, disp = 0)
[gle=0x80070002]
2020-05-01 13:14:19, Info                  CBS    Scavenge: Failed to commit scavenging of CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CSI    00000035@2020/5/1:17:14:19.176 CSI Transaction @0x2a7c8d7fa50 destroyed
2020-05-01 13:14:19, Info                  CBS    Warning: Failed to scavenge CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CBS    Failed maintenance scavenge [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CBS    Maint: end scavenge, scavenge time so far: 9 seconds
2020-05-01 13:14:19, Warning               CBS    Current tick count: 100 lower than last tick count: 235. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2020-05-01 13:14:19, Info                  CBS    Maint: completed, interruptions: 0, (this pass: time: 9 seconds, used space change: 108 KB, hr: 0x80070002, source: Scavenge)
2020-05-01 13:14:19, Info                  CBS    Reboot mark cleared
2020-05-01 13:14:19, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2020-05-01 13:14:19, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2020-05-01 13:14:19, Info                  CBS    Maint: processing complete.  Session: 30810075_3978787691. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CBS    Received notification that the operation is complete.
2020-05-01 13:14:19, Info                  CBS    progress thread terminated normally
2020-05-01 13:14:19, Error                 CBS    Session: 30810075_3978787691 failed to perform Synchronous Cleanup operation [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CBS    Session: 30810075_3978787691 finalized. Reboot required: no [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-05-01 13:14:19, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x80070002]
 
Hi jbholtz

Apologies for the delay. Are you still requiring assistance?
 
Thanks for checking on this. Yes I'm still trying to figure out what file is not being found during the Componet Service Check that hopefully is causing the Windows Update failure. Also interested in how to actually just debug this.

Any additional info that would be needed?
 
Hi

Please attach the full CBS log and the COMPONENTS hive.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
The CBS.log and Components files zipped are located on Dropbox

I have PM'd you the link and password for the file.
 
Hi

Please do the following.

Step#1 - 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. 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.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Here's the results. Pretty bland except for the one comment at the end that one key not found.
 

Attachments

Hi

Please do the following.

Step#1 - 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. 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.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Here's the results. Better output at least. HOLY BATMAN BATMAN! I just did a "Dism.exe /online /Cleanup-Image /StartComponentCleanup" and it worked!!!

Opps...Okay so I'm glad I continued. When I did the "Dism.exe /online /Cleanup-Image /ScanHealth" I see the same Error:2 The system cannot find the file specified.

So close...Here's what happened:
Code:
PS C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[==========================100.0%==========================]
The operation completed successfully.
PS C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[==                         5.0%                           ]
Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 9.03 GB

Actual Size of Component Store : 8.72 GB

    Shared with Windows : 5.76 GB
    Backups and Disabled Features : 2.95 GB
    Cache and Temporary Data :  0 bytes

Date of Last Cleanup : 2020-05-06 17:33:34

Number of Reclaimable Packages : 4
Component Store Cleanup Recommended : Yes

The operation completed successfully.
PS C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[===========                20.0%                          ]
The operation completed successfully.

Should I attempt the RestoreHealth now or could there still be errors? Thanks for my next step.
 

Attachments

BTW: I attempted to perform a Windows Update, in the case it just worked, and that did not succeed as well.
 
ok, please attach the latest CBS log.
 
Hi

It looks like there is a password required for the file?
 
ok thanks.

Please do the following.

Step#1 - 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. 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.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.


Step#2 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 

Attachments

Nice small log files now at least. Here's a zip with both Fixlog.txt and CBS.log Same password. The /RestireHealth came back with the same Error 2: The system cannot find the file specified.
 

Attachments

Hi

Please do the following.

Step#1 - 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. 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.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.


Step#2 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 

Attachments

Getting better it appears. The RestoreHealth now completed up to 62%:
Code:
C:\WINDOWS\system32> Dism.exe /online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.719

[===========================62.0%===                       ]
Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I've noticed that the fixlist.txt is adding the missing registry from the previous cbs.log. Is this essentially the idea to add these missing registry items? Any idea why these may have become missing in the first place?

As always, thanks a ton for helping through this.
 

Attachments

Hi

Yes, that's essentially what we are doing to replace the missing registry keys that is preventing DISM completing. There could be many reasons why the keys are missing - a windows update gone wrong, power outages, hard drive or memory issues to name a few.

Please do the following.

Step#1 - 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. 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.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.


Step#2 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 

Attachments

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

Back
Top