New
#20
No problem. :)
Good Morning Brinks
Great article, Upgraded to Win 10 Home yesterday...Before upgrading I checked that sfc was good in Windows 7 64bit Home premium, from Admin level...After a failed install "Something Happened" window...I restarted the process again. Completion of install, I created a "Restore point", and a few more. Later in the day after many problems I decided to check sfc....corrupt, ran 3 or 4 more times with no repair. Restore Points do not allow me a clean sfc. One of the error refers to"Microsoftedge" mentioned earlier in this tutorial. I have attached the errors below. I must admit I am not in a comfort zone entering data in the Command Prompt!
My main problems, Bluetooth failures, Very slow boot up or recovery from sleep(Black screen) could be more!
What are my options, apart from starting with "Step One"?
Can I start the whole upgrade again?
In anticipation of a reply
Thanks, Stu...If this is posted in the wrong place ..sorry, please move.
Code:2015-08-0306:07:11,Info CSI 000050de [SR] Verify complete 2015-08-0306:07:11,Info CSI 000050df [SR] Repairing 1 components 2015-08-0306:07:11,Info CSI 000050e0 [SR] Beginning Verify and Repair transaction 2015-08-0306:07:12,Info CSI 000050e1 Hashes for file member\SystemRoot\WinSxS\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16397_none_19381f0c8accd5dd\MicrosoftEdgeSquare44x44.scale-125_contrast-white.pngdo not match actual file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-08-0306:07:12,Info CSI 000050e2 [SR] Cannot repair member file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" ofMicrosoft-Windows-MicrosoftEdge, Version = 10.0.10240.16397, pA = amd64,nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-08-03 06:07:14,Info CSI 000050e3@2015/8/3:05:07:14.340 Primitive installers committed for repair 2015-08-0306:07:14,Info CSI 000050e4 Hashes for file member\SystemRoot\WinSxS\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16397_none_19381f0c8accd5dd\MicrosoftEdgeSquare44x44.scale-125_contrast-white.pngdo not match actual file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-08-0306:07:14,Info CSI 000050e5 [SR] Cannot repair member file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" ofMicrosoft-Windows-MicrosoftEdge, Version = 10.0.10240.16397, pA = amd64,nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-08-0306:07:14,Info CSI 000050e6 [SR] This component was referenced by[l:156{78}]"Package_376_for_KB3074683~31bf3856ad364e35~amd64~~10.0.1.0.3074683-592_neutral" 2015-08-0306:07:14,Info CSI 000050e7 Hashes for file member\??\C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Assets\MicrosoftEdgeSquare44x44.scale-125_contrast-white.pngdo not match actual file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-08-0306:07:14,Info CSI 000050e8 Hashes for file member\SystemRoot\WinSxS\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16397_none_19381f0c8accd5dd\MicrosoftEdgeSquare44x44.scale-125_contrast-white.pngdo not match actual file[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-08-0306:07:14,Info CSI 000050e9 [SR] Could not reproject corrupted file[ml:142{71},l:140{70}]"\??\C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Assets"\[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png";source file in store is also corrupted 2015-08-0306:07:14,Info CSI 000050ea CSIPERF - FilePI Queue 220ms 2015-08-03 06:07:14,Info CSI 000050eb@2015/8/3:05:07:14.871 Primitive installers committed for repair 2015-08-0306:07:14,Info CSI 000050ec [SR] Repair complete 2015-08-0306:07:14,Info CSI 000050ed [SR] Committing transaction
Last edited by Brink; 03 Aug 2015 at 09:40. Reason: code box
Hello Stu, and welcome to Ten Forums. :)
Your SFC report shows that a had mismatch has been found for a image file that belongs to Microsoft Edge.
It's nothing to worry about, and would not be related to your other issues.
If you like, please feel free to create a new thread for your other issues to see what we can do to help.
Hi Brinks
Thank you your reply and possible good news. I think you are telling me to live with the corruption and not try to repair...?
Stu
Stu,
It's not corruption, but only a false hash mismatch on an image file used by Microsoft Edge.
Hi Brinks
getten this issue
Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
Image Version: 10.0.10240.16384
[==========================100.0%==========================]
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 Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
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 but was unable to fix some
of 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.
whats happening please?
Hello nitehawk, :)
It seems that many have been getting the Error: 0x800f081f lately for DISM. So far, the only thing that has helped was a clean install.
Hi Brinks
windows seems to be working fine for me right now
if i did a restore which cleans the files n such instead of a clean install will that work?
also is it or will this error cause a major failure by any chance if ignored
it would seem many people wouldn't even know its an issue at this point unless they run that command?
thanks
I'm thinking it may be a bug from a recent update.
A restore to before (if known) this error may help, but if you're not having any issues, then I wouldn't worry about it.
i get this under check health
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
Image Version: 10.0.10240.16384
The component store is repairable.
The operation completed successfully.
so im wondering why it dosent repair
why cannot there be an online version via scannow that connects to a component store somewhere online and downloads the missing or corrupted files
can i run scannow or restore health off a windows dvd to fix corrupted files>?
Last edited by nitehawk; 15 Aug 2015 at 04:28.