Nope ... not shutting down, I watch the database console messages ... that's how I know that the Assets Changed State (and to expect the long validation) ... and b) I can see the validation actually occurring. Like I said, I watch TADDaemon like a hawk (and TrainzUtil for that matter, but those seem less important and once TADDaemon is shutdown, TrainzUtil will be too) ... I NEVER try to restart Trainz or CMP until I know TADDaemon is finished with it's previous shutdown. And why would it always occur on my Desktop then 2-3 days later (like clock work) occur on my Laptop (that's why I am pretty convinced this is part of DRM).
The exact steps are Launch CMP ... login fails (red message at bottom of CMP window) ... I don't check credentials, because I know they are correct, haven't changed ever ... shutdown CMP ... wait about 15-30 minutes for Assets tochange state (if it doesn't do this, no long validation) ... then TADDaemon finally shuts down ... relaunch CMP immediately ... or the next day (doesn't matter) ... if the next login succeeds, a large asset validation occurs (if it doesn't then things really get ugly) I don't mind a couple validations, after a download, no problems there. By the pretty much monthly huge validation is just painful. Should I not be shutting down after the login fails? I always wait for TADDaemon to do it's thing and completely shutdown before relaunching CMP ... would it help to not shutdown CMP quite so soon (is there something CMP needs to do?) ... I'd love to know the secret ... but again my fear is that it is DRM related and like you said, nothing can be done. Also, I almost never shutdown my computers. Desktop has battery back up, laptop obviously does [and it works] ... and if I do have to reboot, CMP/TADDaemon/etc, aren't running and it's typically just because of a windows update or similar.