locked
wuauclt.exe /updatenow error 0x800703F0 => "ERROR_NO_TOKEN An attempt was made to reference a token that does not exist" RRS feed

  • Question

  • Hi,

    we try to implement a scheduled script based solution with the wuauclt.exe /updatenow command

    for some of our Server in the Company. These Servers should get their update just in time after the last succesful backup Job.

    we want to start this as an "after backup succesfully completed" Job, i.e. in the 3rd Party Acronis Backup Agent, or with the psexec command, or as a remote scheduled Task with Schtasks.exe.

    At this Moment, im out of luck with my Troubleshooting and i have no idea, whether wuauclt.exe can used for our intend.

    For my understanding:

    It seems, that the wuauclt.exe /updatenow depends on a interactive user which has to be logged on to a machine.

    Because if you try to start the wuauclt.exe /updatenow locally in a command prompt, the graphical Windows update Windows is opnening and the Installation of the updates is starting.

    at least iam interpreting this error: 0x800703F0 => "ERROR_NO_TOKEN An attempt was made to reference a token that does not exist" => Does this process Need a user token from an active user session for launching the Windows update gui in?

    the other Switches from wuauclt.exe, i.e. /Reportnow or detectnow works by starting it remote via psexec or scheduled Task, no gui is needed.

    Am I right with my Investigation or not? Can I tune this dependency with secpol.msc or in registry ?

    Is it a further dependency with the wuauserv Service which is started under the local System account?

    the psexec -i -s Switch from another thread https://social.technet.microsoft.com/Forums/lync/en-US/0a4ef85d-87ea-4d81-b6cb-5f7cdab6e50d/wuauclt-through-opalis?forum=opalisv5v6

    does not solve my Problem and the error is the same...

    Here the windowsupdate.log file with the determining error part:

    2014-10-21 07:37:44:702  728 fd4 AU AU received handle event
    2014-10-21 07:37:44:702  728 fd4 AU AU setting pending client directive to 'Install Approval'
    2014-10-21 07:37:59:711  728 fd4 AU WARNING: AU found no suitable session to launch client in
    2014-10-21 07:40:29:582  728 588 AU AU received approval from Ux for 95 updates
    2014-10-21 07:40:29:582  728 588 AU AU setting pending client directive to 'Progress Ux'
    2014-10-21 07:40:29:582  728 588 AU FATAL: CAUClient::Launch failed, error = 0x800703F0
    2014-10-21 07:40:29:582  728 588 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2014-10-21 07:40:29:582  728 588 AU Triggering Offline detection (non-interactive)
    2014-10-21 07:40:29:582  728 588 AU AU setting pending client directive to 'Install Complete Ux'
    2014-10-21 07:40:29:582  728 588 AU WARNING: Pending directive, 'Install Complete Ux', is not applicable
    2014-10-21 07:40:29:582  728 588 AU WARNING: ApproveUpdatesInternal failed with hr:800703f0
    2014-10-21 07:40:29:582  728 588 AU WARNING: UpdateNow failed with hr:800703f0
    2014-10-21 07:40:29:582  728 fd4 AU #############
    2014-10-21 07:40:29:582  728 fd4 AU ## START ##  AU: Search for updates
    2014-10-21 07:40:29:582  728 fd4 AU #########
    2014-10-21 07:40:29:613  728 fd4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {AB71D9B3-66DC-43AD-A948-F5745F7FE31E}]
    2014-10-21 07:40:29:613  728 1628 Agent *************
    2014-10-21 07:40:29:613  728 1628 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-21 07:40:29:613  728 1628 Agent *********
    2014-10-21 07:40:29:613  728 1628 Agent   * Online = No; Ignore download priority = No
    2014-10-21 07:40:29:613  728 1628 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"
    2014-10-21 07:40:29:613  728 1628 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-10-21 07:40:29:613  728 1628 Agent   * Search Scope = {Machine}
    2014-10-21 07:40:59:019  728 1628 Agent Update {3F08EED3-8FC3-4253-8FA9-F301430C4B24}.102 is pruned out due to potential supersedence
    2014-10-21 07:40:59:019  728 1628 Agent   * Added update {67EC57DE-47A3-4DB2-8B0F-03C86317C812}.200 to search result

    .... and so on...

    thanks for any help

    Tuesday, October 21, 2014 8:05 AM

