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

Boozad said:

UsernameIssues said:

Boozad said:

There's nothing to fix. Just click on Extract files... and choose the name of the destination folder.

Attachment 360094

I must not be following your instructions correctly.

Starting with the sample RAR that I've attached to this post...
...I selected Extract files... from the context menu.
Attachment 360139

Doing that, offered me this:
Attachment 360140
Notice that the period after "new" has automatically been removed by WinRAR.

Clicking OK in the screen shown above gets me this:
Attachment 360141

Going inside of "new" shows me this:
Attachment 360142
A folder with a problematic name for Windows.

Attachment 360143

You can create a brand new folder called whatever you want so the new. folder never gets created. No problems for Windows then.

What did you find when you went inside of that folder named "new"?

Boozad said:

Nothing, the folder was created but nothing was placed in it.

EDIT: Sorry, the New Folder was created when I first clicked on new while in Winrar but nothing was placed in there when I changed the save location. If I hadn't expanded the new folder nothing would have been placed in there, there was no option to expand it before I clicked on it.

Unless you complete the extraction, I don't think that you will see what I'm talking about. So far, I'm not seeing any benefit to adding more folders. I'm not seeing any way to prevent WinRAR from creating folder names and file names that Windows does not like when extracting the new..RAR file that I posted earlier.

The end result of the extraction by WinRAR should be \new.\test..\test.txt.
(that is one dot after new, two dots after the folder named test and one dot after txt)
Those are three "invalid" (but desired) names.

You can add all of the new folders in front of \new. that you want. It does not seem to solve anything. Or maybe I'm doing it wrong.

Callender said:

Just to add to the mix. Using PeaZip results in the following:

"Extract here" - original folder saved to desktop


results in folder named "new" and no dot. Files inside are correctly named.


Using Peazip File Browser gives exactly the same results. No dot in the extracted folder name.

They are not correct if the desired result is the exact path inside the RAR file

The 64bit version of PeaZip 5.6.0 seems to be based on 7ZIP. It changed the trailing dot(s) to underscore(s) for me.
\new_\test__\test.txt_

For anyone that wants to test this problem in winrar..

Create two rar files
-aaa..rar
-b.rar

Select both files
Right click

Choose
Winrar > extract each archive to separate folder

https://i.imgur.com/LCpwP53.png

I have uploaded some attached files for people to test

Hello, I came into this thread while I was trying to find a ready solution myself. This issue with the folders can be manually fixed by using the command line console and entering this:

dir /x /ad

What this command does is list all the folders with their short and long names. You can simply check the line with the affected folder and use the short name which is displayed right before the long name and after <Dir>. Then, use this command

ren foldershortname newfoldername

That is it. There is also a similar solution. Though, I decided to automate this since I deal with this issue having to deal with plenty of files. You can use my project to fix the folders issues without any effort. It provides shell extension support. So, you can simply right click the main folder that contains the affected folder(s) then click Fix Folders Names and you are done:

https://github.com/samehb/FoldersFixer

P.S. Sorry for bumping this old thread. I only posted here because I wanted anyone googling the problem to easily find the solution.

Regards.

samehb said:

Hello, I came into this thread while I was trying to find a ready solution myself. This issue with the folders can be manually fixed by using the command line console and entering this:

dir /x /ad

What this command does is list all the folders with their short and long names. You can simply check the line with the affected folder and use the short name which is displayed right before the long name and after <Dir>. Then, use this command

ren foldershortname newfoldername

That is it. There is also a similar solution. Though, I decided to automate this since I deal with this issue having to deal with plenty of files. You can use my project to fix the folders issues without any effort. It provides shell extension support. So, you can simply right click the main folder that contains the affected folder(s) then click Fix Folders Names and you are done:

https://github.com/samehb/FoldersFixer

P.S. Sorry for bumping this old thread. I only posted here because I wanted anyone googling the problem to easily find the solution.

Regards.

thanks

but the simple solution is posted on page 1 under my original post

madmax2 said:

thanks

but the simple solution is posted on page 1 under my original post

Hello madmax2, the fix you provided (\\?\ prefix) is what I referred to as similar solution in my post. My project allows you to mass rename all affected folders without having to deal with them one by one. It also allows you to keep the folders in case you need the files inside them. You can use it by right clicking the root folder then clicking Fix Folders Names (after running it once). That is all you need to do.

Best Wishes.