Windows 10: Sfc /scannow and DISM /Online fails

My Lenovo T400 with Windows 10 version 1511 works just fine. But I do find that these 2 commands fail me. Logs are attached. I do want to preserve some applications that I have installed so suggestions on how I can repair or upgrade would be appreciated. It's my understanding dism must be functional to upgrade the OS.

1) sfc /scannow
2) dism /online /?

:)

 

Windows 10 loads but return back to blue screen instead of homescreen.

Ok so I ran sfc /scannow and it completed 100%

then I ran dism /online /cleanup-image /restorehealth

but it failed until 86% and gives Error : 12175

 

Windows Push Notification User

Update: I've been able to start an sfc /scannow, I'm going to attempt to run it a couple of times and then do the

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

then do sfc /scannow again a couple more times

 

Possibly your most straightforward route is to do an in-place upgrade repair install.
If you already have a win 10 1511 bootable medium or iso, that's fine, else you will need to take care that you obtain that build for this procedure.

I'd also ask why you haven't received the upgrade to 1607- is that a deliberate decision- or part of the failure you are experiencing. You probably know we're about to receive the next major upgrade.

Precede it with this in case sthg has happened to your disk or file system:

Download and run Crystal DiskInfo (free) - this reports Good/Caution/Bad based on SMART params.
If not Good, do not continue.

From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed- else do not proceed.
Post back the result, which you can get after a restart as follows:
Read Chkdsk Log in Event Viewer in Windows 10 - Windows 10 Performance Maintenance Tutorials

An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.

For this you need an installation medium with the same base build as you have installed, and x64 if you have a 64 bits OS, else x86 (32 bits).

You should also make sure there's at least 500Mb of unallocated space on your system disk.

Recommendation:
Before you perform the following major repair procedure, do create a disk image (see below).

Repair Install Windows 10 with an In-place Upgrade - Windows 10 Installation Upgrade Tutorials
- this includes a link from which you can obtain a Windows 10 iso file (" download a Windows 10 ISO"), or create a Win 10 bootable medium.

I would recommend creating the bootable medium, as this can be used
- for any future in-place upgrade repair install
- to boot from and use its recovery options should Windows become unbootable.
- to clean install Windows

This will refresh Windows, after the manner of a Windows installation.
- all/most associations will be unchanged
- all your programs will be left installed
- However: if you have installed some on a 2nd drive, these must be uninstalled or reinstalled on C: - else you will get an error message that you can not keep my apps because they arein an unsupported directory.
- no personal data should be affected
- you will lose any custom fonts
- you will lose any customised system icons
- you may need to re-establish your Wi-Fi connection
- you will need to redo Windows updates subsequent to the build you have used for the repair install
- Windows.old will be created
- system restore will be turned off- you should turn it on again and I recommend you manually schedule a daily restore point.
- you will need to redo any language downloads including the display language if you changed that)
- inactive title bar colouring (if used) will be reset to default
- if Qttabbar is installed, you need to re-enable it in explorer (Options, check Qttabbar)
This is one of the better features of Win10: as each major build comes out, that's your updated reference build, and as updates are mostly cumulative, there will be few to do.


Please consider using disk imaging regularly. It's a brilliant way to
- preserve your system (and your sanity)
- back up your data
- restore your system to a previously working state in a relatively short time

Recommended: Macrium Reflect (free/commercial) + boot disk/device + large enough external storage medium.

 

Thank you for the detailed suggestions. I tried your recommendations and still no go, here's my status:

1) chkdsk c: /f
was run and upon laptop restart I do get the message to skip chkdsk by pressing F8 within 8 seconds if desired. I don't skip. When I check the event viewer logs, I do not have any entries that say 'wininit' and other messages don't mention chkdsk in it either. Not sure what could be wrong.

2) in-place upgrade
I did retrieve version 1511 x64 English iso and followed the process. The process goes for a while and eventually I get a popup message that tells me it failed. I'm not sure what to look for except here is the dism snipet immediately after the failed attempt.

