Lansweeperservice.exe crashes after KB5068787 installation

[Mago_Fab]

On a fresh new Windows Server 2022 (21H2) configured as a scan server, the Lansweeperservice.exe service is constantly crashing.

Here what I have in the event viewer:

Faulting application name: Lansweeperservice.exe, version: 12.6.0.11, time stamp: 0x67110000
Faulting module name: coreclr.dll, version: 8.0.1124.51707, time stamp: 0x67115e10
Exception code: 0xc0000005
Fault offset: 0x00000000001c7b0e
Faulting process id: 0x1c94
Faulting application start time: 0x01dc5c0623b1ddc4
Faulting application path: C:\Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe
Faulting module path: C:\Program Files (x86)\Lansweeper\Service\coreclr.dll
Report Id: a99d6493-b23c-45bd-aa47-1dc7ed123f43
Faulting package full name:
Faulting package-relative application ID:

********************************

Prior to this crash, there is a .Net crash in the event viewer:

Application: Lansweeperservice.exe
CoreCLR Version: 8.0.1124.51707
.NET Version: 8.0.11
Description: The process was terminated due to an unhandled exception.

***************
I searched and only found a similar discussion here:
https://developercommunity.visualstudio.com/t/Windows-update-makes-NET-48-program-cr/11000623?jesa=

***************
The problem is solved as soon as I uninstall the KB.
I have a second exact same server which is not affected after the KB installation...

Is anyone else having this issue?

[Mago_Fab]

Thanks for your reply.
The virtual server was migrated to a newer infrastructure and the Lansweeper service seems to be stable now. (Even if it also crashed a few times on the new server)

It could have been a performance issue caused after the update as the event viewer indicates memory problems causing the .Net and LS service to crash and I know the memory (only 4 Gb) is always used almost entirely on this server.

I don't think the memory of the previous server was corrupted, I just guess the performance or memory management is now better on the new infrastructure.

[DavidPK]

Hello there! 

I believe this is something we can maybe pass on to our development team and something that we can document f or our internal documentation. 

Our tech support team should be able to assist you with this.  Please open a ticket in our support portal.

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.