Why You Can't Name a Folder '._.' in Windows 7

Exploring Unusual Folder Names in Windows
Driven by curiosity or a simple desire for change, users occasionally experiment with unconventional names for folders within their Windows operating system. The outcomes of such endeavors can vary significantly.
This exploration stems from a question posed by a reader, which is addressed in today’s featured SuperUser Q&A post.
Understanding the SuperUser Community
The source of this information is SuperUser, a valuable segment of Stack Exchange. Stack Exchange is a network of question-and-answer websites maintained by its user community.
SuperUser provides a platform for users to seek and share technical knowledge.
The accompanying screenshot of the message window was kindly provided by Ben N, a contributor to SuperUser.
- It’s a community-driven resource.
- It focuses on superuser-level questions.
- It’s part of the broader Stack Exchange network.
The question and answer session offers insights into the behavior of Windows when presented with atypical folder names.
Understanding these nuances can prevent unexpected issues and ensure a smoother user experience.
Understanding the Folder Naming Restriction
A SuperUser user, EdwardBlack, recently inquired about the inability to create a folder named ._. within a Windows 7 environment.
The system automatically renames the folder to ._, or in some instances, causes it to briefly vanish before reappearing upon a view refresh.
The Root Cause: Dot Handling in Windows
This behavior stems from how Windows handles filenames containing periods (dots). Specifically, the operating system exhibits sensitivity towards dots positioned at the end of a filename.
Windows interprets trailing dots in filenames as potentially indicating hidden or system files, leading to the observed renaming or temporary disappearance.
Historical Context and Compatibility
The restriction originates from compatibility considerations with older file systems, particularly those used in networking environments.
In older systems, a trailing dot was often used to signify hidden files or directories, a convention Windows inherited.
The ._ Sequence and macOS
The specific sequence ._. is particularly noteworthy because it's commonly associated with macOS's "resource fork" files.
These files store metadata related to applications and documents on macOS systems.
Why Windows Intervenes
To prevent potential conflicts and maintain file system integrity, Windows actively prevents the creation of folders with names like ._..
By renaming or suppressing the folder, Windows aims to avoid misinterpreting it as a macOS resource fork file and causing data corruption or unexpected behavior.
In Summary
The inability to name a folder ._. in Windows 7 is a deliberate design choice rooted in historical compatibility concerns and the prevention of conflicts with macOS file system conventions.
The system's handling of trailing dots in filenames, coupled with the significance of the ._. sequence in macOS, results in the observed renaming or temporary disappearance of such folders.
Understanding File and Folder Naming Restrictions in Windows
A SuperUser community member, Ben N, provides insight into why Windows imposes certain limitations on file and folder names.
Typically, Windows operating systems necessitate that files possess either no extension or an extension consisting of at least one character. Files cannot have extensions of zero length – meaning filenames should not conclude with a period.
Furthermore, folders are also capable of having extensions, leading Windows to disallow folder names that terminate with a period.
This behavior stems from the way Windows interprets the period as a separator between a filename and its extension. The source of this information is an article referenced by DavidPostill.
Key Points from the Source
- The period functions to delineate the base filename from the extension when naming both directories and files.
Attempting to conclude a file or directory name with a period results in Windows disregarding the intended extension and removing it. This occurs even when utilizing the md command within a command prompt.
Potential Issues and Workarounds
While generally discouraged, a folder name ending in a period can be created using the special raw name override sequence \\?\. For example, md \\?\C:\path\to\container\._. will create a folder named ._..
However, numerous applications, including Windows Explorer, may encounter difficulties processing such a directory.

Removing such a directory requires the rd command, again utilizing the \\?\ notation. Alternatively, renaming it using its short (8.3 format, obtainable via dir /x) name is also possible.
This workaround is not recommended for general use due to potential compatibility problems.
Do you have additional information to contribute to this explanation? Share your thoughts in the comments section below. For a more comprehensive discussion and further insights from other technical experts, please visit the original Stack Exchange thread here.





