said by Libra:
I don't know if this could have anything to do with the problem, but Microsoft was changing things regarding file permissions (giving permission to everyone) on files that have to do with root certificates and deleting a lot of files and I noticed this ntfs error at that point. When I spoke to a second level tech and asked him to fix it he said if I wasn't having a problem I shouldn't look at the error, it's only for techs to troubleshoot.
If you've already engaged Microsoft support directly for this issue, why did you not bring these issues (NTFS errors) to their attention, especially if you think they may have caused it? If you're getting support from the OS vendor, you need to continue to drive that to full completion. No offence intended, but what you've now done is create multiple "support"-type situations -- you've got people on a forum struggling to figure out how to assist you, while you've got Microsoft also helping you (?!) at the same time. The likelihood of efforts being doubled or conflicting is very very high. This does not make me happy and makes me very unlikely to assist in the future.
said by Libra:
I went into admin account and opened an elevated command prompt and typed in CHKDSK /R C: . It asked if I wanted to schedule it next time it reboots, I typed in "y". Nothing happened so I exited and restarted the computer. It said Chkdsk will check volume C. Then it said "The Volume is Clean". I didn't see it check anything and it took about 30 seconds. Did I do something wrong? or is this good news?
You didn't do anything wrong. The filesystem insists it's in good condition. Please continue to drive these issues with Microsoft support exclusively. Thanks.--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.