Partager via

Guidelines for Asynchronous WUA Operations

  • Article

This topic identifies guidelines for you to the follow when you perform asynchronous Windows Update Agent (WUA) operations.

  • The asynchronous WUA operations do not guarantee any particular completion speed. The completion time for an asynchronous WUA operation can vary widely depending on computer hardware, version of the operating system, and network configuration. As with other Windows APIs that have network dependencies and that do not contain a time-out parameter or a documented time-out duration, we recommend that you consider implementing your own time-out mechanisms if you need guaranteed response times. For example, you can create a worker thread that calls an asynchronous WUA method and that sets an event or other synchronization object when the asynchronous WUA operation completes; the main thread can then use the WaitForSingleObject or WaitForMultipleObjects function, which allows you to specify a time-out value.
  • When you end a search, download, installation, or uninstallation of updates, you can use IUpdateSearcher::EndSearch, IUpdateDowloader::EndDownload, IUpdateInstaller::EndInstall and IUpdateInstaller::EndUninstall from any thread.
  • When you start a search, download, installation, or uninstallation of updates by using IUpdateSearcher::BeginSearch, IUpdateDownloader::BeginDownload, IUpdateInstaller::BeginInstall, and IUpdateInstaller::BeginUninstall, ensure that you maintain sufficient access permisssions when you release references to WUA API objects.
    • Make sure any callback objects that are used in the asynchronous operation are unreferenced before you destroy them. Wait for the reference count of a callback object to return to the initial value before you destroy it.
    • The reference to the job object that is returned from the corresponding Begin method should be controlled by an object that differs from the callback objects. Use an object that differs from the callback objects to avoid circular references.
    • If you attempt to control the reference to the job object by using a callback object, you must call the IDownloadJob::CleanUp, IInstallationJob::CleanUp, or ISearchJob::CleanUp method outside the callback function to disconnect the job object from the callback object. You must do this before you release the reference to the job object that is returned by the Begin method.
  • Make sure that asynchronous WUA operations are complete. Windows Script Host can terminate a script when all the commands outside of any function are complete, even if the WUA API still has references to the callback object.
    • Use one of the CleanUp methods or have the callback function set a shared global variable upon completion.
    • Never call IDownloadJob::CleanUp, IInstallationJob::CleanUp, or ISearchJob::CleanUp on a job object in its callback function.
    • To ensure the correct clean-up sequence in a script that is running on Windows Internet Explorer, call the CleanUp method on all the job objects when processing window.onbeforeunload.
  • Do not use user-defined data types (UDT) for asynchronous WUA operations. The type is not supported by IUpdateSearcher::BeginSearch, IUpdateDownloader::BeginDownload, IUpdateInstaller::BeginInstall, or IUpdateInstaller::BeginUninstall.