New
#11
Thanks for that info. I ran sfc /scannow The testing phase completed successfully. It gave me the message paraphrasing "found corrupt files and repaired them". I took a look at the CBS.log file. The only entries in it were from this scan. It was quite long. It seemed to find quite a few system files sharing the same space. And there was only 1 file at the bottom of the log file (which I assume was a summary of sorts), which was a OneDrive.lnk file. And a message at the bottom, about all files were successfully repaired. I suppose this COULD have caused my problems, but I doubt it.