I don’t know if anyone experienced the same issue or not, but please have a look on the enclosed photo.
Basically it looks like CBS related binaries are protected, but not for other binaries under C:\Windows\System32.
Running “dism /?” or “sfc /?” will show an error prompt, but the functionalities of these binaries look okay to me.
Hi there, same problem here, exactly after updating to KB5052093!
I discovered this running sfc /scannnow, which, after clicking ok in the error window, runs perfectly.
Same thing happens with Dism /Online /Cleanup-Image /ScanHealth.
Everything was pretty fine till updating to KB5052093.
Tried to overwrite guard64.dll, in safe mode, with the same file from a disk image backup made exactly before updating to KB5052093, but it didn’t solve the problem.
Everything else is ok, if I didn’t run sfc /scannow, I wouldn’t get aware of this.
I haven’t found any solution, maybe this is too recent…
My opinion
Same problem on 2 PC 24H2 after upgrade to Build 26100.3323
The sfc /scannow command takes time to execute or does not launch.
It seems that the allocation of file tables on the C:\ disk is the cause after the KB5052093 update
To solve the problem on the 2 PCs I ran the command to check the C:\ disk using CMD in administrator mode then chkdsk /f
Once restarted sfc / scannow runs normally on the 2 PCs of different brands
Interesting solution! I’ll give it a try.
I’ve solved adding sfc.exe and dism.exe to the exclusion list in “Don’t detect shellcode injections in these applications”, under “Advanced Protection / Miscellaneous” in Comodo Settings.
I’ve followed a short guide I’ve found online, (I don’t know if I can post links to external websites, if it’s possible I’ll post the link here).
Hi All,
We are checking on this issue.
We will keep you posted.
Thanks
C.O.M.O.D.O RT
