Error: 0x800f081f The source files could not be found.

What i had done so far..

ran an elevated CMD..

( already exported install.wim from install.esd to root on C: drive. )

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

C:\WINDOWS\system32>cd/

C:\>sfc /scannow

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

C:\>dism /Get-WimInfo /WimFile:install.esd

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Details for image : install.esd

Index : 1
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 15,305,539,033 bytes

Index : 2
Name : Windows 10 Home
Description : Windows 10 Home
Size : 15,127,824,725 bytes

Index : 3
Name : Windows 10 Home Single Language
Description : Windows 10 Home Single Language
Size : 15,129,601,869 bytes

Index : 4
Name : Windows 10 Education
Description : Windows 10 Education
Size : 15,125,050,322 bytes

The operation completed successfully.

C:\>dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Exporting image
[==========================100.0%==========================]
The operation completed successfully.

C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:C:\install.wim:1 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================88.6%===================       ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

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

C:\>DISM /Online  /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

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

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 7.43 GB

Actual Size of Component Store : 7.38 GB

    Shared with Windows : 6.09 GB
    Backups and Disabled Features : 439.41 MB
    Cache and Temporary Data : 848.27 MB

Date of Last Cleanup : 2017-04-17 09:29:27

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================88.6%===================       ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:F:\sources\install.wim:1 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================88.6%===================       ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\>

Hi Muhammad,

This error may occur when you use an installation wizard, the Deployment Image Servicing and Management (DISM) tool, or Windows PowerShell commands to enable the .NET Framework 3.5.

We suggest that you follow the troubleshooting steps found on this link to resolve your issue.

Do get back to us should you encounter any difficulties.

22 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I opened the given link and got so confused on Resolution for Windows 10.. there's missing information.

i mean.. if you check that link.. where or what is referring to when it said "Configure the Group Policy as in Method 2"..

what is method 2???

BTW.. i am not trying to enable .NET Framework 3.5 or anything..

i am trying to get my system health report back to normal state.

8 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The solution is very simple and it is a bug.
At least C:\Windows\system32\Dism\ do not contain two files DLL to execute DISM.EXE:  SiloedPackageProvider.dll and MetaDeployProvider.dll.

Microsoft Windows [version 10.0.15063] (c) 2017 Microsoft Corporation.

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth

...

C:\Windows\Logs\DISM\dism.log (partim):

2017-04-16 09:10:26, Warning               DISM   DISM Provider Store: PID=2564 TID=4824 Failed to Load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-04-16 09:10:26, Warning               DISM   DISM Provider Store: PID=2564 TID=4824 Failed to Load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Philippe
PC sous Win 11 Pro 22H2 (22621.674)
Protection par Windows Defender
N'oublier pas de voter si ma réponse a été utile
et surtout de respecter les autres.
Merci

9 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The solution is very simple and it is a bug.
At least C:\Windows\system32\Dism\ do not contain two files DLL to execute DISM.EXE:  SiloedPackageProvider.dll and MetaDeployProvider.dll.

Microsoft Windows [version 10.0.15063] (c) 2017 Microsoft Corporation.

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth

...

C:\Windows\Logs\DISM\dism.log (partim):

2017-04-16 09:10:26, Warning               DISM   DISM Provider Store: PID=2564 TID=4824 Failed to Load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-04-16 09:10:26, Warning               DISM   DISM Provider Store: PID=2564 TID=4824 Failed to Load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

what exactly are you suggesting i should do here?

run this dism.exe /online /cleanup-image /restorehealth on powershell/cmd ?

also where did you get that log file from anyway?

are you having the same issue? or have been?
please ELI5 me.. thanks

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

There is a solution to wait that the gurus of Microsoft correct the error from their part side. Sorry
Philippe
PC sous Win 11 Pro 22H2 (22621.674)
Protection par Windows Defender
N'oublier pas de voter si ma réponse a été utile
et surtout de respecter les autres.
Merci

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

There is a solution to wait that the gurus of Microsoft correct the error from their part side. Sorry

you did not answer what i asked and also you are misleading my post by bringing up another situation which is entirely different than what i'm facing.

i can run DISM.exe fine via powershell or cmd.

please don't make this by messing up even worst by explaining something else.

If you have another situation that is related to DISM.. then go and post/make your own question on the community.

thanks.

16 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

For us to isolate the issue, we recommend that you create a new user profile.  If it's not happening on the test user profile, it only means that the current user profile is corrupted.

In case you experience the same issue on the new user profile, we suggest that you perform a System File Checker scan.  This will allow you to scan for corrupted system files and restore corrupted files.  You can find steps on this link.

Don’t hesitate to reach out if you need additional assistance.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

after giving all sort of info on my first post.. i don't know how you managed to get the position as Forum Moderator.

please don't hesitate to quit this post or change to another department.

-moving away from windows to linux.

53 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The solution for the Windows 10 v1703 DISM error 0x800F081F

http://borncity.com/win/2017/04/26/windows-10-v1703-fix-for-dism-error-0x800f081f/

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

For us to isolate the issue, we recommend that you create a new user profile.  If it's not happening on the test user profile, it only means that the current user profile is corrupted.

In case you experience the same issue on the new user profile, we suggest that you perform a System File Checker scan.  This will allow you to scan for corrupted system files and restore corrupted files.  You can find steps on this link.

Don’t hesitate to reach out if you need additional assistance.

It seems like microsoft update error. You might want to look at http://borncity.com/win/2017/04/26/windows-10-v1703-fix-for-dism-error-0x800f081f/ . Same thing is happening for 15063.250 .

win

12 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated May 18, 2024 Views 80,375 Applies to: