This version wants to update to 1.6.3 (the current) at startup, and when after updated, the restart fails because of the hardcoded location of a CSLID file that is not properly written to the usb location (normally would be written to the reg of the OS).

Perhaps all U3-installed apps that auto-upgrade or try to should be made to NOT auto-anything - unless the url of the upgrade for U3 programs are available at U3, and then update through the U3 installer?

Hmm...I'd expect a Maxthon user to know his options (pun intended - there's also an option to turn off auto-update), but here's what I did: d/l the non-U3 version, and you have some more files on the root folder of Maxthon - replace everything and you're good to go. Worked for me with future updates as well (since now you'll already get the latest version anyway...;)
Oh, and to whom concerns - I KNOW the executables were initially different, even for the same version numbers (I mean different between the U3 and non-U3 versions), and I was worried that something would fail so I backed up everything, but all seems very fine and portable (since Maxthon is pretty portable to begin with anyway).
The curious people might already have noticed that U3 launches Maxthon.exe with the "removable" switch (seen through a process explorer) which probably gives it its portable magic (i.e. NOT having a proper documents/pictures saving folder...grrr!)