sfc /scannow fails on new UEFI Install  


  1. Posts : 165
    Windows 10 Pro 64bit Build 2004
       #1

    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?
      My Computers


  2. Posts : 4,116
    Windows 3.1 to Windows 11
       #2

    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
      My Computer


  3. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #3

    ................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.
      My Computer


  4. Posts : 133,860
    Windows 11 Pro (x64) 23H2 Build 22631.2792
       #4

    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.
    http://www.macrium.com/reflectfree.aspx
    Just wish more people would make backups instead of waiting till its too late.
      My Computers


  5. Posts : 165
    Windows 10 Pro 64bit Build 2004
    Thread Starter
       #5

    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.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:08.
Find Us




Windows 10 Forums