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

[Boozad]

I still think Winrar should fix this though.

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

View 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.
View attachment 360139

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

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

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

View 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.

​

 

[UsernameIssues]

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

View 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.
View attachment 360139

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

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

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

View 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.

View attachment 360291​

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

 

[Boozad]

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.

 

[Callender]

Peazip results?

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.

 

[UsernameIssues]

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.

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

"Extract here" - original folder saved to desktop
View attachment 360298

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

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

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_

 

[Callender]

Okay the mystery is solved for me. Using Peazip 5.6.0 64bit I get

\new\test\test.txt - when using Extract or Extract Here

if using "Open As Archive"

I get shown the full paths including dots in Peazip file browser window. However any attempt to move those files into windows (desktop or anywhere else) and the additional dots get removed presumably by Explorer.

I don't see any underscores. I'm not sure why. Reseach suggests that underscores are a result of windows stripping illegal characters from file names. I cannot replicate \new_\test__\test.txt_ for some reason.

WinRAR keeps the file and folder names ending in dot but I cannot view them using Explorer and they can be force deleted.

 

[madmax2]

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

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

I have uploaded some attached files for people to test

 

[samehb]

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.

 

[madmax2]

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

 

[samehb]

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.

 

[golferguy]

I recently was noodling around for a month, decided to try a bunch of "unlockers" for a comparison study.
Even went into the wayback machine and got old freeware.

Made several dummy files and folders with period/dot at the end of name, for testing.

I already knew my oldtimer fix (XP and Win7) I always use would be the easiest and simplest,
Also tried nfts permissions changer on it.

My oldtimer repair worked perfect.
Just use 7zip and navigate / highlight the problem name file or folder, right click and rename...(.or just delete from there)
Works every time......

Done. Never comes back.

 

[Ztruker]

You're replying to a thread that is 4 years old. We call it necro posting

 

[RolandJS]

You're replying to a thread that is 4 years old. We call it necro posting

Glory be praised, the dead are raised to life

 

[golferguy]

LOL
yes I noticed, but it was not closed thread
Good information is still good information!

 

[Ztruker]

True, I just wasn't sure you noticed the date of the last post before yours.

 

[vice86]

Tried apps, tried del CMD line, tried safe mode...nothing. Finally found this post and BOOM! It worked! Thanks so much!