Windows 10: All of our information is case. Sensitive and should be handled carefully

We all need to be carefun with information because that’s how people survive and make money as a living and with our information being so easy to get it makes their job easier, I have had my information stolen in highsvool and they destroyed my credit my criminal background and I had to fight a long battle to get my name back

:)

 

How can I access case-sensitive paths on Windows (created with Bash-on-Ubuntu-on-Windows)?

You can't access to those folders in Explorer, simply because the Win32 subsystem doesn't support case sensitivity, and Explorer doesn't support POSIX subsystem

Release Notes for WSL

 

Case sensitive DNS error

I ran into this earlier this week in trying to use Remote Desktop Connection to get to one of my laptops. It's related to the RDP certificate for the remote device. While machine names are not case-sensitive, certificate names are indeed case-sensitive. Upon seeing your post just now, I said "Hmmm. I wonder if this applies to me, too?" Here's what I just produced from my own network:




Notice that when I ping the working certificate name ("t520") the command completes successfully. But when I ping the very machine name that shows up in the ping reply ("T520") it fails. This tells me there's a problem with name resolution for machine names caused by case sensitivity. I think it's probably certificate related, but I'm not entirely sure. I'm going to report this to MS via the Feedback Hub. I'll post a link here after I do that. We should ALL upvote it. This is NOT the way that UNC names are supposed to work on MS networks!
--Ed--

PS Added 10 Minutes Later: Now posted to Feedback hub as "Machine names now case-sensitive on the LAN." Please Upvote!

PPS: Now that I think further on this, this cannot be a DNS Issue. DNS does not resolve local UNC names: that's a NetBIOS thing. See this MS Support article for an explanation Microsoft TCP/IP Host Name Resolution Order. If you read it through, it doesn't get handled until step 4 "the NetBIOS name resolution sequence." To confirm this, you can easily check that nslookup won't resolve machine names in any case (Upper/Lower/whatever). Interestingly, while nbtstat works on my LAN it is completely case-indifferent. This just keeps getting weirder!

 

Windows Phone Connector: Case Sensitive File System Incompatibility

Are there any plans to release an updated copy of Windows Phone Connector for mac that handles case sensitive file systems?

I am in a bit of a bind being unable to sync my phone without reformatting my hard drive, especially since I need case sensitivity.

I have asked about this in other threads, but since they were marked previously answered I figured I would start a fresh one. Any information on this would be extremely helpful even if it is to say there are no plans to fix this.

Thank you