I would try restarting Lectora with the “Run as Administrator” option. Then try the update again. If that doesn’t work, download the file from our website and run it that way (http://trivantis.com/service-pack-downloads/).
“Run as Administrator”
Make sure Lectora is closed.
Right-click the Lectora shortcut on your desktop or in the Start menu.
Choose “Run as Administrator” from the context menu.
Agree to the Windows UAC dialog or enter a username/password if required.
The Known Issues list contains bugs that we’ve identified, tested, and confirmed. Those bugs are all scheduled to be fixed in one of our future releases. So bugs only appear on that list while we’re working on fixing them and they are taken off when we release a service pack that fixes them.
Thanks. I was one of the ones who reported it. Only workaround so far is to put in equals or doesn’t equal the exact answer to the question. For me, this is pretty time-consuming though as it’s a variable I heavily rely on in every test I created.
The auto-update for Lectora v16.2 was pulled after we found the issue. It was then turned back on when we released v16.2.1 so that any customers who had gotten v16.2 before we pulled it could get the new update with the fixes.
You can always opt out of the auto-update when it pops-up and you can also go into the Lectora Preferences and disable it entirely.
If you need to roll-back to v16.1.2 please use the “Submit a support ticket” button on the right side of this page. We can send you a download link for any of the previous versions.