sfc /scannow can't repair corrupt files

[OSExplorer]

Hi, everyone! Windows Resource Protection found some 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, details are included in the log file provided by the /OFFLOGFILE flag.

CBS.log shows these corrupt files, does anyone know what this is?
2024-05-21 11:31:47, Info DEPLOY [Pnp] Corrupt file: C:\Windows\System32\drivers\vmbusr.sys
2024-05-21 11:31:47, Error DEPLOY [Pnp] Failed repairing file: C:\Windows\System32\drivers\vmbusr.sys: ERROR_FILE_NOT_FOUND
2024-05-21 11:31:47, Info DEPLOY [Pnp] Corrupt file: C:\Windows\System32\drivers\vpcivsp.sys
2024-05-21 11:31:47, Error DEPLOY [Pnp] Failed repairing file: C:\Windows\System32\drivers\vpcivsp.sys: ERROR_FILE_NOT_FOUND
I tried sfc, dism, and chkdsk so i really don't know what else to do.

 

[Xploit Machine]

If your computer works fine without errors, just ignore it as it will be fixed automatically on next Windows Update, else download SysMinion https://www.stefanobordoni.cloud/projects/sys_minion/ and run 3 parts I marked RED below

 

[Mincci]

I take a chance and pumb a few months old thread. Could it be possible to get help somewhere, which is not .. well, stating the obvious repair methods. So, I have also had for some time now the problem with these few files. storvsp.sys, vmbusr.sys and vpcivsp.sys which (in this sfc-dism axel) give the error "file not found". But the dism 2 sfc fix is not for this problem, there is something else. All those files DO exist in the sys32\drivers folder, and the sxs folder has those folder for these. But if I look for example a .. well, any other .sys which is not giving an error, the size and hash of the file is the same in the store. But with these 3 files, they all take more space than the counterpart in sxs. So next one would think, "I will send both of them to virustotal and check the legitimacy". To my surprise, the files which are in the drivers folder, give results of same hash and information about a legitimate, not corrupted windows system file without any anomalies. But the files which are in repository, are not even identified as sys file, or give any details other than hashes and such. No certificates or any function.

So, when trying those windows autorepairs, they always say the files are corrupt, and when "fixing" them from the repository .. something goes wrong. Because the log says the files were not found, yet they are and owned by trusted installer. But sfc can't seemingly force the unidentified versions from repository on the files which are not the hash nor size they should be. Which is good? But I wish, on some forum, someone.. would say something more to this, because the error is clearly in the expectations of the scanner. There is nothing wrong, what makes they seem like the files need repair or they are corrupted? And why is the repository and (I use Everything app for finding all the files for comparison) the download source giving a corrupted file for fixing a non-corrupted file. First of all it should not say they are corrupt, as they are properly installed and the hash and version is right. Secondly, why does dism get some unidentifiable versions of those files as a fix - which it clearly is not. As I look the "modified", "accessed" and "created" -dates of those, the wrong sized repository files are always reloaded/modified when using these commands. But the proper file, which should not flag as an error, wont change. Maybe because it is not corrupted and "file not found" is a.. what? They are found, just in the place where the cbs.log says they are not.

I have always managed to fix and hold my devices together, working around the problems. I don't want to accept "It is a bug" or "clean install it is" reasoning, I want to know what makes this happen - to many. Hyper-V and virtualization and such, which those files are part of, works fine.

Any ideas? Apart from sfc/dism/install media. Of course one could think that it does not matter, but yes it does. I paid for "no integrity violations", not hidden denialism behind robot advisors, like on MS boards.

ps. The adding and removing hyper-v and containers from "Add or remove programs" etc won't change anything either.

- Mincci