well I have a lot of issues with my computer so I did a error log with sfc /scannow and it gave me this log I have to upload it sorry about that the reason why I have to upload it is because it wont work with this website or pastebin anyway here is the log also the reason I am posting this is because I am stupid and do not understand this log at all so if anyone can make sense of it greatly appreciated
(also here is the thing cmd put)
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 windirLogsCBSCBS.log. For
example C:WindowsLogsCBSCBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Hi Zvark3,
Welcome to the 10blog
There are many shortcuts corrupted
Please try following command in admin command promptIf there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - TutorialCode:DISM /Online /Cleanup-Image /RestoreHealth
It just kind of frozeHi Zvark3,
Welcome to the 10blog
There are many shortcuts corrupted
Please try following command in admin command promptIf there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - TutorialCode:DISM /Online /Cleanup-Image /RestoreHealth
With froze you mean what exactly? Did the program froze, the system froze or what froze?
it just gave me this message and stopped doing anythingWith froze you mean what exactly? Did the program froze, the system froze or what froze?
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
My apologies for not telling you.
When running the restorehealth command of DISM it may indeed look like it is frozen, especially at 20% in many cases, it in reality is not frozen and will finish. It could take some hours before the command is finished.
With a few DISM commands it can take some time before they finish, it mainly depends on how bad the corruption is for how long it might take.
this time it gave me thisMy apologies for not telling you.
When running the restorehealth command of DISM it may indeed look like it is frozen, especially at 20% in many cases, it in reality is not frozen and will finish. It could take some hours before the command is finished.
With a few DISM commands it can take some time before they finish, it mainly depends on how bad the corruption is for how long it might take.
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================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:WINDOWSLogsDISMdism.log
Follow the next step of what I suggested.
I could not understand any of what the tutorial meant so I did "Option 2" and now I got this from the power shellFollow the next step of what I suggested.
PS C:UsersJackson> Repair-WindowsImage -Online -CheckHealth
Path :
Online : False
ImageHealthState : Repairable
RestartNeeded : False
This tool should make it easy to do SFC & DISM tasks Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 blog
