Lansweeper support has confirmed that this is a known bug in v11.1.1.3. In their words:
This is a known issue, and it has been escalated to our development team as a bug. A fix for it will be in a future release. Unfortunately, there is no estimated release date. We recommend checking our changelog when a new version is released to ensure this fix is included (LAN-15899). You can enable the update check in the Lansweeper web console under Configuration\Your Lansweeper License to be notified of any new releases.
You can find our changelog here: https://www.lansweeper.com/changelog.aspx
No other information seems to be forthcoming, so I guess the options are to attempt a rollback, or wait for the next release that will hopefully address the issues.