[4432] ImageUnmarshallHandle: Reconstituting wim at C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.
[4432] ImageUnmarshallHandle: Reconstituting wim at C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.
2017-04-16 17:19:55, Error DISM API: PID=4432 TID=6932 Check/scan health cannot be run on a Windows PE target image. The operation must be used on a full Windows operating system image only. - CCheckImageHealthCommandObject::InternalExecute(hr:0x80070032)
2017-04-16 17:19:55, Error DISM API: PID=4432 TID=6932 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070032)
2017-04-16 17:19:55, Error DISM API: PID=4432 TID=6636 CCheckImageHealthCommandObject internal execution failed - DismCheckImageHealthInternal(hr:0x80070032)
[4432] ImageUnmarshallHandle: Reconstituting wim at C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.
[4432] ImageUnmarshallHandle: Reconstituting wim at C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.
[4432] [0x8007007b] FIOReadFileIntoBuffer*Sad1250): The filename, directory name, or volume label syntax is incorrect.
[4432] [0xc142011c] UnmarshallImageHandleFromDirectory*Sad793)
[4432] [0xc142011c] WIMGetMountedImageHandle*Sad3046)
[4432] [0x8007007b] FIOReadFileIntoBuffer*Sad1250): The filename, directory name, or volume label syntax is incorrect.
[4432] [0xc142011c] UnmarshallImageHandleFromDirectory*Sad793)
[4432] [0xc142011c] WIMGetMountedImageHandle*Sad3046)
2017-04-16 17:20:07, Error DISM DISM OS Provider: PID=6040 TID=1116 Unable to retrieve servicing stack folder for DLL search path modification. - CDISMOSServiceManager::SetDllSearchPath(hr:0x800700c1)
2017-04-16 17:20:07, Error DISM DISM OS Provider: PID=6040 TID=1116 Failed trying to determine the OS Version. HRESULT=0x800700c1 - CDISMOSServiceManager::get_OSVersion
2017-04-16 17:20:07, Error DISM API: PID=4432 TID=2920 base\ntsetup\opktools\dism\api\lib\dismcore.cpp:524 - CDismCore::LogImageSessionDetails(hr:0x800700c1)
2017-04-16 17:20:07, Error DISM API: PID=4432 TID=2920 Failed to log image session details. HRESULT=800700C1 - CDismCore::CheckAndConfigureOSServices(hr:0x800700c1)
2017-04-16 17:20:07, Error DISM API: PID=4432 TID=2920 Could not check and configure OS Services - CDismCore::CacheImageSession(hr:0x800700c1)
2017-04-16 17:20:07, Error DISM API: PID=4432 TID=2920 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800700c1)
2017-04-16 17:20:07, Error DISM API: PID=4432 TID=6636 CAttachPathCommandObject failed - DismOpenSessionInternal(hr:0x800700c1)


Your further suggestions would be most welcome.

 

you are using an improper DISM command line..
And windows\logs\cbs\cbs.log is better in detailing corruption results
try Image-Health, link in sig below

or

Dism /Online /Cleanup-Image /AnalyzeComponentStore
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /Restorehealth

 

@Kyhi

I did not use DISM explicitly, I only followed the click thru instructions for in-place upgrade. From my initial description, 'dism /Online /?' does not work for me. Would you still think any of these other Dism /Online might work? I'll be glad to try it tomorrow.

I have now attached the cbs.zip log. It's pretty big , hoping someone can make sense of it.
Thanks

 

