Windows 10: A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC

Discus and support A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC in Windows 10 Ask Insider to solve the problem; Hello! I've tested this process multiple times on both virtual machines and physical boxes and the result is always the same. Here is a recording of... Discussion in 'Windows 10 Ask Insider' started by /u/s1L3nCe_wb, Aug 17, 2022.

  1. A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC


    Hello!

    I've tested this process multiple times on both virtual machines and physical boxes and the result is always the same. Here is a recording of the whole process in a 1 minute video: https://streamable.com/n9dpw9

    As shown in the video, the system shows corrupted file errors and nothing has been touched.

    These are the errors from the CBS.log file

    2022-08-17 01:01:16, Error CBS Package "Package_for_KB5012170~31bf3856ad364e35~amd64~~19041.1880.1.1" requires Servicing Stack v10.0.19041.1677 but current Servicing Stack is v10.0.19041.1220. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    2022-08-17 01:01:16, Error CBS Failed to create internal package [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    2022-08-17 01:01:16, Error CBS Package "Package_for_KB5012170~31bf3856ad364e35~amd64~~19041.1880.1.1" requires Servicing Stack v10.0.19041.1677 but current Servicing Stack is v10.0.19041.1220. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    2022-08-17 01:01:16, Error CBS Failed to create internal package [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    2022-08-17 01:01:16, Error CBS Package "Package_for_KB5012170~31bf3856ad364e35~amd64~~19041.1880.1.1" requires Servicing Stack v10.0.19041.1677 but current Servicing Stack is v10.0.19041.1220. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    2022-08-17 01:01:16, Error CBS Failed to create internal package [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]



    The ISO hashes are:SHA1 510d9003c62370cf91f57482d8265ae136749bdc

    SHA256 06fd4a512c5f3e8d16f77ca909c4f20110329b8cdd5ad101e2afc0d58b06d416

    I suppose there is nothing to worry about but I thought that a fresh install should not have corruption or errors of any kind.

    submitted by /u/s1L3nCe_wb
    [link] [comments]

    :)
     
    /u/s1L3nCe_wb, Aug 17, 2022
    #1

  2. SFC reporting corrupt files in Windows 10 Pro

    Hi,



    I’m still confused. Most of the SFC log is showing a corrupt file, until the last line that states “00004dac [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired”. If
    I run SFC I get the exact same message, I have corrupted file. Is it corrupted or not? If the last line in the log file is correct why does SFC tell me I have corrupt files? Is this an issue in Windows 10 that needs to be resolved?



    Thank you
     
    everynameistaken, Aug 17, 2022
    #2
  3. Corrupted file RAR

    If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:
    • Open WinRAR application in your system.
    • Now click on File tab > Open or simply press Ctrl+O.
    • A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
    • Now click Open button.
    • Click Tools tab > Repair archive or simply press Alt+R.
    • Again a small window "Repairing File name.rar" will pop up.
    • Now click Browse to select a location to save the repaired archive.
    • Check the box "Treat the corrupt archive as RAR" and click OK.
    • WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.
    I hope the above steps will help you repair the corrupted RAR archive.

    Thanks.
     
    Lincoln Dunne, Aug 17, 2022
    #3
  4. Delta6326 Win User

    A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC

    Delta6326, Aug 17, 2022
    #4
Thema:

A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC

Loading...
  1. A Windows 10 Pro 21H2 fresh install shows corrupt files after SFC - Similar Threads - Pro 21H2 fresh

  2. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 BSOD Crashes and Debugging
    sfc /scannow found corrupt files after fresh win10 install: There is another discussion with this name but its locked. The first thing an answer states is that if partitions etc are not deleted and formatted then its not a fresh install, yet I have done that, and I have this issue.......
  3. Windows 10 Corrupted File system after fresh install

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 Corrupted File system after fresh install: i formatted my windows using reset windows on recovery menu, windows is booted up now i tried to open settings and it closed after openning it and gived an error, i tried to open notepad it won't open...
  4. Why is sfc /scannow finding corrupt files after a fresh Windows 10 installation?

    in Windows 10 Ask Insider
    Why is sfc /scannow finding corrupt files after a fresh Windows 10 installation?: I fresh installed Windows 10 because my old installation was corrupt but now sfc /scannow says this version has corrupt files and it repaired them. Why are there corrupt files on a fresh installation? submitted by /u/360isepic [link] [comments]...
  5. Corrupted file shown in sfc /scannow after fresh Windows install

    in Windows 10 Drivers and Hardware
    Corrupted file shown in sfc /scannow after fresh Windows install: Hi, I am facing some issue with respect to disk drive in my system. One day, I couldn't boot windows and it runs to automatic repair loop on boot. I have tried repair, reset and all other options provided in trouble shoot, but still nothing works. Finally, I have used HP...
  6. sfc /scannow shows corrupted file

    in Windows 10 BSOD Crashes and Debugging
    sfc /scannow shows corrupted file: I've run SFC /scannow from both inside Win 10 admin command prompt and SFC scan from Safe Mode, I've also run DISM /Online /Cleanup-Image /RestoreHealth and still show corrupted files here's several sample from the SFC log file 2019-10-19 13:03:25, Info...
  7. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 Performance & Maintenance
    sfc /scannow found corrupt files after fresh win10 install: I started scan with admin priv. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs,...
  8. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 BSOD Crashes and Debugging
    sfc /scannow found corrupt files after fresh win10 install: I started scan with admin priv. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline...
  9. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 Support
    sfc /scannow found corrupt files after fresh win10 install: I started scan with admin priv. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs,...
  10. Random shutdowns, sfc /scannow returns corrupted files, fresh install

    in Windows 10 Performance & Maintenance
    Random shutdowns, sfc /scannow returns corrupted files, fresh install: Hello everyone, yet again another sfc /scannow thread... This one comes with random computer shutdowns, no matter what I'm doing or what processes are launched (game, windows explorer or web browser). When the computer crashes, it just shuts down, like if the power cable...