Question SFC Scannow bug?

[wandererlost]

Hey guys. I hope everyone is well. Every time I run the integrity checker, sfc scannow shows that there are files with corrupted integrity and repairs them.
Being that every time I run it, it finds the same problems and fixes the same problems too.
It ends up repeating this infinitely every time I check.
I updated my Windows to the newest version 24H2. In the previous version 23H2 this problem did not occur. Could it be a build issue?
The image is in Portuguese, but what it means is that every time it finds an error and claims to have corrected it.
"Windows Resource Protection found corrupt files and repaired them successfully."

https://imgur.com/f3WnSPE

View: https://imgur.com/f3WnSPE


I have also tried using dism and found no integrity violations or problems.I also used chkdsk and it didn't solve this problem. I've also tried going into safe mode and it didn't help.

 

[kanewolf]

Hey guys. I hope everyone is well. Every time I run the integrity checker, sfc scannow shows that there are files with corrupted integrity and repairs them.
Being that every time I run it, it finds the same problems and fixes the same problems too.
It ends up repeating this infinitely every time I check.
I updated my Windows to the newest version 24H2. In the previous version 23H2 this problem did not occur. Could it be a build issue?
The image is in Portuguese, but what it means is that every time it finds an error and claims to have corrected it.
"Windows Resource Protection found corrupt files and repaired them successfully."

https://imgur.com/f3WnSPE

View: https://imgur.com/f3WnSPE


I have also tried using dism and found no integrity violations or problems.I also used chkdsk and it didn't solve this problem. I've also tried going into safe mode and it didn't help.

Maybe the corruptions are because you have a disk or RAM problem. That is WAY more likely than a bug, IMO.
Start with a multi-hour run of MEMTEST -- https://www.memtest86.com/

 

[wandererlost]

Maybe the corruptions are because you have a disk or RAM problem. That is WAY more likely than a bug, IMO.
Start with a multi-hour run of MEMTEST -- https://www.memtest86.com/

The mdsched.exe did not encounter any errors. Just like chkdsk didn't find any errors either.
Couldn't it be a bug in the newer version of Windows? I didn't have these problems in version 23H2.

Edit: As I suspected. It's a problem with the build of Win 24h2 itself.
https://answers.microsoft.com/en-us...10001876/aab97215-92cd-4f0c-86e1-4f600afc7dc3