Did you note the in-place upgrade must be performed with the same base build and language? (It's in the Tutorial I believe). I would guess you don't have 1511 installed...

 

Per 'Winver' command it shows as version 1511 OS build 10586.753.

I tried image-heath option 1 and DISM indicates error 193. Any insights for next steps? Post #5 has my attempt results for in-place repair.

2017-04-17 09:49:17, Info DISM DISM.EXE: Dism.exe version: 10.0.10586.0
2017-04-17 09:49:17, Info DISM DISM.EXE: Executing command line: C:\WINDOWS\system32\dism.exe /Online /Cleanup-Image /ScanHealth
2017-04-17 09:49:17, Info DISM DISM Provider Store: PID=560 TID=4720 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2017-04-17 09:49:17, Info DISM DISM Provider Store: PID=560 TID=4720 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:17, Info DISM DISM Provider Store: PID=560 TID=4720 Loading Provider from location C:\WINDOWS\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:17, Info DISM DISM Provider Store: PID=560 TID=4720 Connecting to the provider located at C:\WINDOWS\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-04-17 09:49:17, Info DISM DISM Manager: PID=560 TID=4720 physical location path: C:\ - CDISMManager::CreateImageSession
2017-04-17 09:49:17, Info DISM DISM Manager: PID=560 TID=4720 Event name for current DISM session is Global\{519C8549-CADB-4C30-9D75-365796375BEC} - CDISMManager::CheckSessionAndLock
2017-04-17 09:49:17, Info DISM DISM Manager: PID=560 TID=4720 Create session event 0x164 for current DISM session and event name is Global\{519C8549-CADB-4C30-9D75-365796375BEC} - CDISMManager::CheckSessionAndLock
2017-04-17 09:49:17, Info DISM DISM Manager: PID=560 TID=4720 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2017-04-17 09:49:19, Info DISM DISM Manager: PID=560 TID=4720 Successfully loaded the ImageSession at "C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D" - CDISMManager::LoadRemoteImageSession
2017-04-17 09:49:19, Info DISM DISM Image Session: PID=4996 TID=424 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Loading Provider from location C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Connecting to the provider located at C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-04-17 09:49:19, Info DISM DISM OS Provider: PID=4996 TID=424 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM OS Provider: PID=4996 TID=424 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2017-04-17 09:49:19, Warning DISM DISM OS Provider: PID=4996 TID=424 Failed to bind the online servicing stack - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x800700c1)
2017-04-17 09:49:19, Error DISM DISM OS Provider: PID=4996 TID=424 Unable to retrieve servicing stack folder for DLL search path modification. - CDISMOSServiceManager::SetDllSearchPath(hr:0x800700c1)
2017-04-17 09:49:19, Warning DISM DISM OS Provider: PID=4996 TID=424 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Loading Provider from location C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Connecting to the provider located at C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Loading Provider from location C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Warning DISM DISM Provider Store: PID=4996 TID=424 Failed to Load the provider: C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=424 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Info DISM DISM Manager: PID=560 TID=4720 Image session successfully loaded from the temporary location: C:\Users\Jesus\AppData\Local\Temp\24CAE93C-4F98-4278-8FEB-964F3CDCCA0D - CDISMManager::CreateImageSession
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=192 Getting Provider OSServices - CDISMProviderStore::GetProvider
2017-04-17 09:49:19, Info DISM DISM Provider Store: PID=4996 TID=192 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-04-17 09:49:19, Warning DISM DISM OS Provider: PID=4996 TID=424 Failed to bind the online servicing stack - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x800700c1)
2017-04-17 09:49:19, Error DISM DISM OS Provider: PID=4996 TID=424 Failed trying to determine the OS Version. HRESULT=0x800700c1 - CDISMOSServiceManager::get_OSVersion
20

 

Hi, could you post a screenshot of your Update history - I'm still wondering why you still have build 1511, and haven't upgraded to 1607 - now being replaced by the Creator's Upgrade- was that a deliberate decision, or is Windows update just broken, indicating other problems?

Also, can you confirm you have done the following and advise the results to check your disk and file system, given the multiple failures?

Download and run Crystal DiskInfo (free) - this reports Good/Caution/Bad based on SMART params.
If not Good, do not continue.

From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed- else do not proceed.
Post back the result, which you can get after a restart as follows:
Read Chkdsk Log in Event Viewer in Windows 10 - Windows 10 Performance Maintenance Tutorials