Is anybody testing with Windows 10, version 1709, also known as the Fall Creators Update? I am noticing that every time I reboot by selectin the power button through the user interface and then selecting either reboot or shutdown, it generates a message in the application event log that says.
The following application attempted to veto the shutdown: BESClientUI.exe.
On some devices this has no noticeable effect. However, on other devices it causes the device to hang on shutdown
This is what displays. A user must click the âShut down anywayâ button or else it will hang there forever
If you kill the BESClientUI.exe process it reboots
I am able to consistently recreate the log file entry on every Windows 10 version 1709 device I have. The reboot hang issue is more sporadic. I am able to recreate this problem with several different version of BigFix
9.2.5
9.2.11,
9.5.3, and 9.5.7
I see this occur on various hardware, physical and virtual.
Iâd love to know if anyone else is seeing anything similar
Weâre seeing this issue as well. Luckily, we have Win10 1709 only in our testers group so far. But we have see it on physical (laptop & desktop) and virtual machines. To eliminate other variables, we even tested it with a fresh deployment of Win10 1709 â same result.
We have confirmed it on 9.5.6 and 9.5.7 clients as well.
Killing the BESClientUI.exe process before shutdown does âfixâ the issue.
My only guess is that Windows 10 is killing the BES Client service before it can unload any and all BESClientUI.exeâs or perhaps it used to be able to do so, but something is preventing it in the new update.
One workaround, which is not ideal but should work would be to have a scheduled task that fires on shutdown that kills any BESClientUI.exe
This needs to be addressed quickly. I canât see our site accepting this current state for BigFix. Anything that hinders a userâs experience is bad.
The information provided to the user just states that an application is preventing windows from shutting down, but no application info is available. This message scares the user and makes them think they are going to lose work. I canât go back to my users and tell them âNo, itâs ok, continue with a shutdown with almost no information as itâs probably a false-positive from BigFixâ as their response would be: âok, uninstall anything that is broken software thenâ, and they would be right.
We identified this issue and a few others during our qualification of Fall Creators Update, and are working on fixes. We will release a new agent that supports Fall Creators Update as soon as we can.
Has anyone encountered difficulties with installation of the agent (9.5.6 here) on Windows 10 1709? Some of my distributed IT groups are starting to run in to an installation problem and Iâm trying to isolate it. Itâs made a little more complicated because we wrap the msi in custom code to allow people to choose some initial settings, but itâs looking like the failure occurs during the actual msi installer process. Windows Application log indicates
Unexpected or missing value (name: 'PackageName', value: '') in key 'HKLM\Software\Classes\Installer\Products\3B3AFD518B6CE5C47AAC9305A909AA98\SourceList'
It appears that the fixlet to upgrade the relays is pulling 9.5.7.90 instead of 9.5.7.94⌠It it comes back as a not relevant.
Action Script is wrong.
Is the only supported version for Fall Creators the 9.5.7 version or does the 9.2.12 version also include the fixed agent? We have a few reports of machines having this issue but seems sporadic. Just trying to figure out upgrade timeline and what versions I can upgrade to (currently 9.2.9)