Answers

  • Hi,

    for fully automated update installations, I would recommend using a scripted update rather than wuauclt.exe

    I've use a customized version of this script successfully to do unattended updates in many environments.


    MCP/MCSA/MCTS/MCITP

    • Marked as answer by Neocortex2001 Friday, October 24, 2014 4:49 AM
    Tuesday, October 21, 2014 12:10 PM
  • Hi,

    for fully automated update installations, I would recommend using a scripted update rather than wuauclt.exe

    I've use a customized version of this script successfully to do unattended updates in many environments.


    MCP/MCSA/MCTS/MCITP

    Hi SenneVL,

    thank you very much for posting this link. vbs script works perfect!

    Ive modiefied it a litle bit at the end for checking if a reboot is required, then the machine reboots automatically!

    Bye


    Friday, October 24, 2014 4:53 AM

All replies

  • Hi,

    for fully automated update installations, I would recommend using a scripted update rather than wuauclt.exe

    I've use a customized version of this script successfully to do unattended updates in many environments.


    MCP/MCSA/MCTS/MCITP

    • Marked as answer by Neocortex2001 Friday, October 24, 2014 4:49 AM
    Tuesday, October 21, 2014 12:10 PM
  • we try to implement a scheduled script based solution with the wuauclt.exe /updatenow command

    So this would be your first mistake...

    • This parameter is undocumented and non-functional.
    • Most certainly it does not INSTALL updates, even if it were functional.

    I'm bound to ask you this question: What documentation did you read that led you to believe this parameter could be used in a script to INSTALL updates?


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

    Thursday, October 23, 2014 4:40 AM
  • Hi,

    for fully automated update installations, I would recommend using a scripted update rather than wuauclt.exe

    I've use a customized version of this script successfully to do unattended updates in many environments.


    MCP/MCSA/MCTS/MCITP

    Hi SenneVL,

    thank you very much for posting this link. vbs script works perfect!

    Ive modiefied it a litle bit at the end for checking if a reboot is required, then the machine reboots automatically!

    Bye


    Friday, October 24, 2014 4:53 AM
  • Hi Lawrence,

    it is described in the comments from this TechNet article:

    http://technet.microsoft.com/en-us/library/cc720477(WS.10).aspx

    wuauclt.exe /updatenow works perfect if you are logged in on a local machine and you type it in a powershell command box or in cmd.exe.

    but not via remote, i.e. with psexec.exe

    but its okay for me, the vbs script works perfect.

    Bye

    Friday, October 24, 2014 5:05 AM
  • it is described in the comments from this TechNet article:

    http://technet.microsoft.com/en-us/library/cc720477(WS.10).aspx

    The /updatenow parameter is undocumented, and thus unsupported, and most certainly does not appear in that TechNet article -- except for the user-posted crap that appears underneath the article in the community contributions -- almost all of which is incorrect. It's also contained in legacy documentation (the WSUS3SP1 docs), so the page isn't even being maintained anymore, nor is it the current doc page for that utility.

    I'm happy it worked for you, though.

    Worthy of note, if you're logged into a LOCAL machine you can also run Control Panel > Windows Update and install the updates too! And that method is supported!

    Take note though, because it is NOT documented, it's also subject to being deleted or changed without notice. Relying on the behavior of undocumented command line parameters, particularly in an automated/unattended script, is what makes for catastrophies years down the line when things changed, and nobody remembers what/why something was done, or worse, the person who did it is long gone.


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

    Friday, October 24, 2014 10:53 PM