Re: myQTH changed on most QSO's
+ AA6YQ comments below
The genesis of my problem was when my computer became useless last autumn. Win10 ran a troubleshooter and advised me to do their wipe and reload. That gets rid of all applications but leaves the data files.
The problem started when TQSL stopped working. Apparently, TQSL won't reload certificates onto a "different" computer.
+ You can't effectively move e a Callsign Certificate file (.tq6) from one computer to another unless you also move the Callsign Certificate's "private key". TQSL provides a easy means of moving all Callsign Certificates, Station Locations, and Settings in a single file from one computer to another; see
Since it has a new OS build, to TQSL, this is a "different" computer.
+ No, it's computer whose private keys were deleted by the Windows "wipe and reload" process.
I got only the certificate for my latest call and QTH. When I was trying to fix my requested QSO's in LoTW, when I updated and uploaded to LoTW, it caused everything to be overwritten as W1ES and QTH as Graham.
I have asked Bart at LoTW to send me new certificates.
When I get the new certificates, am I correct in thinking that I will have to make the mass change per the instructions, then upload to LoTW again?
+ No. There is no "mass change" to make, and no need to re-submit anything to LoTW.
+ If you have more than one "My QTH" defined in DXKeeper, it would be a good idea to ensure that each logged QSO specifies the correct "My QTH". This can be accomplished by filtering the Log Page Display to contain QSOs within a date range, and en masse modifying the "My QTH ID" of all of those QSOs to the correct value. Be sure to backup your log before undertaking this process, and don't hesitate to ask for help if you need it.