I'm getting some really crazy issues on my end here. My main work computer, that would take at least a week to rebuild back to it's current state(except fixed), just started for the first time after struggling to start for 24 hours. I was getting a no start issue and nothing would fix it but somehow it started again...
DISM tool and SFC /Scannow aren't fixing the issue by itself.
Just ran SFC /Scannow and got a couple of "Cannot repair member file" issues. Here's what it's saying:
2020-05-06 15:37:55, Info CSI 00000243 [SR] Cannot repair member file [l:9]'mfc90.dll' of Microsoft.VC90.MFC, version 9.0.30729.4148, arch x86, versionScope neutral, pkt {l:8 b:1fc8b3b9a1e18e3b}, type [l:5]'win32' in the store, hash mismatch
2020-05-06 15:37:55, Info CSI 00000244 Hashes for file member [l:11]'mfcm90u.dll' do not match.
Expected: {l:20 b:527a11f17b752da1e642f8fd625ebad444393677}.
Windows Resource Protection found 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.
Hopefully looking for a way to fix those issues.
I've attached the full CBS.log.
Thank you!
DISM tool and SFC /Scannow aren't fixing the issue by itself.
Just ran SFC /Scannow and got a couple of "Cannot repair member file" issues. Here's what it's saying:
2020-05-06 15:37:55, Info CSI 00000243 [SR] Cannot repair member file [l:9]'mfc90.dll' of Microsoft.VC90.MFC, version 9.0.30729.4148, arch x86, versionScope neutral, pkt {l:8 b:1fc8b3b9a1e18e3b}, type [l:5]'win32' in the store, hash mismatch
2020-05-06 15:37:55, Info CSI 00000244 Hashes for file member [l:11]'mfcm90u.dll' do not match.
Expected: {l:20 b:527a11f17b752da1e642f8fd625ebad444393677}.
Windows Resource Protection found 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.
Hopefully looking for a way to fix those issues.
I've attached the full CBS.log.
Thank you!
