BESclient.exe crashing

Usage and Config Platform
1

Anyone else been noticing BESClient.exe crashing on 11.0.4?

We have a case open.

Symptoms:

Message : Faulting application name: BESClient.exe, version: 11.0.4.60, time stamp: 0x67f7f81d
Faulting module name: ntdll.dll, version: 10.0.17763.7553, time stamp: 0x13bce370
Exception code: 0xc0000374
Fault offset: 0x000e0703
Faulting process id: 0x17fc
Faulting application start time: 0x01dc17b393b8911d
Faulting application path: C:\Program Files (x86)\BigFix Enterprise\BES Client\BESClient.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a984ff31-c689-4a44-aaf9-a0286114a593
Faulting package full name:
Faulting package-relative application ID:

2

I’m running 11.0.4 on my Win10 22H2 build with no issues. Looks like you have an older version of Win10 though, build 1809 so it may not have been validated for use on older Win10 builds and you may need to use an older agent perhaps?

If your using the 2019 LTSB build, equivalent to build 1809, then maybe there are some issues that didn’t arise in testing.

3

Unfortunately, that version also applies to server editions, which in this case is 2019 LTSC.

4

I installed a clean build of 2019 LTSC and installed 11.0.4 agent with no errors appearing. Patched it via Bigfix with 2021 Aug SSU and the 2025 Aug CU and rebooted once all complete and Bigfix client still appears to be operating with no errors. The ntdll.dll version is 10.0.17763.7678.

I can try and remove the update and try with last months CU, if thats what your patch level is

5

Please note, crash seems to happen only during client shutdown: @jbruns2017, am I correct?

6

I believe that is true, shutdown for whatever reason but not including manually.

7

Do you mean you are not able to reproduce the crash, if you manually shutdown the client? How are you experiencing the crash then, by rebooting the server? Is it possible the OS does not give enough time to the client to stop itself and kill it?

Thanks.

8

When L3 solves this, I will advise. Restarting the client from restarts is where it is suspected to be coming from but not 100%.

Manually stopping the service does not raise the issue.