FTP settings gone after upgrade to Windows 10 OS

[ykhabins]

I had Windows 7 OS and TC 9.0a installed on my machine.
In preparation to upgrade the OS, I saved on a side the entire directory c:\Users\<user>\AppData\Roaming\GHISLER\*.ini

The PC was upgraded to Windows 10 Pro OS.
I reinstalled the same TC 9.0a
Copied all configuration *.ini files to the same location: c:\Users\<user>\AppData\Roaming\GHISLER\*.ini

All previous settings were picked up, but all FTP configuration settings are gone. Net => FTP Connect... dialog box window shows not a single entry.

TC's Help => About Total Commander... shows the same location in INI-files: c:\Users\<user>\AppData\Roaming\GHISLER\*.ini

The wcx_ftp.ini is there on a file system. Its size 1558 bytes. It is encrypted, so I cannot manually recover the FTP settings...

So how to restore "invisible" FTP settings?

[Horst.Epp]

If you have a copy of the old wcx_ftp.ini
why don't you just copy it over to the expected place ?
May be you had a portable installation on which the file was in TC program dir.

[Dalai]

The wcx_ftp.ini is there on a file system. Its size 1558 bytes. It is encrypted, so I cannot manually recover the FTP settings...

I highly doubt that the whole file is encrypted, because if it were, TC wouldn't be able to read its contents. Now that I think about it, that seems to be exactly what happens. I suspect that your wcx_ftp.ini got corrupted, so I'd do what Horst suggested: copy the file from a backup. If you don't have one, well ... (no comment).

Regards
Dalai

[ykhabins]

The wcx_ftp.ini is there on a file system. Its size 1558 bytes. It is encrypted, so I cannot manually recover the FTP settings...

I highly doubt that the whole file is encrypted, because if it were, TC wouldn't be able to read its contents. Now that I think about it, that seems to be exactly what happens. I suspect that your wcx_ftp.ini got corrupted, so I'd do what Horst suggested: copy the file from a backup. If you don't have one, well ... (no comment).

Regards
Dalai

The entire wcx_ftp.ini is encrypted.
I already copied wcx_ftp.ini from the backup.

My guess, OS change affected encryption/decryption.
That's why TC cannot decrypt wcx_ftp.ini file anymore.

Any other ideas how to resolve the issue?

[Horst.Epp]

The wcx_ftp.ini is there on a file system. Its size 1558 bytes. It is encrypted, so I cannot manually recover the FTP settings...

I highly doubt that the whole file is encrypted, because if it were, TC wouldn't be able to read its contents. Now that I think about it, that seems to be exactly what happens. I suspect that your wcx_ftp.ini got corrupted, so I'd do what Horst suggested: copy the file from a backup. If you don't have one, well ... (no comment).

Regards
Dalai

The entire wcx_ftp.ini is encrypted.
I already copied wcx_ftp.ini from the backup.

My guess, OS change affected encryption/decryption.
That's why TC cannot decrypt wcx_ftp.ini file anymore.

Any other ideas how to resolve the issue?

So you had an OS encrypted user volume and now you can't decrypt files from an old backup ?

[Dalai]

TC doesn't encrypt wcx_ftp.ini because it couldn't read anything from it if it did. This is also true for the passwords saved in this file, even when they're protected by the master password. It's still just an .ini file with its sections, keys and values, like this:

Code: Select all

[General]
e-mail=abcd@aol.com
ConnectRetries=10
WaitDelay=5
transfermode=I

[connections]
1=Hardware-Hersteller|ASUS|ASUS de

.

I still think that the file got corrupted, not encrypted, because which program could have done that? Maybe ransomware, that's the only thing I could think of, but since you still have your wincmd.ini...

And, as I said: If you don't have any backup of this file, well, there's nothing any of us could do about it.

Regards
Dalai

[ykhabins]

Upon further investigation it was revealed that the wcx_ftp.ini got corrupted.

Unfortunately, I have to re-create all FTP connections from scratch.

Thanks to all who replied with the answers in this post.

[hlloyge]

I would suggest to further investigate why the file got garbled, to avoid additional surprises.

[Dalai]

I would suggest to further investigate why the file got garbled, to avoid additional surprises.

Indeed. Perhaps other files have been corrupted, too.

Check the file-system (chkdsk /f), check the drive's health (SMART values), maybe even check your memory (MemTest86+).

Regards
Dalai