1.    22 Jun 2017 #1
    Join Date : Jan 2016
    Posts : 17
    Microsoft Windows 10 Pro

    dism /Online /?dism /online /cleanup- does not work, Error: 0x800f0950

      My ComputerSystem Spec
  2.    22 Jun 2017 #2
    Join Date : Jan 2015
    UK, Midlands
    Posts : 11,051
    Win 10 Pro (1703)

    From your log file:

    Failed to get and initialize the PE Provider

    DISM.EXE: Failed validating command line: Dism /Online /Cleanup-Image /RestoreHealth /source:wim:\sources\install.wim:1 /limitaccessDISM /Online /Cleanup-Image /RestoreHealth /source:WIM:\Sources\Install.wim:1 /LimitAccessSFC /SCANNOW

    DISM.EXE: Failed validating command line: Dism /Online /Cleanup-Image /RestoreHealth /source:wim:\sources\install.wim:1 /limitaccessDISM /Online /Cleanup-Image /RestoreHealth /source:WIM:\Sources\Install.wim:1 /LimitAccess

    Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image.

    -----------------------------------------------
    Have a look at
    Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
    Post #2

    Suggest you try that tool.
      My ComputerSystem Spec
  3.    22 Jun 2017 #3
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    Open administrative command prompt and type or copy and paste:


    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


    2) sfc /scannow


    3) dism /online /cleanup-image /restorehealth


    4) chkdsk /scan


    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread



    Perform windows updates and post any KB# that failed to update with error code.


    2017-06-21 23:43:36, Warning DISM DISM Provider Store: PID=9144 TID=1440 Failed to load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)


    2017-06-21 23:56:24, Error DISM DISM Package Manager: PID=11488 TID=10420 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)


    DISM DISM.EXE: Failed validating command line: Dism /Online /Cleanup-Image /RestoreHealth /source:wim:\sources\install.wim:1 /limitaccessDISM /Online /Cleanup-Image /RestoreHealth /source:WIM:\Sources\Install.wim:1 /LimitAccess




    2017-06-22 00:33:27, Error DISM DISM Package Manager: PID=2436 TID=7968 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)


    2017-06-22 00:05:04, Error DISM DISM Package Manager: PID=9532 TID=3892 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)


    2017-06-22 00:33:27, Error DISM DISM Package Manager: PID=2436 TID=7968 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0950)




    There are 3 error codes in the DISM log:
    0x800f0950 (does anyone know? its not yet on google)
    0x8007007e (unknown error?, corrupted file, missing file, or file mismatch)
    0x800f081f (cbs e source missing)


    If you post the CBS log that may have useful information.

    If scannow displays no integrity violation then the operating system is ok
    Is the problem a failed integrity scannow?

    The other option instead of troubleshooting is to perform an in place upgrade using a bootable windows 10 iso.
      My ComputerSystem Spec
  4.    22 Jun 2017 #4
    Join Date : Jan 2016
    Posts : 17
    Microsoft Windows 10 Pro
    Thread Starter

    Winver: 16256.1000

    Microsoft Windows [Version 10.0.16226.1000]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthdism /online /cleanup-image /restorehealthchkdsk /scan

    Error: 87

    The Online option has been duplicated on the command-line.
    Remove the duplicate option and try the command again.

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

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    578304 file records processed.
    File verification completed.
    5074 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    657370 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    39534 data files processed.
    CHKDSK is verifying Usn Journal...
    35940840 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487805951 KB total disk space.
    446551764 KB in 193676 files.
    131380 KB in 39535 indexes.
    0 KB in bad sectors.
    701047 KB in use by the system.
    65536 KB occupied by the log file.
    40421760 KB available on disk.

    4096 bytes in each allocation unit.
    121951487 total allocation units on disk.
    10105440 allocation units available on disk.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.16226.1000

    Image Version: 10.0.16226.1000

    [===========================88.8%=================== ]
    Error: 0x800f0950

    DISM failed. No operation was performed.
    For more information, review the log file.

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

    C:\WINDOWS\system32>


    I would upload CBS.log but it is too big.
    Should I delete it and retry?
    c:\windows\logs\CBS\CBS.log
    dism /Online /?dism /online /cleanup- does not work, Error: 0x800f0950 Attached Files
      My ComputerSystem Spec
  5.    23 Jun 2017 #5
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    For the CBS log delete everything except 1 day so there is some history with the new information.
    So once you deleted almost all the CBS log perform these commands:

    1) sfc /scannow
    2) dism /online /cleanup-image /checkhealth
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) windows updates
    Then send new copies of the cbs and dism logs.

    Were you able to perform windows updates?
    Were there any KB# that failed to update or error codes?

    The sfc /scannow found corruption and fixed it.
    The dism is a nice backup feature but in this case the corruption has been fixed.

    An in place upgrade with a windows 10 iso seems like it should be able to fix the dism problem.
    So that is the back up plan in case the cbs log cannot be deciphered.
      My ComputerSystem Spec
  6.    23 Jun 2017 #6
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    These are the three DISM errors grouped by error:


    800f0950

    2017-06-22 16:56:11, Info DISM DISM Package Manager: PID=12868 TID=10072 Error in operation: (null) (CBS HRESULT=0x800f0950) - CCbsConUIHandler::Error
    2017-06-22 16:56:11, Error DISM DISM Package Manager: PID=12868 TID=5848 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)
    2017-06-22 16:56:11, Error DISM DISM Package Manager: PID=12868 TID=5848 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0950)
    2017-06-22 16:56:11, Error DISM DISM Package Manager: PID=12868 TID=5848 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0950)
    2017-06-22 16:56:11, Error DISM DISM Package Manager: PID=12868 TID=5848 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)
    2017-06-22 16:56:11, Info DISM DISM Package Manager: PID=12868 TID=5848 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-06-22 16:56:11, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950



    8007007e


    2017-06-22 16:53:48, Warning DISM DISM Provider Store: PID=12868 TID=2408 Failed to load the provider: C:\Users\ryan\AppData\Local\Temp\9AF23DBC-46DE-40B2-9BF1-4474809CA790\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)



    800f081f

    2017-06-22 00:05:04, Info DISM DISM Package Manager: PID=9532 TID=1812 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
    2017-06-22 00:05:04, Error DISM DISM Package Manager: PID=9532 TID=3892 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2017-06-22 00:05:04, Error DISM DISM Package Manager: PID=9532 TID=3892 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2017-06-22 00:05:04, Error DISM DISM Package Manager: PID=9532 TID=3892 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2017-06-22 00:05:04, Error DISM DISM Package Manager: PID=9532 TID=3892 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
      My ComputerSystem Spec
  7.    25 Jun 2017 #7
    Join Date : Jan 2016
    Posts : 17
    Microsoft Windows 10 Pro
    Thread Starter

    Can't find how to delete CBS.log file, how do you do it?
      My ComputerSystem Spec
  8.    25 Jun 2017 #8
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    C:\Windows\Logs\CBS\CBS.log
    C:\Windows\Logs\DISM\Dism.log

      My ComputerSystem Spec

 


Similar Threads
Thread Forum
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...
Performance & Maintenance
why does Dism.exe /online stops @ 20%?
hi i have updated to KB3140768 2 days ago i did run clean disk and after Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase today i wanted to run again Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase but it...
Performance & Maintenance
DISM Online RepairHealth Error
Hello there... I've been trying to use DISM /Online /Cleanup-Image /Restorehealth on my Windows 10 Home, but it keeps telling me that it does not support servicing Windows PE with the /Online option. Of course I'm not running WinPE 10. Can...
Performance & Maintenance
Why doesn't Dism /Online /Cleanup-Image /RestoreHealth work Windows 10
Simply, why doesn't Dism /Online /Cleanup-Image /RestoreHealth work in Windows 10? Is there a way to get this or a similar command to self repair your installation in Windows 10? 48645
Performance & Maintenance
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 13:53.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums