Can't delete or open folder that end with a dot

AddRAM said:

Put in in another folder, try to delete that.

you cannot
-move it
-delete it
-open it

See this post:
Solved:

Code:

rd /s "\\?\C:\Documents and Settings\User\Desktop\Annoying Folder."

UsernameIssues said:

See this post:
Solved:

Code:

rd /s "\\?\C:\Documents and Settings\User\Desktop\Annoying Folder."

Yes, I found a solution in this thread, which basically says same thing like you said.

windows - How to delete a folder that name ended with a dot(".") - Stack Overflow

Thanks for the url link..

It's pretty dumb that windows don't fix this...

Do you know why it allows a dot, when extracting rar, but gives a error, when you delete, open, or move it?

====
The whole mess started because of this..
my rar filename was
e.g.
aaa..rar

Then I using winrar
-extract each archive to separate folders
which produce the folder

aaa.

Now when you delete, open, or move the folder
or the delete/move the parent folder

Windows would give an error message.

> It's pretty dumb that windows don't fix this...

Microsoft (Windows) will not be fixing this because it is not broken. MS has file/folder naming rules/reasons. Other operating systems have their file/folder naming rules/reasons.



> Do you know why it allows a dot, when extracting rar,
> but gives a error, when you delete, open, or move it?

Microsoft (Windows) allows* files/folders to be written this way because the Windows operating system can be used to serve up files to computers that use other operating system. In other words, a computer running a Windows operating system can hold files used by a computer running one of Apple's operating systems.



> ...I [was] using winrar
When you used WinRAR to extract the files/folders, the WinRAR app knew that you were writing the files/folders to a computer that is using the Windows operating system. The WinRAR app might have even checked/known that the name was invalid for the Windows OS. But the WinRAR app had no way of knowing what operating system you would use to interact with these files/folders after extraction. (e.g. perhaps you were putting files on your Windows based computer, but you planned on using a Linux Virtual Machine to run those files.) So, the WinRAR app named the files/folders just as they were in the RAR file.




* Microsoft provides APIs (Application Programming Interfaces). An MS API usually has various checks built in to help programmers get things done the way that the Windows OS wants (needs?) them done. The authors of WinRAR probably opted not to use the MS APIs for writing files/folders. Or, the authors of WinRAR called the MS APIs in such a way as to avoid MS's file/folder naming rules. Either way, it was WinRAR that went around Microsoft's normal checks (and that is okay).

Thanks for the explanation UsernameIssues

I will keep a watchout for RAR that has two dots in it's filename.

e.g. AAA..rar.

I still think Winrar should fix this though.

Since it is a windows app, so it should comply with windows standard.