Windows assets stuck in scanning queue in 11.1.1.3

[WuGe]

Since the update to v11.1.1.3 we have 398 windows assets stuck in the scanning queue.
They are stuck in the queue and seem to be never scanned or removed from the queue.
Before the update to v11.1.1.3 we did not have that problem.
We updated from v10.6.2.0.
How to get rid of that?
Rebooting the lansweeper server did not solve the problem.
Manually clearing the queue is possible but these assets show up as stuck in the queue at some point again.

[jduke_halls]

Thanks to @jgauthier1986 for replying in the other thread that version 11.1.2.1 is out.  It fixed my issue. It may fix yours too:

https://www.lansweeper.com/update-lansweeper/

[WuGe]

After I manually emptied the scanning queue a couple of days ago today I endet up again with 450+ stuck assets in the scanning queue that are not processed.
That version 11.1.1.3 seems totally broken with the major problems that are occouring.
I hope there will be a fix for all the problems very soon or a way to roll back to a previous version.

[Mister_Nobody]

Could you show output

Select Top 1000000 tblassets.AssetID,
  tblassets.AssetName,
  tblassets.IPAddress,
  tblassets.Userdomain,
  tblassets.Username,
  tblassets.oscode,
  tblassets.memory,
  tblassets.Processor,
  TsysWaittime.CFGname,
  TsysLastscan.Scantime,
  TsysLastscan.Lasttime,
  TsysWaittime.Waitdays
From tblassets
  Inner Join TsysLastscan On tblassets.AssetID = TsysLastscan.AssetID And
      TsysLastscan.Scantime > 5 And TsysLastscan.Lasttime > GetDate() - 7
  Inner Join TsysWaittime On TsysLastscan.CFGcode = TsysWaittime.CFGCode
Order By TsysLastscan.Scantime Desc

[WuGe]

Shure. That report gives me back 26 assets:

[ErikT]

Hi there,

Check out this blog, it might be just what you are looking for. 

Seeing your scanning queue stuck at the same asset... - Lansweeper Community - 61291

[WuGe]

Thank you. But I do think none of that in the blog is the issue as far as I can see.
The problem seems to be related to the update because before the update to v11.1.1.3 we did not have that problem.
I opened a support case meanwhile.