none
Is not possibile to install KB2855265 - Update for Microsof Security Essential

    General discussion

  • Hey folks,

    we are experiencing problems installing the "KB2855265 - Update for Microsof Security Essential - 4.3.215.0".

    All other updates are installed correctly but this one remains pending on all our clients (W7 and WXP).

    I know that a "user input is required" but no popup or Windows are opened on user's session so the only way is to logon as administrator and install the update manually.

    Here below the setup of our Wsus' policy:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "WUServer"="http://192.168.1.9:80"
    "WUStatusServer"="http://192.168.1.9:80"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    "NoAutoRebootWithLoggedOnUsers"=dword:00000001
    "AUPowerManagement"=dword:00000001
    "IncludeRecommendedUpdates"=dword:00000001
    "AutoInstallMinorUpdates"=dword:00000001
    "RescheduleWaitTimeEnabled"=dword:00000000
    "UseWUServer"=dword:00000001
    "RebootRelaunchTimeoutEnabled"=dword:00000001
    "RebootRelaunchTimeout"=dword:000005a0
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000001
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000004
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:00000003

    Many thanks in advance

    Diego

    Tuesday, July 23, 2013 11:03 AM

All replies

  • Hola Diego,

    What is the Agent message in the WindowsUpdate.log file for this precise update ?

    You should find why it's still pending with user profile. As your AUOptions is set to the 4th option, it should install itself and just wait for a Shutdown with Start>Shutdown to complete.

    Thanks.

    TiGrOu.

    Tuesday, July 23, 2013 11:37 AM
  • I know that a "user input is required" but no popup or Windows are opened on user's session so the only way is to logon as administrator and install the update manually.

    Exactly! A logged on user must initiate the installation of this update.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, July 23, 2013 2:32 PM
    Moderator
  • What is the Agent message in the WindowsUpdate.log file for this precise update ?

    There won't be any Agent messages for this update, except the initial download when detected

    You should find why it's still pending with user profile. As your AUOptions is set to the 4th option, it should install itself and just wait for a Shutdown with Start>Shutdown to complete.

    Except that it doesn't install itself, for the very reason that was stated -- the update requires user interaction (it's not a silent/unattended) installation, and as such a logged on user must initiate the installation

    I do so wish that the announcement of this update had been a bit more forthcoming about this requirement, though. In fact, the announcement of the update stated something to the effect "you'll get this update just like you get Definition Updates".... which isn't quite true since Definition Updates can be automatically installed. This one cannot.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, July 23, 2013 2:36 PM
    Moderator
  • Nice to know.

    Thanks for this point Lawrence.

    TiGrOu.

    Tuesday, July 23, 2013 3:05 PM
  • Many thanks Lawrence. 

    Anyway, the standard users don't have any message/popup/Windows that allow them to install the update. Only the few colleagues that are administrators of their own machine are able to install the package, including me. 

    The result is that this update has been approved for the installation for several days but appears always as "downloaded" in the status coloumn of my wsus report.

    I've tried to change my wsus policy enabling "Allow non-administrators to receive update notifications" but I had no luck...

    Thanks in advance for your help

    Diego

    Wednesday, July 24, 2013 8:39 AM
  • Many thanks Lawrence. 

    Anyway, the standard users don't have any message/popup/Windows that allow them to install the update. Only the few colleagues that are administrators of their own machine are able to install the package, including me. 

    The result is that this update has been approved for the installation for several days but appears always as "downloaded" in the status coloumn of my wsus report.

    I've tried to change my wsus policy enabling "Allow non-administrators to receive update notifications" but I had no luck...

    Thanks in advance for your help

    Diego

    "AUOptions"=dword:00000004

    If I'm right, this setting is : 4 - Auto download and schedule the install".

    Specify the schedule using the options in the Group Policy Setting. If no schedule is specified, the default schedule for all installations will be everyday at 3:00 AM. If any of the updates require a restart to complete the installation, Windows will restart the computer automatically.

    You can also set this policy to avoid automatic restart while a user is logged on :

    No auto-restart with logged on users for scheduled automatic updates installations         

    Enabled

    And in the same time, this option will pop-up users that a restart is required as said in the GPM Edit options :

    If the status is set to Enabled, Automatic Updates will not restart a computer automatically during a scheduled installation if a user is logged in to the computer. Instead, Automatic Updates will notify the user to restart the computer.

    TiGrOu.

    Wednesday, July 24, 2013 9:45 AM
  • Thanks TiGrOu,

    I've already try this way but it doens't work: all other updates have been installed but the KB2855265 remains as "downloaded" but not installed.

    Obviusly, if I logon on that machine with admin credentials, I can choose to install the update by selecting it an the icon near the system clock.
    Wednesday, July 24, 2013 10:22 AM
  • From Windows Update Catalog

    Update for Microsoft Security Essentials - 4.3.215.0 (KB2855265)
    Last Modified: 7/8/2013
    Size: 789.8 MB

    Restart behavior: Can request restart
    May request user input: Yes
    Must be installed exclusively: No
    Requires network connectivity: No
    Uninstall Notes: n/a
    Uninstall Steps: n/a

    If users are not at least Power Users, they won't be able to install it as this patch is requiring action from them

    TiGrOu.

    Wednesday, July 24, 2013 11:15 AM
  • From Windows Update Catalog

    Update for Microsoft Security Essentials - 4.3.215.0 (KB2855265)
    Last Modified: 7/8/2013
    Size: 789.8 MB

    Restart behavior: Can request restart
    May request user input: Yes
    Must be installed exclusively: No
    Requires network connectivity: No
    Uninstall Notes: n/a
    Uninstall Steps: n/a

    If users are not at least Power Users, they won't be able to install it as this patch is requiring action from them

    TiGrOu.

    Oh, bad news! :-(

    This is the first time after several years using SUS and WSUS that I have this trouble.

    Do you know if exist any workaround?

    Wednesday, July 24, 2013 1:07 PM
  • This is the first time after several years using SUS and WSUS that I have this trouble.

    Microsoft Security Essentials is not licensed for use in a commercial environment.

    It is licensed for use in the home, and in home-based businesses.

    Having said that...

    On Windows7 systems this is a non-issue. All users on Windows7 systems have full rights to install updates. You need to instruct your users to navigate to Control Panel -> Windows Update and install the update. The update does not require a system restart.

    On WindowsXP systems, the user must be a local administrator. If they are not, the policy Allow non-admins to receive update notifications will grant a standard user the necessary privileges to respond to the Notification Icon and launch the installation of the update. HOWEVER, setting that policy will not grant the rights immediately, because the client must first do a GPRefresh to get the registry setting from policy, and then the WUAUSERV (Windows Update Agent service) on the client must be restarted in order to get the registry setting.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, July 24, 2013 4:28 PM
    Moderator
  • Of course, we are talking about a non-commercial enviroment.

    On Windows 7, I tried to navigate to Control Panel -> Windows Update and install the update with a standard user but I have a message: "It's necessary to provide administrator privilege".

    Could it depend on the fact that UAC is disabled?

    I'm thinking about install the update by deploying it via GPO: is it possible in your opinion? Or do you know if there is another way?

    Many thanks

    Thursday, July 25, 2013 9:05 AM
  • On Windows 7, I tried to navigate to Control Panel -> Windows Update and install the update with a standard user but I have a message: "It's necessary to provide administrator privilege".

    On the Windows7 machine, if you have that message, it's because you have enabled some other Group Policy setting that is restricting access, or the option "Allow all users to install updates" has been disabled in the WUApp "Change Settings" screen.

    You cannot install the update via GPO... it **REQUIRES** a local user to launch the application because the installer is INTERACTIVE.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, July 25, 2013 7:03 PM
    Moderator
  • Thanks Lawrence, 

    I've enabled the option "Allow all users to install updates" and now I see the relative flag into the Windows Update panel

    Now I have the error 80240020 after that the update has been downloaded and that Windows tried to install it.

    In the WindowsUpdate.log I have this message: "AU found no suitable session to launch client in"

    There are no other restricting policies about the users. 

    Any idea? 

    Thanks again

    Friday, July 26, 2013 11:03 AM
  • The error 80240020 is related to the non Administrator's user issue.

    It should be great for us if you copy-paste the WindowsUpdate.log complete.

    Thanks.

    TiGrOu.

    Friday, July 26, 2013 11:44 AM
  • Here you are:

    2013-07-26 15:08:00:281 332 e84 AU All updates already downloaded, setting percent complete to 100
    2013-07-26 15:08:01:155 332 bb0 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}]
    2013-07-26 15:08:01:155 332 bb0 AU  # WARNING: Install failed, error = 0x80240020 / 0x00000000
    2013-07-26 15:08:01:295 332 e84 AU All updates already downloaded, setting percent complete to 100
    2013-07-26 15:08:01:482 332 4f8 Agent *********
    2013-07-26 15:08:01:482 332 4f8 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2013-07-26 15:08:01:482 332 4f8 Agent *************
    2013-07-26 15:08:01:482 332 bb0 AU Install call completed.
    2013-07-26 15:08:01:482 332 bb0 AU  # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2013-07-26 15:08:01:482 332 bb0 AU #########
    2013-07-26 15:08:01:482 332 bb0 AU ##  END  ##  AU: Installing updates [CallId = {F7EBE7AA-CC63-4A5A-9037-8DABE62FA502}]
    2013-07-26 15:08:01:482 332 bb0 AU #############
    2013-07-26 15:08:01:482 332 bb0 AU Install complete for all calls, reboot NOT needed
    2013-07-26 15:08:01:482 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:08:01:482 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:01:482 332 e84 AU Getting featured update notifications.  fIncludeDismissed = true
    2013-07-26 15:08:01:482 332 e84 AU No featured updates available.
    2013-07-26 15:08:01:498 332 e84 AU All updates already downloaded, setting percent complete to 100
    2013-07-26 15:08:02:044 332 e84 AU All updates already downloaded, setting percent complete to 100
    2013-07-26 15:08:04:399 332 e84 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2013-07-26 15:08:04:415 332 e84 AU Triggering Offline detection (non-interactive)
    2013-07-26 15:08:04:415 332 e84 AU AU setting pending client directive to 'Install Complete Ux'
    2013-07-26 15:08:04:415 332 e84 AU Changing existing AU client directive from 'Progress Ux' to 'Install Complete Ux', session id = 0x2
    2013-07-26 15:08:04:431 332 e84 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:04:431 332 40c AU #############
    2013-07-26 15:08:04:431 332 40c AU ## START ##  AU: Search for updates
    2013-07-26 15:08:04:431 332 40c AU #########
    2013-07-26 15:08:04:805 332 40c AU <<## SUBMITTED ## AU: Search for updates [CallId = {794319F1-BD40-4F16-BA81-FC7812D4244A}]
    2013-07-26 15:08:04:805 332 b60 Agent *************
    2013-07-26 15:08:04:805 332 b60 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-07-26 15:08:04:805 332 b60 Agent *********
    2013-07-26 15:08:04:805 332 b60 Agent  * Online = No; Ignore download priority = No
    2013-07-26 15:08:04:805 332 b60 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2013-07-26 15:08:04:805 332 b60 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-07-26 15:08:04:805 332 b60 Agent  * Search Scope = {Machine}
    2013-07-26 15:08:04:836 332 e84 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:04:836 332 40c AU AU received handle event
    2013-07-26 15:08:58:391 332 b60 Agent  * Added update {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}.201 to search result
    2013-07-26 15:08:58:422 332 b60 Agent  * Found 1 updates and 74 categories in search; evaluated appl. rules of 1466 out of 3309 deployed entities
    2013-07-26 15:08:58:500 332 b60 Agent *********
    2013-07-26 15:08:58:500 332 b60 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-07-26 15:08:58:500 332 b60 Agent *************
    2013-07-26 15:08:58:703 332 bb0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {794319F1-BD40-4F16-BA81-FC7812D4244A}]
    2013-07-26 15:08:58:703 332 bb0 AU  # 1 updates detected
    2013-07-26 15:08:58:765 332 b60 Report REPORT EVENT: {4565B3BD-426F-4953-A151-A8B410E77646} 2013-07-26 15:08:01:155+0200 1 182 101 {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD} 201 80240020 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80240020: Update for Microsoft Security Essentials - 4.3.215.0 (KB2855265).
    2013-07-26 15:08:58:781 332 bb0 AU #########
    2013-07-26 15:08:58:781 332 bb0 AU ##  END  ##  AU: Search for updates [CallId = {794319F1-BD40-4F16-BA81-FC7812D4244A}]
    2013-07-26 15:08:58:781 332 bb0 AU #############
    2013-07-26 15:08:58:781 332 bb0 AU Featured notifications is disabled.
    2013-07-26 15:08:58:812 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:08:58:890 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:58:890 332 bb0 AU Auto-approving update for download, updateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}.201, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2013-07-26 15:08:58:890 332 bb0 AU Auto-approved 1 update(s) for download (NOT for Ux)
    2013-07-26 15:08:58:890 332 bb0 AU #############
    2013-07-26 15:08:58:890 332 bb0 AU ## START ##  AU: Download updates
    2013-07-26 15:08:58:890 332 bb0 AU #########
    2013-07-26 15:08:58:890 332 bb0 AU  # Approved updates = 1
    2013-07-26 15:08:58:937 332 bb0 AU AU initiated download, updateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}.201, callId = {0995994E-A8CF-42DF-9338-D50DF013226B}
    2013-07-26 15:08:58:999 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:08:58:999 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:58:999 332 bb0 AU AU setting pending client directive to 'Download Progress'
    2013-07-26 15:08:59:062 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:59:062 332 bb0 AU  # Pending download calls = 1
    2013-07-26 15:08:59:062 332 bb0 AU <<## SUBMITTED ## AU: Download updates
    2013-07-26 15:08:59:093 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:08:59:421 332 eb0 AU Getting featured update notifications.  fIncludeDismissed = true
    2013-07-26 15:08:59:421 332 eb0 AU No featured updates available.
    2013-07-26 15:09:00:169 332 eb0 AU Getting featured update notifications.  fIncludeDismissed = true
    2013-07-26 15:09:00:169 332 eb0 AU No featured updates available.
    2013-07-26 15:09:00:325 332 b60 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2013-07-26 15:09:00:325 332 b60 Report WER Report sent: 7.6.7600.256 0x80240020 0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD Install 101 Managed
    2013-07-26 15:09:00:325 332 b60 Report CWERReporter finishing event handling. (00000000)
    2013-07-26 15:09:00:357 332 b60 DnldMgr *************
    2013-07-26 15:09:00:357 332 b60 DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2013-07-26 15:09:00:357 332 b60 DnldMgr *********
    2013-07-26 15:09:00:357 332 b60 DnldMgr  * Call ID = {0995994E-A8CF-42DF-9338-D50DF013226B}
    2013-07-26 15:09:00:357 332 b60 DnldMgr  * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2013-07-26 15:09:00:357 332 b60 DnldMgr  * Updates to download = 1
    2013-07-26 15:09:00:357 332 b60 Agent  *   Title = Update for Microsoft Security Essentials - 4.3.215.0 (KB2855265)
    2013-07-26 15:09:00:357 332 b60 Agent  *   UpdateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}.201
    2013-07-26 15:09:00:357 332 b60 Agent  *     Bundles 1 updates:
    2013-07-26 15:09:00:357 332 b60 Agent  *       {E381C97C-375B-46A4-A24F-3DBADE3E80B8}.201
    2013-07-26 15:09:00:481 332 b60 DnldMgr ***********  DnldMgr: New download job [UpdateId = {E381C97C-375B-46A4-A24F-3DBADE3E80B8}.201]  ***********
    2013-07-26 15:09:03:477 332 b60 DnldMgr  * All files for update were already downloaded and are valid.
    2013-07-26 15:09:03:586 332 b60 Agent *********
    2013-07-26 15:09:03:586 332 b60 Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2013-07-26 15:09:03:586 332 b60 Agent *************
    2013-07-26 15:09:03:586 332 bb0 AU >>##  RESUMED  ## AU: Download update [UpdateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}, succeeded]
    2013-07-26 15:09:03:586 332 bb0 AU #########
    2013-07-26 15:09:03:586 332 bb0 AU ##  END  ##  AU: Download updates
    2013-07-26 15:09:03:586 332 bb0 AU #############
    2013-07-26 15:09:03:586 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:09:03:601 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:601 332 bb0 AU AU setting pending client directive to 'Install Approval'
    2013-07-26 15:09:03:601 332 b60 Report CWERReporter finishing event handling. (00000000)
    2013-07-26 15:09:03:617 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:664 332 eb0 AU Getting featured update notifications.  fIncludeDismissed = true
    2013-07-26 15:09:03:664 332 eb0 AU No featured updates available.
    2013-07-26 15:09:08:625 332 b60 Report CWERReporter finishing event handling. (00000000)
    2013-07-26 15:09:14:054 332 40c AU WARNING: AU found no suitable session to launch client in

    Friday, July 26, 2013 11:51 AM
  • 2013-07-26 15:09:03:586 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:09:03:601 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:601 332 bb0 AU AU setting pending client directive to 'Install Approval'
    2013-07-26 15:09:03:601 332 b60 Report CWERReporter finishing event handling. (00000000)
    2013-07-26 15:09:03:617 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:664 332 eb0 AU Getting featured update notifications. fIncludeDismissed = true
    2013-07-26 15:09:03:664 332 eb0 AU No featured updates available.

    I'm sure you can find the reason alone :)

    TiGrOu.

    Friday, July 26, 2013 12:27 PM
  • 2013-07-26 15:09:03:586 332 bb0 AU Setting AU scheduled install time to 2013-07-27 11:00:00
    2013-07-26 15:09:03:601 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:601 332 bb0 AU AU setting pending client directive to 'Install Approval'
    2013-07-26 15:09:03:601 332 b60 Report CWERReporter finishing event handling. (00000000)
    2013-07-26 15:09:03:617 332 bb0 AU Successfully wrote event for AU health state:0
    2013-07-26 15:09:03:664 332 eb0 AU Getting featured update notifications. fIncludeDismissed = true
    2013-07-26 15:09:03:664 332 eb0 AU No featured updates available.

    I'm sure you can find the reason alone :)

    TiGrOu.

    Do you mean "No featured updates available"? But I see the MSE availble, I can run the update as standard user, the system download it, create a restoration point but when it starts to install I receive the error...

    Thks

    Diego

    Friday, July 26, 2013 12:56 PM
  • I mean that the 07.27.2013 scheduled time is for tomorrow ... :)

    That's maybe because you planned install to be performed only once a day at 11:00.

    TiGrOu.

    Friday, July 26, 2013 1:18 PM
  • But if I force the installation by clicking on "Install updates" I should be able to install them...or I must to accomplish this task only at 11:00???
    Friday, July 26, 2013 1:41 PM
  • But if I force the installation by clicking on "Install updates" I should be able to install them

    Correct.

    or I must to accomplish this task only at 11:00???

    No. In fact, the scheduled installation event is absolutely irrelevant to this update, which is why you don't see the message "(update) is scheduled for installation at (nextInstallationEvent)".

    The error 0x80240020

    2013-07-26 15:08:01:155+0200 1 182 101 {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD} 201 80240020 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80240020: Update for Microsoft Security Essentials - 4.3.215.0 (KB2855265).

    0x80240020
    SUS_E_NO_INTERACTIVE_USER
    interactive user is missing to finish the operation

    is because there was no interactive user eligible to install the update. The update does not require any special privileges (I installed mine on my own system as a standard non-administrative user.)

    However, since the log snippet posted started at the END of the active installation event, it's impossible to tell what kind of installation was running that threw this error. I would suggest rebooting this workstation and trying the installation again.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, July 26, 2013 8:26 PM
    Moderator
  • I've tried several times to reboot the system but I have always the same error when I try to install the update as standard user.

    Here you are the WindowsUpdate log and the current settings of my Wsus policies: http://we.tl/8BC1bqldx1

    Thanks for your help

    Diego


    Monday, July 29, 2013 2:47 PM
  • Well, the provided log does not contain entries from July 26, so there's no way I can further investigate the event you've reported. In fact, the log segment provided in the link starts on 7/29 @ 3:34pm (0134 GMT), which was just a few hours ago.

    There is, however, an installation event initiated in this logfile @ 3:39pm.

    2013-07-29 15:39:21:673 1308 b50 CltUI AU client got new directive = 'Install Approval', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0
    2013-07-29 15:39:21:673 1308 b50 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-07-29 15:39:21:673 1308 b50 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-07-29 15:39:21:673 1308 b50 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-07-29 15:39:21:673 1308 b50 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-07-29 15:39:21:688 412 b14 AU AU received handle event
    2013-07-29 15:39:21:688 412 b14 AU AU setting pending client directive to 'Install Approval'
    2013-07-29 15:39:36:696 412 b14 AU Launched new AU client for directive 'Install Approval', session id = 0x2
    2013-07-29 15:39:36:711 2744 968 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0200) ===========
    2013-07-29 15:39:36:711 2744 968 Misc = Process: C:\Windows\system32\wuauclt.exe
    2013-07-29 15:39:36:711 2744 968 AUClnt Launched Client UI process
    2013-07-29 15:39:37:507 2744 968 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0200) ===========
    2013-07-29 15:39:37:507 2744 968 Misc = Process: C:\Windows\system32\wuauclt.exe
    2013-07-29 15:39:37:507 2744 968 Misc = Module: C:\Windows\system32\wucltux.dll
    2013-07-29 15:39:37:507 2744 968 CltUI AU client got new directive = 'Install Approval', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0
    2013-07-29 15:39:57:163 412 61c AU Getting featured update notifications. fIncludeDismissed = true
    2013-07-29 15:39:57:163 412 61c AU No featured updates available.

    One thing I note from the above log entries... the installation was launched from SessionID 0x2 ... are you launching this using Remote Desktop?

    In any event, for whatever reason, the WUAgent has reported "no featured updates available". I'm pondering the significance of this in consideration of the current state of things.

    Nonetheless, an instalation was launched at a later time...

    2013-07-29 16:02:30:321 412 eb0 AU BeginInteractiveInstall invoked for Install
    2013-07-29 16:02:30:321 412 eb0 AU Auto-approving update for install, updateId = {0D5EDAA4-A3F0-4426-AEB8-A8AE6CD5D5DD}.201, ForUx=1, IsOwnerUx=1, HasDeadline=0, IsMinor=0
    2013-07-29 16:02:30:321 412 eb0 AU Auto-approved 1 update(s) for install (for Ux), installType=1
    2013-07-29 16:02:30:321 412 eb0 AU #############
    2013-07-29 16:02:30:321 412 eb0 AU ## START ## AU: Install updates
    2013-07-29 16:02:30:321 412 eb0 AU #########
    2013-07-29 16:02:30:321 412 eb0 AU # Initiating manual install
    2013-07-29 16:02:30:321 412 eb0 AU # Approved updates = 1

    2013-07-29 16:02:47:746 412 2a4 AU # WARNING: Install failed, error = 0x80240020 / 0x00000000
    2013-07-29 16:02:47:855 412 b8c Agent *********
    2013-07-29 16:02:47:855 412 b8c Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
    2013-07-29 16:02:47:855 412 b8c Agent *************
    2013-07-29 16:02:47:855 412 2a4 AU Install call completed.
    2013-07-29 16:02:48:666 412 f78 AU Changing existing AU client directive from 'Progress Ux' to 'Install Complete Ux', session id = 0x2
    The installation failed with 0x80240020. I note, again, from SessionID 0x2.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, July 29, 2013 5:03 PM
    Moderator
  • Thanks a lot Lawrence for your patience.

    Yes, I was working remotely but now I have tried again to work directly on the machine but the result doesn't change :-(

    I've tried also on another machine. Here you are both logs file (log1 the same machine of yesterday, log2 another Windows 7 machine): http://we.tl/sgtmq7RkYd

    I have always the same error 80240020 when I try to manual force the installation with a standard user. The policies are always the same of yesterday.

    I'm beginning to desperate :-(

    Tuesday, July 30, 2013 12:56 PM
  • I have always the same error 80240020 when I try to manual force the installation with a standard user. The policies are always the same of yesterday.

    Okay, let's get primitive, because I'm not aware of any scenario in which a standard user would be unable to install this MSE update.

    Please export and post the following registry keys/subkeys/values:

    • HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    • HKCU\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    • HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer
    • HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, July 30, 2013 4:51 PM
    Moderator
  • I've found only two entries of the four above, here you are:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "WUServer"="http://192.168.1.9:80"
    "WUStatusServer"="http://192.168.1.9:80"
    "ElevateNonAdmins"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    "NoAutoRebootWithLoggedOnUsers"=dword:00000001
    "AUPowerManagement"=dword:00000001
    "IncludeRecommendedUpdates"=dword:00000001
    "AutoInstallMinorUpdates"=dword:00000001
    "UseWUServer"=dword:00000001
    "RebootRelaunchTimeoutEnabled"=dword:00000001
    "RebootRelaunchTimeout"=dword:000005a0
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000001
    "NoAUAsDefaultShutdownOption"=dword:00000000
    "NoAUShutdownOption"=dword:00000000
    "RescheduleWaitTimeEnabled"=dword:00000001
    "RescheduleWaitTime"=dword:00000001
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000004
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:0000000b

     

    ...and

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
    "NoDriveTypeAutoRun"=dword:00000091
    "ForceStartMenuLogOff"=dword:00000001

    Thanks again

    Diego

    Wednesday, July 31, 2013 8:42 AM
  • Nothing in the key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate ?

    Otherwise, we can now authoritatively rule out that any other WUAgent configuration settings are responsible.

    Previously we could attribute the 0x80240020 error to the remote desktop session on SessionID 2, which likely did not have sufficient privileges to perform an installation using the Windows Installer - a common limitation of this technology. It would be useful to know if the WindowsUpdate.log is providing any additional clues as to why the current user is prohibited from performing the installation.

    Also, I found KB910341 which discusses known causes/remediations for the 0x80240020 error when installing updates using the WUAgent. "Section C", for Vista/WS2008 is equally applicable to Win7/WS2008R2 systems, but basically this procedure revolves around verifying correct logon rights (which is wierd because administrator rights are not required on Vista and newer systems), confirming that BITS and SENS are running, and verifying that DNS is working (and I haven't a clue as to why a defective DNS would throw an "interactive user" violation during an installation).

    Finally, if all else fails, consider simply uninstalling MSE, downloading the new full installer for the current release, and installing a fresh MSE. As a diagnostic step this might point at a pre-existing issue with the current installation(s), although hopefully you won't have to do this on dozens of systems.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, July 31, 2013 8:52 PM
    Moderator
  • When you go to install the update in windows update it'll just hang there. Open MS security essentials while this is "hanging" and it will give you a new dialog prompt for the update and will install correctly.
    Wednesday, August 14, 2013 1:40 PM