tjsepka
Contributor
When running sfc in RE, it reported that it found problems but could not fix all of them and results were in the cbs.log file. Unfortunately, sfc on the C drive was not touched and nothing appeared in x:\windows\logs\cbs\. I used attrib -H cbs.log and it reported the file was not found.
Trying to run sfc in safe mode said it was unable to start the repair service. However, it appears a cbs.log files was created (I renamed the current one) and it did say that Windows was running in safe mode, which I recall ever having seen. The current cbs.log file is attached. Nothing appears to have been appended to it in normal mode. That might change after my next reboot.
Right now a scheduled full system backup is running and it will probably take about 2 hours to complete. I can try rebooting after it's done and see what might be appended to cbs.log.
System Writer is still listed in the list of writers, so that's progress. Any thoughts on how to proceed from here?
Trying to run sfc in safe mode said it was unable to start the repair service. However, it appears a cbs.log files was created (I renamed the current one) and it did say that Windows was running in safe mode, which I recall ever having seen. The current cbs.log file is attached. Nothing appears to have been appended to it in normal mode. That might change after my next reboot.
Right now a scheduled full system backup is running and it will probably take about 2 hours to complete. I can try rebooting after it's done and see what might be appended to cbs.log.
System Writer is still listed in the list of writers, so that's progress. Any thoughts on how to proceed from here?