Update to windows 10 pro version 1511, 10586 failure

Troubleshooting Windows Update Failures After Upgrading to Windows 10 Pro Version 1511, Build 10586

====================================================================================

After installing a new operating system or service pack on your organization's computers, it is not uncommon for issues with Windows Updates (WU) and Microsoft's own update management tool, WSUS (Windows Server Update Service), to arise. In this article, we will focus specifically on resolving problems encountered when attempting to upgrade from earlier versions of Windows 10 Pro to version 1511, build 10586.

Symptoms

-----

After installing the latest cumulative updates for your current version of Windows 8 or later operating system (e.g., Windows Server 2012 R2), WSUS may still display two unapproved update choices:

* Upgrade to Windows 10 Pro, version 1511, 10586 - en-us, Retail

* Upgrade to Windows 95Pro, version 1511, 10586 - en-us, Volume

The symptoms described above can manifest in various ways depending on the specific configuration of your organization's IT environment and how WSUSService is configured. However, these two scenarios are among the most common.

Causes

---

Before we dive into potential solutions for this issue, it is essential to understand what might be causing such behavior from WSUS:

1. Insufficient Product Keys: If you haven't properly activated your Windows operating system or if there isn't a valid product key entered in WSUSServer.msc (the Group Policy Object Editor), then the client computers will not receive any updates.

2. WSUS GPOs Not Properly Configured: Sometimes, WSUS-related GPOs might be configured incorrectly on your domain controllers or maybe they haven't been propagated to all machines yet.

3 Malfunctioning WSUSServer Components: If there are issues with the components that handle Windows Update functionality within WSUS itself (e.g., wuauclt.exe), then this can lead to such symptoms as well!

4. Missing or Corrupt KB3109878/KB3124260 Updates Installed Beforehand

Solutions

-----

### Solution 1: Verify and Install Latest Cumulative Updates

Before attempting any of the following solutions, ensure that all client computers are running the latest cumulative updates for Windows Update (WU) itself. To do this:

1. Open PowerShell or Command Prompt as an administrator.

2. Run `Get-WuUpdate -IncludeNonPublic` and verify if there are any available updates listed.

If you find any pending updates, install them according to Microsoft's instructions: 'KB3109878'(https://support.microsoft.com/en-us/kb/3109878) or 'KB3124260'(https://support.microsoft.com/en-US/KB3124260).

### Solution 2: Reset WSUS Client-Side Components

Sometimes, resetting the client-side components responsible for Windows Update can resolve these issues. To do this:

1. Open PowerShell or Command Prompt as an administrator.

2. Run `net stop wuaclient` followed by `net start wuaclient`.

3. Reboot your computer to apply changes.

### Solution 3: Uninstall and Re-Install WSUS Client

If the above solutions do not resolve the issue, it might be necessary to completely remove and re-install the Windows Update Agent (WUA) client on affected machines:

1. Open PowerShell or Command Prompt as an administrator.

2. Run `wusa /kb:4486995` followed by a reboot.

### Solution 4: Re-Register WU Components

In rare cases, registering missing components for Windows Update might resolve the issue:

1. Open PowerShell or Command Prompt as an administrator.

2. Run each of the following commands one at a time and then restart your computer after each:

* `reg delete 'HKCU\Software\Policies\Microsoft\Windows\WindowsUpdate' /f`

* `reg add 'HKEY_LOCAL_MACHINE\SOFTWARE\Policies\M Microsoft\Windows\WindowsUpdate' -d '' -t REG_DWORD -e 0x00000000`

3. Re-run the Windows Update troubleshooter: 'Troubleshoot problems installing updates in Windows'(https://support.microsoft.com/en-us/KB30866003).

-------

In conclusion, issues with WSUS and WU after upgrading to a new version of an operating system are not uncommon and can often be resolved through simple troubleshooting steps. Ensure that all necessary cumulative updates have been installed, verify the configuration of your environment's Group Policy Objects (GPOs) related to Windows Update, and consider resetting or re-installing WSUS client components as a last resort.

By following these solutions in this order and carefully reviewing Microsoft's official documentation for any specific requirements or caveats applicable to your particular IT environment, you should be able to successfully resolve issues with upgrading from earlier versions of Windows 10 Pro to version 1511, build 10586.

Update to windows 10 pro version 1511, 10586 failure