I'm running KMyMoney on a new laptop running Windows 10. I'm unable to create a backup. I get an error message. when I mount the backup location, I no longer get an error message but still no backup. Also, this action appears to keep the program from closing down.

Please specify which version of KMM you are running, and where you got it. Also, to where are you trying to save the backup? Local drive, local USB drive, network SMB share, other type of network share? It is NOT necessary to click the mount first (that has been removed from recent versions) but if you are saving to a network share, it does need to be mounted (by you) before trying the backup.

ostroffjh wrote:Please specify which version of KMM you are running, and where you got it. Also, to where are you trying to save the backup? Local drive, local USB drive, network SMB share, other type of network share? It is NOT necessary to click the mount first (that has been removed from recent versions) but if you are saving to a network share, it does need to be mounted (by you) before trying the backup.

I'm running KMyMoney Version 5.0.6 in Windows 10. For the Windows installation, I downloaded from: https://download.kde.org/stable/kmymoney/5.0.6/

I'm saving to the local folder. I've done this in the past when running in Linux with no problems.

It's still not clear exactly what you're trying and what's happening. I assume you are selecting the menu item File/Backup. If you're trying to backup to the local hard drive, don't click the mount checkbox) but do select the directory in which to create the backup. Does that work? Then when you hit the button to actually save, what happens? What do you mean that it appears to keep the program from closing down?

ostroffjh wrote:It's still not clear exactly what you're trying and what's happening. I assume you are selecting the menu item File/Backup. If you're trying to backup to the local hard drive, don't click the mount checkbox) but do select the directory in which to create the backup. Does that work? Then when you hit the button to actually save, what happens? What do you mean that it appears to keep the program from closing down?

Thanks so much for the kind answer. I'll try to be more specific. However, you got most of it correct.

When I create a backup, not checking the mount checkbox gives me the error message: Error copying file to device. Checking the mount checkbox takes the program through the motions of backing up, but does not result in a backed up file. The directory file path is correct.

WAIT WAIT WAIT!!!

I found the problem.

the program is placing an extra "\" where it is not needed.

Instead of giving me the path: C:/Users/marks/Documents/KMyMoney

It's giving me a path with an extra slash thrown in at the very beginning: /C:/Users/marks/Documents/KMyMoney

No matter where I navigate, this extra slash is being inserted by KMyMoney.

Okay, solved!:) Perhaps this is a bug?

There have been several related bugs fixed recently. Most fixes are older than your version, but the specific one about the extra leading slash will be fixed in 5.1, set to be released very soon. Unfortunately, a Windows version is likely to be delayed beyond that. You might want to try the latest successful version from https://binary-factory.kde.org/job/KMyM ... tly_win64/

ostroffjh wrote:There have been several related bugs fixed recently. Most fixes are older than your version, but the specific one about the extra leading slash will be fixed in 5.1, set to be released very soon. Unfortunately, a Windows version is likely to be delayed beyond that. You might want to try the latest successful version from https://binary-factory.kde.org/job/KMyM ... tly_win64/

This is not a problem whatsoever. It's my fault that I didn't see it immediately. But, thanks to your attention and patience in discussing this, you allowed me to walk through the process whereby I then identified the problem. Thank you.

If the error comes up, I'll simply edit the path. All good. Hopefully, this thread will help someone else who might be experiencing the same little glitch.