Anyone getting a clean sfc scan after updating LTSC to 1387? Mine reports an integrity violation, but the cbs.log looks clean and there is no indication what the problem might be. The sfc scan starts at 2021-11-29 17:19:02 in the attached CBS file. Just wondering if something is wrong with my build. Spoiler: LTSC 2021 Updated Code: c:\>sfc /verifyonly Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found integrity violations. 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, details are included in the log file provided by the /OFFLOGFILE flag. c:\>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt c:\>DISM /Online /Cleanup-Image /ScanHealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1387 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. c:\>ver Microsoft Windows [Version 10.0.19044.1387]
Same, and who in all honesty likes Windows 11? Even more spying than Win10; a UI which is straight up copied from Gnome; even less settings to tinker with... This LTSC was a godsend and it is everything that the base Windows 10 should've been all along. "but windows 11 is faster" at release, in 2016, windows 10 was faster than windows 7 too, because it wasn't as bloated as now. I'll give it a year tops until Windows 11 becomes s**ttier than now. The downloads seem to be down due to an overflow of downloads, cloudflare error 520. How do you use SVF Files, especially on linux? EDIT: If you're on linux, like me, just use Ventoy (on the EN_US x64 iso).
+1 I tested the 2 iso ltsc french x86 and x64 without any modification at the second boot sfc / scannow reports errors
Perhaps the integrity violations it is talking about are just the double directory ownership ones? I'm not seeing any other errors. I remember someone saying that a restore function was bugged for ssd. I wonder if it is not specific to ssds but more of a core OS issue related to permissions.
I don't think it's the Duplicate ownership entries because I also see them in the cbs log for 14393 which is clean after running sfc /verifyonly. I'm just trying to figure out if this is a false positive or not.
i think i found it https://forums.mydigitallife.net/th...ot-enterprise-n-ltsc-2021.84509/#post-1705489
I noticed this issue about 10 pages back... this appears to be a problem with all later 20H1/21H2 builds, not just LTSC. CBS.log does not indicate any specific issue, but if you run a sfc /scannow it appears to to be touched a number of font files, as their timestamps update immediately after it is run.