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 with Windows 10 & I'm sure I have run it since switching to Windows 11. Could be a Windows beta issue (?).

Anyways, I've attached a screen capture & also printed the error details. It mentions a file name that's too long. Not sure how to get around that.

Appreciate suggestions.



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.

Could be a Windows beta issue (?).

Click to expand...

Very possible. Is your test version of Win11 installed on a fully compatible machine or the "customized" install used on older machines? I was in the Technical Preview when it first came out and heeded the warning to Not install on an only machine or production machine as things may not work as desired. Old software sometimes won't work as desired because the authors/producers don't keep it up to date as often as the test versions of Windows come out.

Berton said:

Very possible. Is your test version of Win11 installed on a fully compatible machine or the "customized" install used on older machines? I was in the Technical Preview when it first came out and heeded the warning to Not install on an only machine or production machine as things may not work as desired. Old software sometimes won't work as desired because the authors/producers don't keep it up to date as often as the test versions of Windows come out.

Click to expand...

When I first tried to install Win 11 it said my Ryzen 7 1700 CPU wasn't compatible. I upgraded the CPU to a Ryzen 9 3900X 12-core, put the latest BIOS on the MB & Winn 11 installed. That was about 6 months ago & I have used the backup software since then.
Probably something to do with the BETA version which was installed recently.

GARoss said:

When I first tried to install Win 11 it said my Ryzen 7 1700 CPU wasn't compatible. I upgraded the CPU to a Ryzen 9 3900X 12-core, put the latest BIOS on the MB & Winn 11 installed. That was about 6 months ago & I have used the backup software since then.
Probably something to do with the BETA version which was installed recently.

Click to expand...

I hate to go back to earlier Versions and Builds but sometimes it's best if wanting to run a specific program. I have a graphics program I've used for 20 years that now won't work on Win10 and they changed to a SaaS model anyway so I may install what I have on a Dell with Win7 to make it useful again.

You might want to check into using a more dependable, better known backup solution.

glasskuter said:

You might want to check into using a more dependable, better known backup solution.

Click to expand...

I have looked as of today. I had no reason to doubt Oops Backup by Alberto as it has always been dependable - until today. Back when Win 10 was new, I needed to install an older version of NET Framework to get Oops to work. That was a sign it was old, I guess.

Any suggestions?

I use Macrium myself. The free version is very good.

GARoss said:

I have looked as of today. I had no reason to doubt Oops Backup by Alberto as it has always been dependable - until today. Back when Win 10 was new, I needed to install an older version of NET Framework to get Oops to work. That was a sign it was old, I guess.

Any suggestions?

Click to expand...

Oops may not be the problem and the Win 11 version may not be the problem.
However, they may be a problem when run together.

From MS's point of view, Oops may not have a large enough market share for them to keep caring about.
Try another backup software, and see if that works.

Macrium Reflect and Aomei Backupper, both have free versions.
See if either of those work. At worst, you'll then have another piece of information to work with.

Maximum Path Length Limitation

Alex__ASSR said:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

Maximum Path Length Limitation

Click to expand...

Thanks. I'm not confident changing the registry but appreciate your post. Too dangerous for an amateur.

Ghot said:

Oops may not be the problem and the Win 11 version may not be the problem.
However, they may be a problem when run together.

From MS's point of view, Oops may not have a large enough market share for them to keep caring about.
Try another backup software, and see if that works.

Macrium Reflect and Aomei Backupper, both have free versions.
See if either of those work. At worst, you'll then have another piece of information to work with.

Click to expand...

Oops has been a great backup but probably, as suggested, to update my backup with updated software. Alberto stopped selling Oops & hasn't updated it for many, many years.

GARoss said:

Oops has been a great backup but probably, as suggested, to update my backup with updated software. Alberto stopped selling Oops & hasn't updated it for many, many years.

Click to expand...

Backup software has to be 100% reliable and kept up to date. A friend of mine was still using Norton Ghost on old pc, but it failed to work on new pc. Reaaon is simple - Norton Ghost could not handle UEFI pcs.

GARoss said:

Oops has been a great backup but probably, as suggested, to update my backup with updated software. Alberto stopped selling Oops & hasn't updated it for many, many years.

Click to expand...

Yes. That's what I'm trying to say.
Obviously, MS can't keep up with ALL software.
So their best option is to keep up with the software with the biggest market share.

And I'm thinking that maybe Oops, doesn't make the list anymore.

Ghot said:

Yes. That's what I'm trying to say.
Obviously, MS can't keep up with ALL software.
So their best option is to keep up with the software with the biggest market share.

And I'm thinking that maybe Oops, doesn't make the list anymore.

Click to expand...

I am not sure MS really keep up to date with biggest market share. I think they just wing it.

Alex__ASSR said:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

Maximum Path Length Limitation

Click to expand...

Hi, I've tried every setting change in Maximum Path Length Limitation suggests. All settings in registry were previously set for Maximum Path Length.