Windows 10: Errors in uppercase file

How do i fix errors in uppercase file, I have already tried using chkdsk C: /f, it did not work. any help would be appreciated.

:)

 

Uppercase file error





I just want to know if I can do anything else while using chkdsk to correct the uppercase file errors that were detected.

 

Uppercase file error

Indeed, Windows stopped running, so after the automatic scan made by Windows I rebooted the pc from command prompt and this is wha I got so far:

I believe this might help.Microsoft Windows [Version 10.0.14393]

X: \windows\system32>chkdsk /r

The type of the file system is NTFS.

Cannot lock current drive.

Windows cannot run disk checkking on this volumen because it is write protected.

X: \windows\system32>chkdsk

The type of the file system is NTFS.

The volumen is in use by another process. Chkdsk

Might report errors when no corruption is present.

Volume lael is Boot.

WARNING! /F paameter not specified.

Running CHKDSK in read-only mode.

Read-only chkdsk found bad on-disk uppercase table – using system table.

Stage 1: Examining basic file system structure…

29 file récords processed.

File verification completed.

0 large file récords processed.

0 bad file récords processed.

Stage 2: Examining file name linkage…

43 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors…

Security descriptor verification completed.

7 data files processed.

Errors detected in the uppercase file.

Windows has checked the file system and found problems.

Run CHKDSK with the /F (fix) option to correct these.

3086 KB total disk space.

4 KB in 9 indexes.

0 KB in bad sectors.

2485 KB in use by the system.

2048 KB in use by the log file.

597 KB available on disk.

512 bytes in each allocation unit.

6173 total allocation units on disk.

1195 allocation units available on disk.

Failed to transfer logged messages to the event log with status 50.

X: \windows\system32>chkdsk /i

The type of the file system is NTFS.

The volumen is in use by another process. Chkdsk

Might report errors when no corruption is present.

Volume label is Boot.

WARNING! /F parameter not specified.

Running CHKDSK in read-only mode.

WARNING! /I parameter specified.

Your drive may still be corrupt even after running CHKDSK.

Read-only chkdsk found bad on-disk uppercase table – using system table.

Stage 1: Examining basic file system structure…

29 file récords processed.

File verification completed.

0 large file récords processed.

0 bad file récords processed.

Stage 2: Examining file name linkage…

24 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors…

Security descriptor verification completed.

7 data files processed.

Errors detected in the uppercase file.

Windows has checked the file system and found problems.

Run CHKDSK with the /F (fix) option to correct these.

3086 KB total disk space.

4 KB in 9 indexes.

0 KB in bad sectors.

2485 KB in use by the system.

2048 KB in use by the log file.

597 KB available on disk.

512 bytes in each allocation unit.

6173 total allocation units on disk.

1195 allocation units available on disk.

Failed to transfer logged messages to the event log with status 50.

X: \windows\system32>chkdsk /F

The type of the file system is NTFS.

Volume label is OS.

Stage 1: Examining basic file system structure…

571648 file récords processed.

File verification completed.

Deleting orphan file record segment 18210.

Deleting orphan file record segment 350860.

Deleting orphan file record segment 350861.

Deleting orphan file record segment 350862.

Deleting orphan file record segment 350863.

13957 large file récords processed.

0 bad file récords processed.

Stage 2: Examining file name linkage…

Deleting index entry offsymsl.ttf in index $I30 of file 264301.

660378 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors…

Security descriptor verification completed.

44366 data files processed.

CHKDSK is verifying Usn Journal…

36616 USN bytes processed.

Usn Journal verifiction completed.

Stage 4: Looking for bad clusters in user file data…

Windows replaced bad clusters in file 3787

Of name \Windows\Logs\NetSetup\SERVIC~2.ETL.

Windows replaced bad clusters in file 7057

Of name \PROGRA~1\UNP\Logs\UN3A48~1.ETL.

Windows replaced bad clusters in file 7122

Of name \Users\ ROBERT~1\ DOWNLO~1\Twister\TWISTE~1\TWISTE~1.MP4.

Windows replaced bad clusters in file 7659

Of name \Windows\Logs\NetSetup\SERVIC~1.ETL.

Windows replaced bad clusters in file 7122

Of name \Users\ROBERT~1\AppData\Local\Google\Chrome\ USERDA~1\Default\Cache\f_00052b

And chkdsk is still running

I just wondered whether I need a new hard drive. I have been fearing this for some weeks, I have been running chkdsk since the first time I noticed chkdsk detected uppercase file errors but yesterday no errors were detected and today I got the same
errors detected again.

 

UPPERCASE Extension for attachments in email?

I have a new Samsung Blackjack II SGH-i617 with Windows Mobile 6.1. When receiving an email with an uppercase extension *.PDF the file will not save or open. If the same file is sent with a lowercase extension *.pdf the file can be viewed and saved.
Since the files are delivered from an automated document server (A Microsoft Product) the file extension cannot be modifed at delivery. Is there a way to work around the uppercase extensions with Windows Mobile 6.1? Modify the registry on the Windows Mobile
device to permit opening of files with uppercase extensions? View the exention when saving the file in Windows Mobile Outlook. An alternate PDF viewer that will allow viewing of file attachments with Uppercase extensions in emails?