Windows 10: sfc /scannow fails on new UEFI Install

Hey all,

Just a little concerned. I installed to my new PC: Windows 10 Pro x64. This was from a brand new OEM DVD. I installed under UEFI. Installation was a breeze with no errors or issues.

Immediately after the installation completed, I installed the motherboard drivers, rebooted and GPU driver, rebooted. Device Manager showed zero problems. All looking good.

Then I ran sfc /scannow and it reported errors. I did not run it because I thought there might be an issue, in fact the PC was running brilliantly, but I did not want to start loading all my software without first checking this. I did not bother much with the CBS.log file as I did not understand anything in it.

So I tried again, deleting all partitions on the SSD and starting from scratch with another fresh, clean install of Windows. Exact same thing the second time. Why would this happen?

Anyway, after some research, found some info on the "DISM" command and popped the DVD back into the drive and it ran the process and it seemed to fix whatever was wrong. The sfc /scannow command now gives no errors.

Before I go ahead and start loading software and registering licenses etc, is this something I should be concerned about? Just bothering me that a brand new install can already have an issue like this?

:)

 

sfc/scannow failed

Microsoft Windows 10

Version 1511 (OS Build 10586.318)

The problems I have been having with the laptop at the moment is that the laptop, overall, is running quite slow and Google Chrome is not running properly overall. I tried to do a system restore, as this helped before. However it said Windows8_OS C) (System)
drive needs to be restored, however it has errors and has detected file system corruption. I have just recently got it to restore at the moment. So I will see if the problem persists after.

Thanks so much by the way.

 

sfc/scannow failed

Happy to help.

The source option usually means you have to mount an ISO of the same version of the OS that is running on the computer (described in the wiki). I cant really read the snip but it appears your image is 10586.0. I suspect your running build is higher.
You can check that by typing winver in run. (win key +"R">winver)

I am not sure that SFC is the proper tool for the performance issue so if you can be more specific about the problems you are having NOW I might be able to suggest something else.

 

without seeing the LOG - I would assume you have a Nvidia video card..
There is a known issue with the opencl.dll that causes such an error in SFC..

The problem is being addressed by MS - and at that point is not really an issue for your PC

 

................Anyway, after some research, found some info on the "DISM" command and popped the DVD back into the drive and it ran the process and it seemed to fix whatever was wrong. The sfc /scannow command now gives no errors................

IF dism command fixes " whatever was wrong" and sfc /scannow "now gives no errors", then your computer is free and clear.
There is nothing for you to be concerned of.

 

What I would do right now before anything else is make a Complete Image Backup, and put this on a 2nd drive. This way if something happens again, you can restore your Windows 10 without having to re-install. Use the free program Macrium Reflect. Here is the link.
Macrium Software | Macrium Reflect Free
Just wish more people would make backups instead of waiting till its too late.

 

Thanks for the advice! And yes, will definitely make a full system back up right now before loading any programs. I do have Acronis True Image (will have to install it first of course). I do indeed have a NVidia GTX780Ti installed.