It could be caused by bad clusters on the disks. Run CHKDSK with elevated privilege first. Also try run the vendor’s diagnosis tool to scan the disk.
TechNet Subscriber Support |If you have any feedback on Technet forum, please contact email@example.com.
Did you ever try this in Windows Server 2012?
1) In the Windows File Explorer, select the hard drive, Right click, select Properties, then select the Tools tab and click the Check button in the Error Checking section. The result is a friendly dialog:
However, I still ran CHKDSK manually with the following clean results:
The type of the file system is NTFS.
Volume label is HVOL.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
1400832 file records processed.
File verification completed.
18 large file records processed.
0 bad file records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
1928132 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
263650 data files processed.
Windows has scanned the file system and found no problems.
No further action is required.
7340413 MB total disk space.
2522794 MB in 1135049 files.
281076 KB in 263652 indexes.
0 KB in bad sectors.
1696355 KB in use by the system.
65536 KB occupied by the log file.
4815688 MB available on disk.
4096 bytes in each allocation unit.
1879145983 total allocation units on disk.
1232816175 allocation units available on disk.
I would really like to try increasing the Semaphore Timeout period to prevent the Windows File Explorer failures copying large files. How do I increase the Semaphore Timeout period?