Windows 10: Issues with case sensitive attributes on folders.

After convert an old disk from FAT to NTFS, all folders in this disk has set case sensitive attributes on.In this computer no problem accessing this files and folders, but from another computer this disk is shared on my home network can't access.I find on internet a solution to set to disable this attribute folder but is not recursive to subfolders and files. I can't set one by one all files and folders.Is there a solution?

:)

 

Date Attributes of Parent Folder based on Child Folder Attributes

Hi,

Running Windows 10 ver 1909 (build 18363.1256)

I am looking for a way to change Date Attributes (at the very least, the Date Created attribute) of a series of Folders. Each folder has one or more sub-folders that have a date in the Folder Name, and each of their Date Created attribute reflects this same date too.

I would like the Parent Folder to have the latest Date Created of its sub-folders.

Example:
Parent Folder:

• Project-XYZ

Child Folders:

• SubTask - 2019-08-07 - Title - Otherinfo
• SubTask - 2021-02-05 - Title - Otherinfo
• SubTask - 2020-06-19 - Title - Otherinfo

I would like the Date Created timestamp of Project-XYZ to be the latest from the SubTask folders, which in this case would be 2021-02-05.

Please note: I don't want the date reflected in the folder name, but in the Date Created attribute.

 

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!

 

Keyboard sensitivity issue


Hi,

I wasn't sure where to post this, i have a computer that has a keyboard sensitivity issue only in File Explorer.

this is a Windows 10 Enterprise laptop. This occurs with built in keyboard and when an external keyboard is used.

This sensitivity is not an issue in Applications such as Microsoft Word 2016 or notepad.

Any suggestions?

Thank you