I went to test TTDXC 2.8.6 -- I put it in my TTD folder, and ran it, and it quite helpfully said "Unable to create switches.xml info file. TTDXC will download the info file for TTDPatch 2.0 rev 1 now."
I'm not quite sure what it's smoking there, because it didn't even *try* to start ttdpatchw.exe (I know this because my firewall allerts me when unknown programs try to start other programs.) Had it done so, TTDPatch would have done as TTDXC requested, and generated a proper XML file. (This was verified by running ttdpatchw -!S- from a command line.)
If I manually generate switches.xml, TTDXC deletes it and then reports that switches.xml couldn't be generated, as above.
The ttdpatchw.exe in my folder, as reported by -!T-, is "TTDPatch V2.6 alpha 0 r1141mod (Windows)".
The same basic problem is exhibited with my local 2.5 build. (version "TTDPatch V2.5 beta 8 r1135mod (Windows)")
That's related to a version detection problem. You didn't mention how does TTDXC detect your TTDP version at all, that would be helpful.
If TTDXC does not create the XML, it's because the TTDP exe filesize corresponds to an old version without XML, and therefore it will download the one for 2.0 rev 1 for backwards compatibility. Now, I recently changed the function that retrieves file sizes with one native VB function, it seems that wasn't a good idea.
Here I attach a new TTDXC 2.8.6 version which uses the system's GetFileSize API to query file size. Also, the existant switches.xml won't be deleted it TTDXC cannot run the version detection, so switches will be created using the local XML even if version detection fails.
Wile E. Coyote wrote:
It doesn't update back to 2.8.5 for me.
That's all I can say based on the extensive info your provided. I won't start with the correct bug report speech, but you could at least mention what the heck happened when you received the new version notification after Live Update.