Recent Posts

Pages: [1] 2 3 ... 10
« Last post by admin on February 08, 2018, 12:15:18 PM »
Despite all installed updates and two spam prevention systems, there are hundreds of spam messages in moderation.
I am not able to keep up cleaning it so I have decided to disable registration and posting on forum. It will stay as help resource but for now it will not be maintained.
You can still contact me through One Commander's feedback message, mail, Twitter, Facebook...
Themes / Re: LightBlack theme
« Last post by admin on January 22, 2018, 11:07:06 AM »
Thank you. I have been using it for a few days and as a Max user, I like it. You should just change icon colors as black on gray is hard to see. For example, the icons in context menus are hard to see, especially on the TVs when color is not well calibrated.
Bugs / Re: Cannot open a filename exceeding 260 characters
« Last post by admin on January 13, 2018, 08:36:30 PM »
Hi Joe,

Even though the OC supports long paths, the program in which you are trying to open or save the file might not support it. It depends on the API the end program uses, and some don't support long paths. When OC shows notification that the file was opened, it has started the system process to open it, and then the rest is up to Windows and the associtated program to open the file.
Bugs / Cannot open a filename exceeding 260 characters
« Last post by Joe on January 06, 2018, 03:01:00 PM »
Hello One Commander,

First of all, thank you very much for this intuitive, innovative, user-friendly, and robust software. It's making my life a ton easier rather than using Windows 10 explorer.

I currently installed One Commander yesterday and I am having some difficulties with long filenames. This particularly happens when the file's name exceeds Explorer's 260 character limitation forcing me to either shorten the filename or move it to another location. To better illustrate, let me use an example:

The filename I am modifying: instructions
Where is the filename located in Explorer: c:\users\joe\desktop\health\software\guides\listofmodules\instructions

Note: I truncated the names for these folders located in the path above for easability and confidentiality purposes.

If I try changing listofmodules to list of modules, Explorer will prevent the action from occurring. The reason is because with the extra spaces in between those words, that folder name will exceed the 260 character limitation. Hence, I am forced to name the folder listofmodules without the spaces.

Now, when I try renaming that folder to "list of modules" using One Commander, since it supports longer filenames, if I try double clicking the file contained in that folder (i.e. instructions) I get a dead response. A "File Opened" message pops up on the top of One Commander, but the pdf file simply doesn't open on my computer.

When I try clicking this very same instructions file via Windows Explorer, I also get a dead response. Any files located outside of the listofmodules folder open up just fine.

It seems the problem is prevalent only when I try expanding a folder's or file's name WITHIN ONE COMMANDER that exceeds Explorer's 260 character limitation.

Any thoughts?

Also, if I continue to use One Commander will I also run into similar problems when I save all my files and folders contained in the above file path onto a flash drive? For example, if I expand a filename or folder name within One Commander and then save that same file or folder onto a flashdrive, will I run into errors when I try to access that same file or folder via the flashdrive?

Any help would be immensely appreciated!

Themes / LightBlack theme
« Last post by Rider on January 05, 2018, 05:44:07 AM »
I made this theme for matching with adobe or 3dsmax/maya interface
I hope you'll like  :)
Bugs / Re: Getting consistent bluescreens, "wcifs.sys failed"
« Last post by MaxusValtron on December 20, 2017, 05:27:45 PM »
Ahhh good thought. I've got WinAero Tweaker running on all my machines, which does indeed include changes to context menu items, file explorer, and others.

I'll try disabling that then report back if I still have issues with the UWP version.

For now, I'm happy that I can use OC again though!
Bugs / Re: Getting consistent bluescreens, "wcifs.sys failed"
« Last post by admin on December 20, 2017, 11:52:33 AM »
Thanks for the update. Can you please tell me if you have any Shell Context Menu Extensions installed on those machines, or any thumbnail handler... anything that is in Windows's File Context menu that is not part of the original Windows installation?
Bugs / Re: Getting consistent bluescreens, "wcifs.sys failed"
« Last post by MaxusValtron on December 19, 2017, 06:16:44 PM »
It's almost certainly OC, as I had the problem on three different computers that previously had no blue screen errors and didn't have any when OC was not running. Between the three computers I had about 20 blue screen errors, all while OC was running.

The good thing is that the ClickOnce version appears to be working perfectly, and hasn't given me any errors at all in the last few days. You were exactly right. I'm not sure what part of my configuration was causing that problem with the UWP isolation, but I'm glad it's resolved!

Thanks for the quick response, and keep up the good work.
General / Re: How to open multiple files
« Last post by photoflash100 on December 19, 2017, 12:36:51 PM »
Fantastic! Thanks, that works! Saves me a LOT of time!
Bugs / Re: Getting consistent bluescreens, "wcifs.sys failed"
« Last post by admin on December 17, 2017, 10:10:29 PM »
Are you sure it is related to OC?
This is the first time I have heard of wcifs and seeing that it is related to "Windows Container Isolation" it could be something to do with UWP apps. You can try regular ClickOnce installer version from
It is the same version but it is not packaged as an app
Pages: [1] 2 3 ... 10