Microsoft Vista Updates Will Not Download

Feb 16, 2019 - Hello. I have Windows Vista and over the last month the windows updates will no longer download and therefore won't install.

  1. Windows Vista Update Not Working
  2. Microsoft Vista Updates Will Not Download On Laptop
  3. Microsoft Vista Updates Will Not Download On Pc

Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Because of this proxy servers configured on the network must support HTTP RANGE requests. [1] Beginning in Windows 8, Microsoft began releasing regular, major updates to Windows 8. Service packs will not be released. [2] Windows 7 SP1 and the April 2015 Servicing Stack Update both must be installed prior to installing the Convenience Rollup. [3] Windows Vista SP2 can only be installed if you already have Windows Vista SP1 installed, which you can download here for 32-bit versions. Jun 20, 2009  [b]Question:[/b] Windows Vista updates are available, but won't download and install I was hoping someone could help me fix Windows Update. It's been mont.

-->

Windows Vista Update Not Working

Applies to: Windows 10

If you run into problems when using Windows Update, start with the following steps:

  1. Run the built-in Windows Update troubleshooter to fix common issues. Navigate to Settings > Update & Security > Troubleshoot > Windows Update.
  2. Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See Servicing stack updates for more details on SSU.
  3. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:

Advanced users can also refer to the log generated by Windows Update for further investigation.

You might encounter the following scenarios when using Windows Update.

Why am I offered an older update/upgrade?

The update that is offered to a device depends on several factors. Some of the most common attributes include the following:

Microsoft vista updates will not download on laptop
  • OS Build
  • OS Branch
  • OS Locale
  • OS Architecture
  • Device update management configuration

If the update you're offered isn't the most current available, it might be because your device is being managed by a WSUS server, and you're being offered the updates available on that server. It's also possible, if your device is part of a Windows as a Service deployment ring, that your admin is intentionally slowing the rollout of updates. Since the WaaS rollout is slow and measured to begin with, all devices will not receive the update on the same day.

My machine is frozen at scan. Why?

The Settings UI is talking to the Update Orchestrator service which in turn is talking to Windows Update service. If these services stop unexpectedly then you might see this behavior. In such cases, do the following:

  1. Close the Settings app and reopen it.
  2. Launch Services.msc and check if the following services are running:
    • Update State Orchestrator
    • Windows Update

Feature updates are not being offered while other updates are

On computers running Windows 10 1709 or higher configured to update from Windows Update (usually WUfB scenario) servicing and definition updates are being installed successfully, but feature updates are never offered.

Checking the WindowsUpdate.log reveals the following error:

The 0x80070426 error code translates to:

Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on the Microsoft Account Sign In Assistant (MSA) to get the Global Device ID for the device. Without the MSA service running, the global device ID will not be generated and sent by the client and the search for feature updates never completes successfully.

In order to solve this issue, we need to reset the MSA service to the default StartType of manual.

Issues related to HTTP/Proxy

Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Because of this proxy servers configured on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.

To fix this issue, configure a proxy in WinHTTP by using the following netsh command:

Note

You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie

If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.

You may choose to apply a rule to permit HTTP RANGE requests for the following URLs:

*.download.windowsupdate.com
*.dl.delivery.mp.microsoft.com
*.emdl.ws.microsoft.com

If you cannot permit RANGE requests, keep in mind that this means you are downloading more content than needed in updates (as delta patching will not work).

The update is not applicable to your computer

The most common reasons for this error are described in the following table:

CauseExplanationResolution
Update is supersededAs updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you may encounter this error message.Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package.
Update is already installedIf the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.Verify that the package that you are trying to install was not previously installed.
Wrong update for architectureUpdates are published by CPU architecture. If the update that you're trying to install does not match the architecture for your CPU, you may encounter this error message.Verify that the package that you're trying to install matches the Windows version that you are using. The Windows version information can be found in the 'Applies To' section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers.
Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows.
Missing prerequisite updateSome updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed.Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424).
Note: To determine if these prerequisite updates are installed, run the following PowerShell command:
get-hotfix KB3173424,KB2919355,KB2919442
If the updates are installed, the command will return the installed date in the 'InstalledOn' section of the output.

Issues related to firewall configuration

Error that may be seen in the WU logs:

Or

Or

Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information , see I need to disable Windows Firewall or Windows Update stuck at 0 percent on Windows 10 or Windows Server 2016.

Issues arising from configuration of conflicting policies

Windows Update provides a wide range configuration policies to control the behavior of WU service in a managed environment. While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting polices may lead to unexpected behaviors.

See How to configure automatic updates by using Group Policy or registry settings for more information.

