To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

Software Updater Google Chrome 114.0.5735.110

DiAmi W/ Alumni Posts: 31 Junior Protector


Software Updater has a problem with the Google Chrome 114.0.5735.110. This version of Chrome was updated with WithSecure

If I scan host for the missing updates, this version again appears under "Missing Updates" list.
And this behavior is on many hosts…

And from the management portal I see this. Meanwhile the latest version has been already installed.

Best Answer

  • Sethu Laks
    Sethu Laks W/ Partner, W/ Staff, W/ Moderator Posts: 250 Moderator

    Hi @DiAmi

    Thank you for reaching out WithSecure Community,

    It's hard to say without checking the wsdiag logs. Please ensure that the chrome is not running on the problematic client machines during the software update installation.

    You may change the following setting to allow the feature to close the application always before software update installation kicks in via Profile Editor:

    For Elements Endpoint Protection products:

    a) Via Automated tasks

    1. Log in to the Elements Endpoint Protection portal
    2. Click Profiles tab
    3. Go to Automated tasks
    4. Click the Add task option
    5. Enable the new rule
    6. Choose the following update installation type

    Install critical and important security updates

    7. Place a checkmark on the 'Terminate running applications' option
    8. Set the task schedule
    9. Click Save and Publish

    b) Via push install updates operation

    1. Log in to the Elements Endpoint Protection portal
    2. Go to the Devices tab
    3. Place a checkmark on the target device
    4. Click Install Software Updates operation at bottom menu
    5. Choose the software update categories
    6. Place a checkmark on the 'Close running applications' option
    7. Click Install button

    Note that all unsaved work will be lost if the software is closed.

    If the issue still remains, the potential root cause could be that this update was rolled out through a different source (SCCM, etc.) already, and hence, it is no longer detected as missing again by SWUP.

    Another potential scenario that we can think of, is that the Windows Update Agent could have started to download this update, or Windows changed some settings during the scanning (by Windows Update Agent, etc.), and this could affect SWUP

    We will also suggest you look into the Windows Update settings, to find out whether the update is listed under Update Status, or Update History.

    I would be happy to assist you any further if needed!



This discussion has been closed.