Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, March 16, 2018 12:59 AM
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
[===========================96.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:\WINDOWS\system32>
Here is the link of dism log
https://www.dropbox.com/s/b5fkfii5bsm7lmc/dism.log?dl=0
help pls
All replies (15)
Friday, March 16, 2018 4:15 AM
are u referring to the file i uploaded in dropbox? theres no need for a password. The file is BIG thus a "file cant be previewed" will pop up. Just click on the right side of the screen. The download button is there
Friday, March 16, 2018 5:55 AM
Yes, I did that with SFC /SCANNOW... result shows file was fixed and on next scan, shows NO file violation however when i used DISM, there is an integrity violation. Which is reliable, SFC or DISM?
Friday, March 16, 2018 7:09 AM
The error unfortunately is very common and has been hard to fix.
I run these commands very frequently on my computers:
sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk/scan
The 0x800f081f unfortunately is relatively common and it comes and goes. It can remain for a while though.
It occurred last year AFTER the Windows 1703 upgrade.
Sometimes it can be fixed by
a) making sure .net framework is up to date
b) an in place upgrade repair
c) a major windows upgrade which is coming soon
Start with these steps:
Open administrative command prompt and copy and paste:
dism /online /cleanup-image /startComponentCleanup
dism /online /cleanup-image /analyzeComponentStore
dism /Online /cleanup-image /checkhealth
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc scannow
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 edit then copy > paste into the thread
Run the fix Windows update issues which includes the Windows update troubleshooter:
https://support.microsoft.com/en-us/help/10164/fix-windows-update-errorsPerform and in place upgrade repair:
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
https://www.microsoft.com/en-us/software-download/windows10
Tuesday, March 20, 2018 6:00 AM
Hi,
Any update?
Please mount intact official Windows 10 ISO to run dism again:
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess
Note: H is the drive letter where the iso is mounted. If your drive letter is not H, replace H with your drive letter.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, March 20, 2018 6:09 AM
Haren_Hu,
The Windows 10 iso from the Microsoft website are typically in esd format.
The Windows 10 iso from non-Microsoft websites are typically in wim format.
Have you found it to be same or different?
If the Windows 10 iso in file explorer is labeled G these would be the commands:
DISM /Online /Cleanup-Image /RestoreHealth /Source:G:\Windows.~BT\Sources\Install.esd /LimitAccess
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:G:\Windows.~BT\Sources\Install.esd:1 /LimitAccess
The 1 is for professional.
On one of my computers I have been unable to fix 0x800f081f
Tuesday, March 20, 2018 6:22 AM
i went directly to step 11.
an error occurred. pics posted at answers.microsoft.com. SEE LINK below. (berrus_king is my username)
Tuesday, March 20, 2018 6:44 AM
The posts don't have numbers. Counted to post 11 and saw your username. There you commented that you did not want to perform a clean install. Was there something else to see?
Tuesday, March 20, 2018 6:53 AM
"the post dont have numbers"
Thats strange. It is on page 13 of the post. Some pics attached there. i attempted clean install using 1703 ISO. Windows said it cant create a partition on my SSD samsung.
Tuesday, March 20, 2018 7:49 AM
Found the posts. It seems to have other error codes. Thanks.
I'm looking or a fix for 0x800f081f when it is not possible to perform an in place upgrade repair or clean install and the dism commands fail. Wondering how the source files can be found that are missing in the windows 10 iso?
Tuesday, March 20, 2018 8:52 AM
The error code that is persistent is
"0xC1900101 - 0x20017 Installation failed during safe OS phase with an error during boot operation"
havent able to install w10 1703/1709 since april 2017. Still looking for a solution as provided by the users.
Tuesday, March 20, 2018 8:56 AM
Hi Karen Hu. im still encountering the same problem. "source files could not be found".
1. can you go to this link
username is beerus king, post 13. attempted clean install using bootable USB. Windows cannot create new partition.
Tuesday, March 20, 2018 9:05 AM
For the problem that you are having with the upgrade I troubleshoot the computer logs to tune up the computer. Then I provide a upgrade check list. If you want to do that then open a new thread with the 0xc19000101 0x20017 full error code and post a link into this thread.
Tuesday, March 20, 2018 9:08 AM
I already did. see this link
Tuesday, March 20, 2018 9:22 AM
Info was posted in the new thread to troubleshoot.
Tuesday, March 20, 2018 6:05 PM
Here is the link of dism log
https://www.dropbox.com/s/b5fkfii5bsm7lmc/dism.log?dl=0
2018-02-18 10:19:49, Error DISM DISM Package Manager: PID=14140 TID=11644 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2018-02-18 10:19:49, Info DISM DISM Package Manager: PID=14140 TID=11644 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
DISM.log is almost always useless. Why they can not at least give us a module name I do not know. Use the timestamp here as an index into CBS.log (if it is still present there) or into one of its archived pieces.
Robert Aldwinckle