What's new Search

Recent content by csbx

C
Win7 - can't run sfc after memory corruption

20.2.2401 (build 20.2.5130.571) version of Avast installed (should be recent ish).
- csbx
- Post #13
- Apr 28, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Peter--just wanted to confirm that this solved my issue. A bunch of updates ran and I am now able to run sfc. Thanks a lot for your time. Don't have a lot of $, but will happily send a tip along to support the site. Thanks again !
- csbx
- Post #11
- Apr 28, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Thanks. I hope I did this correctly. Resultant SFCFix attached. AVAST had been uninstalled / re-installed and repaired recently-prompted by my noticing it appearing in the pertinent logs. Even uninstalled, and after SUR, problem not resolved (sfc still didn't run). So I re-installed AVAST. Also...
- csbx
- Post #10
- Apr 27, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Whoops--missed part about compressing file. I'll re-send if needed.
- csbx
- Post #8
- Apr 27, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Components
- csbx
- Post #7
- Apr 27, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Thanks Peter.
- csbx
- Post #5
- Apr 27, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

Thanks Rob. Here it is: CBS.log
- csbx
- Post #3
- Apr 27, 2020
- Forum: Windows Update
C
Win7 - can't run sfc after memory corruption

I had what I finally realized was memory corruption a few months back and it appears to have resulted in damaged areas of the system. Any help would be much appreciated. I've attached the relevant files (I think..). I suspect this is an easy one--er--maybe ? I notice that CBS.log is too large...
- csbx
- Thread
- Apr 27, 2020
- Replies: 13
- Forum: Windows Update

csbx