Updates aren't downloading from the intranet endpoint (WSUS/SCCM)

Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:

  1. Start Windows PowerShell as an administrator
  2. Run $MUSM = New-Object -ComObject 'Microsoft.Update.ServiceManager'.
  3. Run $MUSM.Services.

Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.

OutputInterpretation
- Name: Microsoft Update
-OffersWindowsUpdates: True
- The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.
- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.)
- Name: DCat Flighting Prod
- OffersWindowsUpdates: True
- Starting with Windows 10 1709, feature updates are always delivered through the DCAT service.
- Indicates that the client is configured to receive feature updates from Windows Update.
- Name: Windows Store (DCat Prod)
- OffersWindowsUpdates: False
-The update source is Insider Updates for Store Apps.
- Indicates that the client will not receive or is not configured to receive these updates.
- Name: Windows Server Update Service
- OffersWindowsUpdates: True
- The source is a Windows Server Updates Services server.
- The client is configured to receive updates from WSUS.
- Name: Windows Update
- OffersWindowsUpdates: True
- The source is Windows Update.
- The client is configured to receive updates from Windows Update Online.

You have a bad setup in the environment

If we look at the GPO being set through registry, the system is configured to use WSUS to download updates:

From the WU logs:

In the above log snippet, we see that the Criteria = 'IsHidden = 0 AND DeploymentAction='. '' means there is nothing specified from the server. So, the scan happens but there is no direction to download or install to the agent. So it just scans the update and provides the results.

Now if you look at the below logs, the Automatic update runs the scan and finds no update approved for it. So it reports there are 0 updates to install or download. This is due to bad setup or configuration in the environment. The WSUS side should approve the patches for WU so that it fetches the updates and installs it on the specified time according to the policy. Since this scenario doesn't include SCCM, there's no way to install unapproved updates. And that is the problem you are facing. You expect that the scan should be done by the operational insight agent and automatically trigger download and install but that won’t happen here.

High bandwidth usage on Windows 10 by Windows Update

Download

Users may see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that may consume bandwidth expand beyond Windows Update components.

The following group policies can help mitigate this:

Not

Microsoft Vista Updates Will Not Download On Laptop

  • Blocking access to Windows Update servers: Policy Turn off access to all Windows Update features (Set to enabled)
  • Driver search: Policy Specify search order for device driver source locations (Set to 'Do not search Windows Update')
  • Windows Store automatic update: Policy Turn off Automatic Download and Install of updates (Set to enabled)

Other components that reach out to the internet:

  • Windows Spotlight: Policy Configure Windows spotlight on lock screen (Set to disabled)
  • Consumer experiences: Policy Turn off Microsoft consumer experiences (Set to enabled)
  • Background traffic from Windows apps: Policy Let Windows apps run in the background
My windows update does not work. When I 'Check for Updates' it will never download anything. Ive had it trying for over 12 hours before and it makes no progress....

Hi Conan of Cimmeria:

Microsoft Vista Updates Will Not Download On Pc

Many Vista SP2 users are currently affected by a problem where the initial 'Checking for updates...' phase of Windows Update runs for several hours (or even days) without throwing an error message. I first noticed this issue on my 32-bit Vista SP2 machine in August 2015 (i.e., one month after the official release of Win 10 on 29-Jul-2015) and the length of the 'Checking for updates...' hangs got progressively worse each month.
Please see the instructions on page 1 of m#1's thread Updates not working, it has been searching for updates for hours for a possible solution. See Note 6 at the bottom of those instructions if you have MS Office 2007, MS Office 2010 or the MS Office Compatibility Pack SP3, since there are additional speed up patches for those Office products that must also be pre-installed to speed up Windows Update.
One alternative method is to use Torsten Wittrock's WSUS Offline Update tool to patch your system. I haven't tried this tool myself but other Vista SP2 users have reported good success. Note that a special extended support release (ESR) v9.2.2 of the tool was released 03-Jul-2017 for older platforms like Win XP SP3 and Vista SP2 since the latest v11.0.0 version only supports Win 7 SP1 and higher. Instructions are posted at http://www.wsusoffline.net/docs/.
Post #455 of KellyB56's thread Windows Vista Update Hangs at 'Checking For Updates' in the bleepingcomputer forum includes some background information on the cause of these slow Windows Updates, and if you are affected by this problem then running repair tools will not solve your issue. The Windows Update Agent (C:WindowsSystem32wuaueng.dll) v7.6.7600.256 for Vista SP2 has not been updated since June 2012 so you will likely have the latest available version unless you've recently performed a clean reinstall of your OS.
ASIDE:
See the Oracle support article Error Code 1603: Java Update Did Not Complete for a possible workaround for your Java issue.

------------
32-bit Vista Home Premium SP2 * Firefox ESR v52.2.1 * NS Premium v22.10.0.83 * MBAM Premium v3.1.2
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS