Maximum Path Length Limitation error in beta build but registry is set for longer length.

Hi. I am running Windows 11 Pro 64-bit, Version 22H2 (OS Build 22616.100)

I first tried Apps & Software, here (

Software problem

Hi. I am running Windows 11 Pro 64-bit, Version 22H2 (OS Build 22610.100). Today I cannot run my backup software, Oops Backup by Alberto. Odd thing is the software backs up, but I cannot open the software to search for a deleted file. I realize the software was written long ago but worked fine...

www.elevenforum.com

), but now feel the issue is within the Win 11 beta build. A post suggested checking the registry (Maximum Path Length Limitation) to turn on extending the max file length. I found everything in the registry was all set for long file names so why I get this error is confusing. I don't have a clue what's wrong.

BTW - the software giving the error is an older program but has always worked fine over the many Windows OS changes.

Below is the error & the text.

All suggestions are appreciated.




See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.



************** Exception Text **************

System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

at System.IO.Path.SafeSetStackPointerValue(Char* buffer, Int32 index, Char value)

at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)

at System.IO.DirectoryInfo..ctor(String path)

at Wormhole.Manager.ControlPanel.BackupFoldersReviewPanel.LoadModules()

at Wormhole.Manager.ControlPanel.frmControlPanel..ctor()

at Wormhole.Manager.ControlPanel.frmControlPanel..ctor(Boolean BrowseMode)

at Wormhole.Manager.frmManager.ShowBrowserForm()

at Wormhole.Manager.ControlPanel.frmQuickLaunch.btnBrowseSnapshots_Click(Object sender, EventArgs e)

at Wormhole.Manager.Common.Controls.AltaroLargeButton.pbIcon_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Label.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)





************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

----------------------------------------

OopsBackup

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.exe

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

OopsBackup.UICommon

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.UICommon.DLL

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

OopsBackup.Common

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.Common.DLL

----------------------------------------

OopsBackup.CommArch

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.CommArch.DLL

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

zgkxxzbi

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Web.Services

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll

----------------------------------------

OopsBackup.SystemController

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.SystemController.DLL

----------------------------------------

dtfet2b9

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

OopsBackup.CommArch.XmlSerializers

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.CommArch.XmlSerializers.DLL

----------------------------------------

zu6bbknp

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Management

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll

----------------------------------------

OopsBackup.Remoting

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/OopsBackup.Remoting.DLL

----------------------------------------

System.Runtime.Remoting

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

4n466u9o

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

ovi1lvjz

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Web

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.9160 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll

----------------------------------------

Altaro.Controls

Assembly Version: 3.0.45.0

Win32 Version: 3.0.45.0

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/Altaro.Controls.DLL

----------------------------------------

dotnetCHARTING.WinForms

Assembly Version: 5.3.3532.18313

Win32 Version: 5.3.3532.18313

CodeBase: file:///C:/Program%20Files%20(x86)/Altaro/Oops!Backup/dotnetCHARTING.WinForms.DLL

----------------------------------------

mqv1d-ah

Assembly Version: 3.0.45.0

Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------



************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.



For example:



<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>



When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

I doubt there is any solution. Long filenames have never worked properly.

Far simpler to just ditch an old backup tool and use a nice shiny new one

You do not say what is being backed up i.e
is it just data, or image backups.

cereberus said:

I doubt there is any solution. Long filenames have never worked properly.

Far simpler to just ditch an old backup tool and use a nice shiny new one

You do not say what is being backed up i.e
is it just data, or image backups.

Click to expand...

You responded to my other post. Thanks again.

This problem was not present in Win 11 until I tried the Win 11 beta version. And, yes, it's an older program I use for backup - Oops.

AOMEI looks to a good backup. But I don't want to give up & pay $100 for 2 PCs just yet. I'm using a trial version of AOMEI now but see no advantage over Oops; that is, if Oops will ever work properly again.

The odd thing is Oops will backup anytime I open my backup drive. And I can browse the files directly on the HDD & retrieve what I need. What I can't do is open the Oops app & use the app software to retrieve data. When I try to open the app is when I get the long file name error. I'm guessing that long file name is the Oops product key which was extremely long.

GARoss said:

You responded to my other post. Thanks again.

This problem was not present in Win 11 until I tried the Win 11 beta version. And, yes, it's an older program I use for backup - Oops.

AOMEI looks to a good backup. But I don't want to give up & pay $100 for 2 PCs just yet. I'm using a trial version of AOMEI now but see no advantage over Oops; that is, if Oops will ever work properly again.

The odd thing is Oops will backup anytime I open my backup drive. And I can browse the files directly on the HDD & retrieve what I need. What I can't do is open the Oops app & use the app software to retrieve data. When I try to open the app is when I get the long file name error. I'm guessing that long file name is the Oops product key which was extremely long.

Click to expand...

The free version is fine. You have downloaded wrong version. Of course the free version is less feature rich than the paid (trial) version but still good enough for most users.

Hi there

while most apps are still using essentially the "Windows explorer" API which still limits long path / file names to 266 chars some modern apps such as FileZilla use the new internal API which DOES allow long file / path names -- you need to enable the feature somewhere in the registry though --forgotten where at the moment but it's "do-able".

Cheers
jimbo

jimbo45 said:

Hi there

while most apps are still using essentially the "Windows explorer" API which still limits long path / file names to 266 chars some modern apps such as FileZilla use the new internal API which DOES allow long file / path names -- you need to enable the feature somewhere in the registry though --forgotten where at the moment but it's "do-able".

Cheers
jimbo

Click to expand...

Thanks, jimbo. But as I mentioned, every registry location such as in the image, were already set for longer file names & the app still errors.

GARoss said:

Thanks, jimbo. But as I mentioned, every registry location such as in the image, were already set for longer file names & the app still errors.

Click to expand...

Hi there

@GARoss
It doesn't matter if that bit is set if the API used is still calling the "base File explorer" API.

For example filezilla shows perfectly Very long file names from my NAS server == Filezilla running on Windows.
It's whether the app uses the old or new API. !!!!!





Cheers
jimbo

jimbo45 said:

Hi there

@GARoss
It doesn't matter if that bit is set if the API used is still calling the "base File explorer" API.

For example filezilla shows perfectly Very long file names from my NAS server == Filezilla running on Windows.
It's whether the app uses the old or new API. !!!!!

Click to expand...

jimbo45 said:

Cheers
jimbo

Click to expand...

Thanks,
I'm guessing old APL as I purchased the app more than 10 years ago.