Windows 10 and frequently corrupt files

[Puffnstuff]

I've been running 10 since August on my desktop and have clean installed several times along the way with the last being after the 1511 update. I've noticed that I'm seeing corrupt files as reported by sfc /scannow but it cannot fix the files. I'm also seeing strange behavior in IE and with other programs that often times will not launch correctly. Has anyone else seen a similar behavior from their systems? I'm in the middle of this semester but am close to clean installing yet again. The thought has crossed my mind to roll back to win 7 or 8.1 for my school system to end this problem.

 

[lxskllr]

failing drive?

 

[Mem]

failing drive?

Does sound more like hardware issue ie drive or faulty memory?..
No issues on either of my Win10 PCs, very doubt it's the OS causing this.

 

[Puffnstuff]

I've clean installed the revised 1511 on my desktop and have spent the past few hours restoring my software. I honestly don't know what the issue is but if it happens again win 7 ult x64 here I come.

 

[Anteaus]

I've have experienced similar issues. I had a file fail CRC check...which triggered me thoroughly checking the drive for errors to the to the tune of a SMART data review, complete sector scan, and full reformat. It passed everything with flying colors.

I still get weird performance hiccups with different drives when transferring files.
While I can't prove it is a Windows 10 issue, it isn't hard to pass blame in that direction.

 

[postmortemIA]

I have a bit different problem, my windows 7 partition thinks that NTFS partition belonging to windows 10 is bad. After it "fixes" it, then Windows 10 cannot boot anymore... so dual boot between these two is not optimal.

 

[readymix]

Happened to me too. 3 instances of known corruption. Notebook wouldn't boot because of some cryptic named driver was corrupt, a single project site photo transferred from desktop to archive drive was cut by two thirds and a macrium reflect image verified upon completion was corrupt after moving to another HD.

ie problems too. it would run fine most of the day, then randomly cascade into a raft of www not-responding-dot-com errors and some other anomalies. Restarting restores it.

With all the suggestion I've seen to sfc/scan, restore health and DISM whatever, whenever
someone has a problem with 10 i'm guessing google has plenty of "windows 10 file corruption" to look over.

and storage spaces lol, not working at all for me.

 

[ArisVer]

I have a bit different problem, my windows 7 partition thinks that NTFS partition belonging to windows 10 is bad. After it "fixes" it, then Windows 10 cannot boot anymore... so dual boot between these two is not optimal.

I have seen this issue with external drives and win7 and win8. The other OS wanted to fix the drive after it was fixed by the previous one.

 

[thewhat]

I have a bit different problem, my windows 7 partition thinks that NTFS partition belonging to windows 10 is bad. After it "fixes" it, then Windows 10 cannot boot anymore... so dual boot between these two is not optimal.

It's probably because you have "fast startup" enabled.

 

[Puffnstuff]

My problem happened with fast boot disabled but it doesn't seem to matter. I believe that the forced updates are corrupting system files. It's happened on my laptop too and sfc /scannow cannot fix those files either.