[SOLVED] Windows 10 [10.0.19045.5796], Version 22H2 sfc errors. Those Cannot verify component files for AVG.VC140.MFC

[Hammer_three]

After command executed - sfc.exe /scannow I've got these errors:

Cannot verify component files for Policy.14.0.AVG.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002c6 [SR] Cannot verify component files for Policy.14.0.AVG.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002c7 [SR] Verify complete
2025-05-11 21:50:12, Info CSI 000002cc [SR] Repairing 8 components
2025-05-11 21:50:12, Info CSI 000002cd [SR] Beginning Verify and Repair transaction
2025-05-11 21:50:12, Info CSI 000002ce [SR] Cannot verify component files for AVG.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:5]'win32', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002cf [SR] Cannot verify component files for AVG.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:5]'win32', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d0 [SR] Cannot verify component files for Policy.14.0.AVG.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d1 [SR] Cannot verify component files for Policy.14.0.AVG.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d2 [SR] Cannot verify component files for AVG.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:5]'win32', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d3 [SR] Cannot verify component files for AVG.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:5]'win32', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d4 [SR] Cannot verify component files for Policy.14.0.AVG.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)
2025-05-11 21:50:12, Info CSI 000002d5 [SR] Cannot verify component files for Policy.14.0.AVG.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:f92d94485545da78}, type [l:12]'win32-policy', manifest is damaged (false)


Please, help!

 

[Windows Update Bot]

Hi @Hammer_three,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Hammer_three]

See the files attached

 

[Maxstar]

Hi and welcome to Sysnative,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Hammer_three]

Here it is.

 

[Maxstar]

Hi,

Step 1. Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[Hammer_three]

=====================================================
Microsoft Windows [Version 10.0.19045.5796]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>SFC /Scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>
=======================================================

Your help is greatly appreciated, Maxstar !!!

 

[Maxstar]

Great, the latest CBS log looks good so if there are no remaining issues we can mark this thread as solved.

 

[Hammer_three]

Solved problem.

 

[Maxstar]

Great, then I will mark this thread as solved...