IgniteRemote v1.6.26

Fixed: the last update blocker

The installer's own log — now sent to us automatically — captured the failure word for word:
GM's Techline Connect keeps a proxy component running that holds our J2534 file open. Windows'
"close the apps using these files" mechanism could not close it, and a silent update answered
its own question with Abort and rolled everything back.

That mechanism is now off. The installer handles busy files itself: parts of IgniteRemote are
closed properly, and a file held open by someone else's software is renamed aside rather than
deleted — Windows permits exactly that — so the new file always lands. Software that was open
during an update keeps running on the old copy until it restarts, which is the same approach
Windows Update uses.

Updates no longer require closing anything, GM software included.

Nothing starts recording on update

Unchanged: recording is off on every computer and stays off until an owner completes the
attestation in the console and switches it on for that specific computer.