Ok so a few days ago I received a BSOD on my Alienware Aurora R5 running Windows 10 Home 64Bit.
I didn't see the BSOD but for a second because I was out of the room and re-entered as it finished and was restarting so I don't know what error code it gave.
I didn't pay much attention to it but realized it happened just a minute or so after I had opened up Alienware Support Assistant for the first time. I thought maybe it was because of the program.
Tonight as I was playing 7 Days to Die with some friends I BSOD'd again with a Critical Process Died error.
I decided to run an sfc scan to repair any problems that I might have and it failed with this message:
"Windows Resource Protection found corrupt files but was unable to fix someof 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.
I then did research and ran the DISM command but it fails as well with this error:
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.
I have tried using a fresh downloaded .iso of Windows 10 to fix it and received the same error. When checking the DISM command it says that it is repairable. I just can't seem to repair it.
Also I have read that an upgrade of Windows 10 onto my existing Windows 10 install may fix the issue but it may not either.
I know I've read a lot of people seem to be reporting this issue though I'm not sure if I should just take this as a bug in Windows 10 as it seems to be from my research and not worry about it since everything is working fine so far or if I need to fix it.
Any advice will be appreciated.
P.S. Also I'm wondering if these BSOD's are being caused by Support Assistant because I never received a BSOD until I ran that program.
-
-
Mount your ISO and use this DISM command:
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /limitaccess
Note: Replace D with your current mounted drive letter.
If you're using ESD file, use this command Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:\sources\install.esd:1 /limitaccess
Last edited: Jan 27, 2017hmscott likes this. -
I double clicked it to mount it and then ran a similar command. It was DISM /Online /Cleanup-Image /RestoreHealth /Source:driveletter:\sources\install.wim /LimitedAccess
Then I received the error.
I see the path you posted is a bit different. Is it essential the same?
I also replaced "install.wim" with "install.esd" because I couldn't find "install.wim" in the sources folder in the .iso image. Unfortunately it still came back with the same error whether I used "install.wim" or "install.esd".
If you could confirm this path for me I'll use it when I get home.
DISM /Online /Cleanup-Image /RestoreHealth /Source:wimA:\sources\install.wim:1 /LimitedAccess
I am just using A as an example drive letter.
Are there any spaces or characters missing from the above path or should that work?
I can try it again when I get home. If it doesn't work should I do the upgrade Windows 10 on Windows 10 option?Last edited: Jan 27, 2017 -
@LinkinForcer: I have modified the command line for esd please refer above.
-
One question I have is would upgrading my Home version to Pro version fix this issue all together? -
-
An In-Windows upgrade? -
Backup your files and do a clean install. It saves a lot of time rather you spend time troubleshooting.
-
I was afraid you'd say that.......I've already got all my files and games allocated to other drives in my computer. Is just have to get the drivers and clean install and then install the programs again........sigh
Vasudev likes this.
sfc/scannow fails! HELP!
Discussion in 'Windows OS and Software' started by LinkinForcer, Jan 27, 2017.