Windows 10: DISM Error: 0x800f0950

Yesterday, in SFC scan there was windows integration violation found.

so, I ran DISM /online /cleanup-image /restorehealth and after reaching about 88%, it showed an error.


Error: 0x800f0950

DISM failed.


Is it a huge problem ? what are the ways to fix this ? my Laptop is running on windows 10 v1809, can i update it to v1903 without resolving that problem and if i do so will it appear again while running on v1903 ? can anyone help please ?

:)

 

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


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:rocessCmdLine_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:rocessCmdLine_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)

 

.NET Framework 3.5 installation error: 0x800F0950

Hi,

It is possible that you received the error code 0x800F0950 due to corrupted system files or a software conflict. To assist you better, we'd like to gather more information:

• Have you made any recent changes prior to this issue?
• Have you tried the suggestion shared by Andre Da Costa?
• What troubleshooting steps have you done so far?

Meanwhile, we suggest that you try to start your computer in safe mode by clicking on this
link.
It will let you start Windows in a basic state, using a limited set of files and drivers.

If the issue still persists, we suggest that you follow the steps in this
article to scan for corruption and restore corrupted files. We also recommend that you perform the instructions in this

article to restore Windows corruptions errors.

Let us know if you need further assistance.

 

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


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*Biggrin:\sources\install.wim:1 /limitaccessDISM /Online /Cleanup-Image /RestoreHealth /source:WIM*Biggrin:\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.