Hi,
It could be that BESClient.exe (or one of its .dll dependencies) is not compatible with some other Windows shared libraries.
Problem is that when running BigFix Client as a service any potential error popup will be swallowed as there is no UI access.
Thus, I'd start with manual run of '..\BES Client\BESClient.exe' executable.
Does Windows complains with anything ?
If not, check the exit code (echo %errorlevel%).
If the above will not give any hints, Process Monitor (https://learn.microsoft.com/en-us/sysinternals/downloads/procmon) allows to verify the executable load & processing.
Play with Process Monitor is on a tedious side but sometimes inevitable...
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------