locked
Running updates in a background process RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I realize thet my question can sound strange as is not strictly related to WSUS.

    My question is related to Microsoft updates instead.

    A customer implemented a custom solution to manage updates by creating a background process that executes updates, either for their custom applications and for Windows updates.

    When they attempt to execute a Microsoft Windows update the update fails and in the logs they see the following eror:

    WARNING: AU found no suitable session to launch client in

    If they exectute the same update in the same server manually everything works fine and the log reports a line like:

    Launched new AU client for directive 'Reboot Pending', session id = 0x2

    The background process is executed as Administrator so I don't think there is any authorization issue.

    So the question is: how can they confngure theyr background process in order to make AU available to the update they want to run?

    Or, how can they confngure their service in order to launch the Windows Update in a way compatible to the execution in a background context?

    Regards

    Mario

     

    Tuesday, April 2, 2019 3:10 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Mario,
      

    Providing the server and client operating system versions will help with the analysis of the problem, as well as posting the windowsupdate.log error message section will also help the problem analysis.
      

    The WARNING "AU found no suitable session to launch client in" means that:
      

    • There is no user logged onto the system
    • The user logged on does not have administrator permissions.
        

    By default, a logged in user must be a Local Administrator to interact with the UI. You can also extend authorization to all users, by enabling the policy "Allow non-admins to receive update notifications", but before you do that, be aware of all of the implications of granting that level of access to all users.
      

    Reply back with the results would be happy to help.
      

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 3, 2019 7:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Many thanks for your answer.

    I am collecting the information and I'll update ASAP.

    In the meantime let me ask for some further clarification: you said that the problem can occur if:

    • There is no user logged onto the system
    • The user logged on does not have administrator permissions.

    I can confirm that when the update is executed there is no interactive user logge don interactively, while the update is executed by a background process (a service) configured to run as the Domain Administrator. Can this be the problem?

    Regards

    Mario

    Wednesday, April 3, 2019 8:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Let me provide some further information.

    The update is being installed on a Windows server 2008 R2 server.

    I include the most relevart part of the windowsupdate.log (I added the asterisk lines myself).

    I hope there are enough information.

    Regards

    Mario

    2019-03-27	13:41:36:322	 940	1380	AU	Initializing featured updates
2019-03-27	13:41:36:322	 940	1380	AU	Found 0 cached featured updates
2019-03-27	13:41:36:322	 940	1380	AU	Successfully wrote event for AU health state:0
2019-03-27	13:41:36:322	 940	1380	AU	Successfully wrote event for AU health state:0
2019-03-27	13:41:36:322	 940	1380	AU	AU finished delayed initialization
2019-03-27	13:41:36:322	 940	1380	AU	AU setting pending client directive to 'Reboot Pending'
2019-03-27	13:41:36:322	 940	1380	AU	AU setting next sqm report timeout to 2019-03-28 12:41:36
2019-03-27	13:41:36:322	 940	1380	AU	#############
2019-03-27	13:41:36:322	 940	1380	AU	## START ##  AU: Search for updates
2019-03-27	13:41:36:322	 940	1380	AU	#########
2019-03-27	13:41:36:322	 940	1380	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {A0130975-991B-432A-B095-670FFD420585}]
2019-03-27	13:41:36:322	 940	10ec	Agent	*************
2019-03-27	13:41:36:322	 940	10ec	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2019-03-27	13:41:36:322	 940	10ec	Agent	*********
2019-03-27	13:41:36:322	 940	10ec	Agent	  * Online = Yes; Ignore download priority = No
2019-03-27	13:41:36:322	 940	10ec	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"
2019-03-27	13:41:36:322	 940	10ec	Agent	  * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2019-03-27	13:41:36:322	 940	10ec	Agent	  * Search Scope = {Machine}
2019-03-27	13:41:36:322	 940	10ec	Setup	Checking for agent SelfUpdate
2019-03-27	13:41:36:322	 940	10ec	Setup	Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
2019-03-27	13:41:36:400	 940	10ec	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2019-03-27	13:41:40:986	 940	10ec	Misc	 Microsoft signed: NA
2019-03-27	13:41:40:986	 940	10ec	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9ED0.tmp with dwProvFlags 0x00000080:
2019-03-27	13:41:51:329	 940	1380	Misc	WARNING: IsSessionNonstandardUI: session 65536 is an unknown session type 0; treating it as a standard session

*********************************************************************************************************************

2019-03-27	13:41:51:329	 940	1380	AU	WARNING: AU found no suitable session to launch client in

*********************************************************************************************************************

2019-03-27	13:42:00:174	 940	10ec	Misc	 Microsoft signed: NA
2019-03-27	13:42:00:237	 940	10ec	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-win7sp1-wuredir.cab with dwProvFlags 0x00000080:
2019-03-27	13:42:01:141	 940	1380	AU	Forced install timer expired for scheduled install
2019-03-27	13:42:01:141	 940	1380	AU	UpdateDownloadProperties: 0 download(s) are still in progress.
2019-03-27	13:42:01:141	 940	1380	AU	Found a pending reboot, launching reboot UI
2019-03-27	13:42:01:141	 940	1380	AU	AU setting pending client directive to 'Reboot Warning'
2019-03-27	13:42:01:141	 940	1380	AU	AU scheduling auto reboot check since no user is logged on and reboot is required.
2019-03-27	13:42:01:141	 940	1380	AU	Setting AU scheduled install time to 2019-03-28 02:00:00
2019-03-27	13:42:01:141	 940	1380	AU	Successfully wrote event for AU health state:0
2019-03-27	13:42:04:823	 940	10ec	Misc	 Microsoft signed: NA
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2019-03-27	13:42:07:116	 940	10ec	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2019-03-27	13:42:07:132	 940	10ec	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2019-03-27	13:42:07:132	 940	10ec	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193

    Wednesday, April 3, 2019 11:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,
      

    Thank you for your response.
    Please try the following steps to resolve:
      

    • Reset the Windows Update component by the instructions in the following article: "How do I reset Windows Update components?"
       
    • If there is a firewall between WSUS or client and the Internet, you need to obtain authorization to allow Internet access from local to the following list of URLs:
         http://windowsupdate.microsoft.com
         http://*.windowsupdate.microsoft.com
         https://*.windowsupdate.microsoft.com
         http://*.update.microsoft.com
         https://*.update.microsoft.com
         http://*.windowsupdate.com
         http://download.windowsupdate.com
         https://download.microsoft.com
         http://*.download.windowsupdate.com
         http://wustat.windows.com
         http://ntservicepack.microsoft.com
         http://go.microsoft.com
        

    Hope the above can help you.
     

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 4, 2019 4:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 15, 2019 8:03 AM