Alex

It's encountering some invalid character in your password database. Unless you have some way to guess which of your entries might have some strange character in it, you will have to just narrow it down by taking a copy of your database and then deleting half the entries and try again. Then you will know which half has the offending entry. Repeat until it becomes clear which one is causing the problem. If you do identify it, it would be very helpful if you could post an example wallet which reproduces...

It will only show that message if it can't read that registry value, so if the value exists, something must be blocking it from reading it. Maybe a permissions issue? You could try running it as administrator, but apart from that I don't have any other suggestions.

It will look for the registry key HKEY_CURRENT_USER\Software\Ilium Software\eWallet and the value InstallDir. eWallet should populate that as part of its installation, but if that's not happening then I guess you could create it manually. Set it to point to the folder that has eWallet.exe in it. I'm away from my desk at present so can't try the 8.12 trial installer specifically to see if anything has changed, sorry.

You are using the wrong plugin. eWalletDataLiberator is compatible with v2.x, but not v1.x. However, it is not EWalletImport. That's a different plugin. eWalletLiberatedDataImporter.plgx is included in the eWalletDataLiberator.zip file.

This is the right thread. Please give the attached updated liberator tool v0.15 a try, I've recompiled it for .net 4.7.2. If it still doesn't work, then please try and create a minimal wallet that reproduces the error (without sensitive information in it) and I will investigate.

Not really sure what's going on here. Neither eWallet or Liberator require "System.Core, Version=2.0.5.0", both use version 4.0.0.0 (.net Framework 4.0). It does seem to be sync-related, though, so you might have been on the right track in disabling could sync. If you have any cloud sync configured for the wallet, try removing it. Otherwise, re-installing the .net Framework might potentially help: https://www.microsoft.com/en-us/download/details.aspx?id=17851

I haven't got Norton, so I can't say specifically. However, this executable is finding...

Please try the attached 0.13. This seems to be a problem on Windows 10, but I've...