Windows 10: Case insensitive file system that isn't case insensitive

windows 10 pro, version 2004, OS build 19041.685


I have these two directories:

C:\Users\xxx\OneDrive\pictures

C:\Users\xxx\OneDrive\Pictures


I ran fsutil on the directory that has "pictures" and "Pictures":
fsutil.exe file queryCaseSensitiveInfo C:\Users\xxx\OneDrive
and it said
Case sensitive attribute on directory C:\Users\xxx\OneDrive is disabled.


This allegedly means that C:\Users\xxx\OneDrive is not case sensitive.

So how can that directory have sub-directories "pictures" and "Pictures"?


This command

dir C:\Users\xxx\OneDrive

displayed

11/23/2020 10:59 AM <DIR> pictures
12/01/2020 08:26 AM <DIR> Pictures 1


I am really confused.

:)

 

Can't rename case in File Explorer.

Hi LoveWindows_500

This is a long known issue for many versions of Windows, this happens because in the background, files names are case insensitive and Windows ignores case . . .

The solution you have found is the actual work-around that is recommended by Microsoft . . .

rest assured, there is nothing wrong with your system, this is just a known bug that has been around forever and has not been addressed by Microsoft . . .

 

Windows Phone Connector: Case Sensitive File System Incompatibility

I went so far as to install the application on a removable read-write device that was formatted with a case insensitive file system, but that did not solve the problem. I think that is because the booted/loaded system was on the case sensitive drive and
the application tries to write configuration files to the running system.

I did not bother to install an entire second copy of the OS on another drive since that defeats the purpose of using it with my iPhoto, iTunes, etc.

I tried linking to the system files WP7 Connector writes in /Library in various capitalizations in case I could stumble upon a single file being accessed through two or more capitalizations within the application.

That was a simpleton approach and it bared no fruit.

Since the beta gets further into the startup my next approach was going to be to run a diff between the last beta and the [1.1 Mac App Store version] and start looking within the contents of the application for changes.

I have been able to use this on a case insensitive file system. I recently upgraded my computer for use with the development tools I was describing before and the WP7 Connector stopped working. The only reason I figured out why was from comments made by
others in this forum.

I did not see anything useful in the OS X Console either. No obvious errors.

I hope a solution is not out of the question. There doesn't seem to be anything fundamental about the way this program operates that would restrict it from case sensitivity.

Thanks!

EDIT: I changed the version name of latest copy I have been trying to use to help avoid confusion for future readers. I reflected my change inside square brackets.

 

How to search case-sensitive in Win10 file explorer?

Interestingly, Locate32 DOES do a case sensitive search on mp3 tags, now I've tried it. Well, well.

Whereas Ultrasearch help says:
Case sensitivity

Differences in capital or smaller case letters will be disregarded for all search types (searching for file names, file types or file content). The search is 'case insensitive'. UltraSearch will use the code page associated with the currently specified locale.