KB3035583 Installing Windows 10 using. Meaning that if they had not already been installed. 'This update is applicable to your systems even if you're not.

1. Wsus Updates Installed/not Applicable
2. Windows Installed Updates Registry
3. Update Not Applicable

Wsus Updates Installed/not Applicable

Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).

Most of you know that we released the Windows 10 1511 feature update, which is the first for Windows 10, to WSUS in December 2015. To fully enable this deployment scenario, we shipped a patch to WSUS for WS12 and WS12R2 in October 2015. Following this release, we received some questions regarding the applicability of this update. Such questions included:. Is this patch required to support Windows 10?.

What happens if I don’t install it?. Should I wait for the DLC or other non-Hotfix release?. Are there any known issues with the release? The simple translation of 'Support Windows 10' You might be asking whether WSUS can recognize, sync/import, and distribute Windows 10 updates without having to receive a patch itself to enable this functionality. If this is your concern, then you will not need any patches to enable this behavior. While Windows 10 is indeed a monumental release in our history, from the WSUS perspective it's just another product in the list, and there's nothing new to Windows 10 updates (including security updates) that requires WSUS to be modified in order to handle them.

Administrators of WSUS 3.0 SP2 (including SBS 2011) and unpatched WSUS 4.0 will be able to deploy Windows 10 updates, but not feature updates. Our preferred translation of 'Support Windows 10' One feature that makes Windows 10 special is delivering Windows as a service. For the WSUS or Configuration Manager administrator, this means enabling feature updates to a new build of Windows. These feature updates will be processed just like the usual quality updates, except that once they are approved for installation on WSUS/ConfigMgr-managed machines, they upgrade the entire build, not just some of its binaries.

If you're a member of the Windows Insider Program, then you've already been using this technology for a while (though not via WSUS). Wiping and loading images in order to refresh your Windows builds can be nothing but a memory, and that's what is offered here. It's especially useful because new Windows 10 builds will be released much more frequently than on the one-to-three-year release cycle to which you might be accustomed.

In order for WSUS to support these feature updates, it needs to install a patch. Feature updates introduce a new update content file type (and classification, called Upgrades) that will likely only be apparent to the WSUS admin: we've done our best to abstract the details from non-enterprise users. As for the quality Some folks are cautious about updates like KB 3095113 being released with boilerplate text that include verbiage such as “do not install unless you are experiencing this issue.” Hotfix is our most expedient release vehicle, and we wanted to provide as much time to deploy this ahead of the Windows 10 1511 feature update release to WSUS as possible. We have tested it the same as we would any Windows Update release, so there is no reason to wait to install the update on your WSUS 4.0 servers. For your convenience, we’ll be releasing the update more broadly to DLC and Catalog, as well as to WSUS itself, in the first quarter of 2016. If you prefer to wait for those releases, then please review the caution described next.

Important caution WSUS may be able to see the Windows 10 1511 feature update even if it can’t properly download and deploy the associated packages. The feature updates will become visible as soon as the “Upgrades” classification is checked in the WSUS options for Products and Classifications. If you attempt to sync any Upgrades without having first installed the, then you will populate the SUSDB with unusable data that must be cleared before Upgrades can be properly distributed. This situation is recoverable, but the process is nontrivial and can be avoided altogether if you make sure to install the update before enabling sync of Upgrades. If you have encountered this issue, then please stay tuned for an upcoming KB article that details the recovery steps.

What this means for you If you are content to wipe and load images for Windows 10 in order to stay on a current build, then simply do not enable sync of Upgrades in your WSUS, and do what you usually do to upgrade your Windows builds. However, if you ever intend to deploy Windows 10 and fully enable Windows as a service for your enterprise, then you'll want to deploy the. Furthermore, the safest route is to enable sync of Upgrades in your WSUS only after you have installed this patch on all WSUS 4.0 servers that service Windows 10 machines in your environment.

Your 1511 upgrade experience The Windows 10 1511 feature update is available via WSUS today, and it will apply to Windows 10 RTM as well as Windows 7 and Windows 8.1 machines. If you are upgrading from Windows 10 RTM, then the process is highly automated: it will skip the application provisioning stage and all setup steps that require user interaction, and will preserve file associations and other settings by default. Upgrading from Windows 7 and Windows 8.1 via WSUS will require some end user interaction because the entire platform is changing, not just a build. Feel free to post any questions below, and we'll clarify as needed. Todd: The 1511 feature upgrade carries a EULA that must be approved by the WSUS administrator before it can be installed on managed clients. This won’t happen automatically.

With that said, a managed client has to scan WSUS in order to determine that it has the 1511 upgrade available for installation. If the managed client is busy doing other setup tasks because of ConfigMgr or MDT, then it will finish those first, and then consider the 1511 feature upgrade not applicable when it does get around to scanning. Harry: WS08R2 SP1 can only run WSUS 3.0 SP2, so you’d be in that boat as described. We’ve got another post coming for folks in your situation that should illuminate your options and our recommendations here.

Not sure what you mean by your other question. Sir Francis: It means the 1511 feature upgrade can target Win7 and Win8.1 systems. If the WSUS administrator approves installation to those computer groups AND those computers are not marked to defer upgrades (they must be on the 'CB train' to get this), then yes, the behavior will be as you describe. Sandy: The update applicability is determined by build, and is agnostic to how the build was installed on the machine. If you’re running 1511 on your Win10 machines, then not only do you not need this upgrade via WSUS, you won’t even be able to install it because it will show as not applicable to those machines. However, should you want to change your deployment approach in the future, you could use WSUS instead of MDT.

A few of us seem to be having issues with download failures from the clients. Issue appears to be with the way the clients Windows update downloads the install.esd file (content/D3/5EDACCE12150D3.esd from the wsus server. I manually went to the location and copied it to the c:/Windows/softwaredistribution/download/72e7184eeed folder and renamed the file to what it was expecting according to the Windows update log. Then restarted the system and told it to retry the 1511 installation and it completed as expected.

Me too, same problem as David and Himura, Windows 2012R2 WSUS already patched before checking the Upgrades feature in WSUS. It downloaded to the server fine. I created a Windows 10 Upgrades container and a Windows 10 workstations (for those already on W10). I approved the 1511 upgrade in those two containers and put some test PC’s in.

I did receive the EULA on the management station and agreed. The ESD is in the D3 directory. The test PC’s all show a failed upgrade to Windows 10 1511 and the Windows 10 PC’s also fail. It shows a failure to download with error code 80244019. This seems to be on any Windows 7, 8.1 or 10 machine. Is there something we can do to fix the server to get the right name to download?

Todd: I’ve contacted the MDT owners to confirm the expected behavior in this scenario, which I’ll post as soon as I have it. Glenn: You needn’t be so quick to rule out CB/CBB in your environment. LTSB will also be eligible for a one-way upgrade to the CB/CBB servicing trains, and you may want this functionality somewhere down the road. It doesn’t hurt to patch your WSUS now, just so you don’t run into problems later. Also, the patch fixes an issue where Windows 10 machines display as 'Windows Vista' in the WSUS console, so it’s worth getting for that reason, too. PeterAUS: What the upgrade does when it’s on the box is not up to WSUS, so I unfortunately can’t comment on this uninstall behavior you’re seeing. I’ve sent your note to the appropriate team, though, and will let you know when I get an answer.

Thorsten: KB2938066 should be installed on every WSUS server in order to ensure proper functioning (and secure operation). With that said, there is no hard-coded prerequisite for this specific KB. Kevin: You’ll need Configuration Manager vNext to support deployment of feature upgrades, though you might see them in your SUM console today because that view is based on what WSUS can see. I recommend you do not sync Upgrades if you cannot deploy them. Anthony: When deployment is complete (in progress at the moment), you’ll see version 1511 upgrades for Pro, Education, and Enterprise in your WSUS. Michael: The 1511 upgrade only targets Windows 7, 8.1, and 10. Any groups with Windows 8 machines need not be duplicated from your existing environment.

With that said (and without knowledge of your environment), you might consider creating a new group of all your Windows 10 machines, to be used only for the purpose of deploying an upgrade, and then continue with your current groups for update management. Jonathan/Sandy: We’ll be posting a KB article that describes how to fix your SUSDB if you happened to miss the warning in this blog post to patch first. Maybe we’ll use bigger font next time. = Tim: The licensing download issue is one we haven’t seen.

I’m having someone look into this, and will let you know via this blog (and possibly KB) when a workaround is available. Can you share the download error you’re seeing in windowsupdate.log when this occurs? Any event log entries to go with it? Henri: Stay tuned for a more comprehensive treatment of the WSUS 3.2 topic regarding Windows 10 servicing.

CurtK-CA/Himura: Have you checked your windowsupdate.log to see whether the file it’s expecting matches the filename in your SUSDB? If there is a mismatch, then you might review David’s post above. I can’t comment on our official workaround until we’ve had a chance to take a look ourselves. Lavee45: Can you try again?

I get an 'Accept Terms' page when I click the link you provided, and am able to download the hotfix afterward. Please post here if you’re still seeing ESD download failures after using Alexx80’s solution. We were about to recommend something similar via PowerShell scripts.

Regarding the visible upgrades, we are investigating existing publishing issues (which didn’t occur when we released this internally), and hope to have Education and Enterprise published soon. This is our first time pushing upgrade content to WSUS externally, so it’s a bit rockier than it will be in future releases. We appreciate your patience and willingness to look for solutions to the new challenges that have arisen. We will finalize the release for the remaining editions as soon as we’ve worked out these issues. So I checking in the windowsupdate.log file to see and I did find the line where it’s failing, but not so good at interpreting these logs. It kind of appears that the download in not happening correctly, although it does say it resumes, but issues a warning: 2015-12-11 04:33:09:759 500 1270 DnldMgr Failed job file: URL =, local path = C:WINDOWSSoftwareDistributionDownload04de5be507e0b8fa84eeed10586.0.1.th2releaseCLIENTPRORETx64freen-us.esd 2015-12-11 04:33:09:915 500 12d0 AU # WARNING: Download failed, error = 0x80244019 All our testing machines are failing in this way. One thing I have noticed as well is that I used to have an Upgrades section under Updates in the WSUS mgr, but that’s now gone.

I did install the patch well before ever checking that box and allowing sync (was days in between actually). But it no longer appears in the list. Everything still shows failing no matter what the client. So a follow up for why my clients did not see the upgrade. I had previously turned on 'Turn off the upgrade to the latest version of Windows through Windows Update' back in the summer. Since then I have moved on to Windows 10 admx templates. I guess Microsoft removed that GPO setting so I didn’t see it any more in Group Policy Manager.

So what I did was grabbed a Windows 8.1 WindowsUpdate.admx file and placed it in my central store. Then set it to not configured. My clients see the upgrade now.

One of them is in the process of upgrading now. Let’s see if I get any other errors.

Thank you for these details. We wish we had this information when KB3095113 was first released. We are anxiously waiting for the details behind the nontrivial process to recover from syncing any Upgrades without having first installed KB3095113. We are even more eager to learn about what can be done for an enterprise that is running WSUS mostly from Server 2008R2. Finally, does Microsoft expect an enterprise to upgrade all of its WSUS servers to Server 2012 or better and also install KB3095113 on all of its WSUS servers before enabling the ‘Upgrade’ option? If so, that’s going to severely impact Win10 deployment at some enterprises who may begin to look for some WSUS alternatives from other vendors. Environment.

WSUS on Windows Server 2012 – Windows 10 Pro Clients. The WSUS Hotfix Update KB3095113 is already installed and 'Upgrades' section is visible. The Updates 'Upgrade to Windows 10 Pro, Version 1511, 10586' is ready to install. Problem. All Windows 10 clients get same error: Download failed. Solution:. IIS: Add a MIME type on IIS for.esd as application/octet-stream (Many thanks to: )  Test Result.

Windows Update download completed successfully. Installation of Windows 10 Pro 1511 finished after 25min. Without errors.

—————————————————————————- But unfortunately our Windows 7 Enterprise Clients still get Windows update error. Code 80244019. Hey, i am running mad. Yesterday we updated a customer from SCCM 2012 R2 SP2 to SCCM 1511. The new 'Upgrades' synced. But download fails as described above.

But this is not my problem. The Problem is my lab.

I updated my lab also to 1511. I installed the wsus hotfix and WSUS is showing the 'Upgrades'. But the Upgrades category is not synced to SCCM. So i cant see the Upgrades in SCCM.

I tryed reinstalling WSUS / SCUP, but it comes up with old WSUS 7 SCUP configuration. Best regards, Andre. Hoping for a possible answer to an upgrade question: We have a number of Enterprise 1507 installs that activate to our campus KMS — not using MAK activation — that are 'standalone' systems — they do not connect to a WSUS or ConfigManager or any other central patch management — they just get their updates through Windows Update. My understanding is.MAK. activated systems like this — are now seeing the 1511 update.

Does anybody have any idea if/when KMS-activated systems would see the 1511 update? Thanks a bunch! Steve, any update you may have for those of us with the error 'Failed to download content id 16851217.

Error: Invalid certificate signature'. I am running a Windows Server 2012 WSUS server with KB KB 3095113 installed. In SCCM 1511 we are seeing over 512 Windows 10 updates available and not one of them will download without the aforementioned certificate error. I had the KB installed before checking the Upgrades box.

I understand this is a new process, but the silence coming from the teams is getting pretty frustrating when we just want to update our environment. This manual DB cleanup process worked for me.

I’m writing a chunk of it from memory though, so I could be missing something. Warning: I have no idea what long-term repercussions there could be from performing this procedure. It may or may not work for anyone else. In my case, it was against a temporary lab WSUS server that was built just to test W10 1511 upgrades. You should definitely test yourself, and take backups of everything first.

Consider yourself warned. Record the update ID (GUID) from within the console (in my case, 5BEAEC8F-FE8F-4A81-830E-B1AAAAF6A76C for Enterprise 1511 en-US Volume) 2. Decline update for all computer groups 3. Stop the 'WSUS Service' service in SCM 4.

Run a SQL query against the WSUS database to find the local update ID (integer value):. select localupdateid from tbUpdate where UpdateID = ” (command if using WID: SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'select localupdateid from tbUpdate where UpdateID = ”' ) 5. Run a SQL query against the WSUS database to delete the update from the DB: exec spDeleteUpdate @localUpdateId= (command if using WID: SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'exec spDeleteUpdate @localUpdateId=' ) 6.

Start 'WSUS Service' service 7. Run Server Cleanup Wizard (I left all options selected) 8.

Run a synchronization (I don’t remember if I bounced the service again or not) 9. Re-approve update. If you’re using WID and don’t have SSMS, you can install SQL Server Native Client and the SQL Server Command Line Utilities from – by default, SQLCMD will be in c:program filesMicrosoft SQL Server110ToolsBinn.

Looks like these forums don’t escape gt/lt signs. Here are the queries from steps 4 and 5 again: 4. Run a SQL query against the WSUS database to find the local update ID (integer value):. select localupdateid from tbUpdate where UpdateID = ‘GUID from step 1’ (query if using WID: SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'select localupdateid from tbUpdate where UpdateID = ‘GUID from step 1’' ) 5. Run a SQL query against the WSUS database to delete the update from the DB: exec spDeleteUpdate @localUpdateId=Integer ID value from step 4 (query if using WID: SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'exec spDeleteUpdate @localUpdateId=Integer ID value from step 4' ).

Hi folks, and thanks again for the patience around these deployment issues. We have refreshed the Professional edition upgrades. Please sync the latest, try these downloads again, and report your results here, along with the edition that you’re attempting to deploy. The mitigation (i.e., KB article) for 'I clicked Upgrades before installing the hotfix' is in the works, and should be published soon.

Another blog post is coming regarding WSUS on 2008/R2 systems. Our focus has been on resolving the pressing issues with the 1511 release to WSUS. No current version of Configuration Manager is capable of downloading feature upgrades from WSUS. In order to deploy this content with Config Manager, you need to use task sequences.

This gap is under investigation, and the team is working on bridging it in a near-future release, though exact timelines are unknown at this point. Finally, as you may have noticed, we expired the original 1511 release from WSUS because it did not distinguish between Retail and Volume licenses. You should now see a clear distinction between these options in the title of the upgrades available in WSUS. Note that the applicability is the same, only the license is different. This still seems to fail for us, one machine is now permanently in a state of Restart for Updates.

We got the Install Now or Schedule for later pop up, we chose Install Now, and it restarted, but comes right back to 8.1 with a pending restart in the windows update panel. Can’t see new updates, can’t upgrade, totally nerfed. We’re going to reset that PC and start all over from scratch.

Windows Installed Updates Registry

We have Revision 201 approved for the test group, Pro, Retail and all other versions not approved. Our machines are all on the Pro release, en-us, non-volume. Should be as plain as it comes. Hi, I just installed WSUS on Windows Server 2012 (without R2) with the Hotfix.

I have set the update settings in the WSUS GPO to 'Auto download and notify for install' and Windows 10 reflects this as 'Notify for install'. This actually works and I am informed in Action Center about new updates. However, there is no Option to install the updates at reboot and shutdown – Windows shows just the normal shutdown and reboot options. 'Fast Shutdown' is already disabled. Is there a way to get this functionality working? On Windows 7 we are installing all updates during shutdown which is especially important for 3rd party updates like Java and Flash which cannot be installed during a browser is running. Thanks, Michael.

So, after waiting a month, I though 'to heck with with, lets enable Upgrades' 🙂 Fortunately I was plenty prepared by reading all the blog posts and comments, though it took a while to fully understand the Windows Servicing Models (well documented) in combination with Windows Update for Business (documentation on this really sucks, as well as the pre-coverage – it’s basically just a GPO us). So i prepared my ActiveDirectory OUs, created one for CurrentBranch and for CurrentBranchForBusiness, added the GPO tweaks and WSUS targeting, and here we go Everything went as planned, except I’m stuck at installing the 1511 Upgrade: -Windows Update Error on the machine: There were problems installing some updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: – Event ID 20 Error on the machine: Installation Failure: Windows failed to install the following update with error 0x8024200D: Upgrade to Windows 10 Pro, version 1511, 10586 – en-us, Retail. Any suggestions?

Jonatnav2 (11 Dec)/Jason (23 Dec): The upgrade (and all future upgrades) will apply to down-level as a matter of our servicing policy. This is primarily to reduce the number of entries in your WSUS/ConfigMgr consoles, especially considering that the end result is the same regardless of the targeted platform. You can quickly create a new Computer Group, then sort All Computers by Operating System, and finally right-click your Win10 machines and 'change membership' to the new group. This will allow you to target just the Win10 machines without restructuring your AD/GP hierarchy. Joe (12-13 Dec)/Timothy (22 Dec)/Paul (8 Jan): As Mike helpfully mentioned, there is now a hotfix available for Config Manager that allows feature upgrades to be downloaded from the SUSDB as expected. Please install to address the 'invalid certificate signature' errors mentioned here.

HeyAdmin: Although unrelated to this topic, the limitation you mention is fixed at 100 categories. Please ensure that you are not creating duplicate entries in the local publishing catalog–each pair of Vendor Name + Product Name will generate a new entry toward this 100-item limit.

Bill: Have you checked the deferral settings on these machines? Clients that are configured only to pick up CBB (i.e., have the 'defer upgrades' policy enabled) will consider the 1511 upgrade not applicable/needed. Michael (13 Jan): After you’ve downloaded the upgrades, they will install in the background and trigger an automatic restart after a fixed amount of time. By default, your machines should restart and complete the upgrade process at the next 3 AM opportunity.

In Win10, you won’t see the 'Install updates and restart' for these upgrades because a special type of restart is required, and it can’t be manually launched. Quinn: Definitely recommend adding the WSUS hotfix now, before you get into a situation where you might be synching Upgrades to your server.

If you use Config Manager, then you’ll want to consider that hotfix, as well, but the WSUS fix is crucial–plus it fixes the issue where Windows 10 machines appear as 'Windows Vista' in the UI. CurtK-CA: Thanks for confirming that you’re still having issues. Can you reach out to me directly (email blog author) so that we can properly troubleshoot your situation? Klaus: I’m not sure why you’re installing the x86 version of this hotfix, since WS12/R2 servers are always x64. Can you try using the x64 package instead? Ivan: Have you already added the MIME-type as suggested by alexx80? It looks like you haven’t downloaded the full package before launching installation.

Please submit all new issues with 1511 deployment via WSUS to the appropriate forum. Hi Steve, thanks for the info on the 'install updates and shutdown' question. Actually, I was not referring to Feature Upgrades in particular but to the option in general.

However, I now learned that the classic option to install updates during shutdown (what we know from Windows 7) seems to have already been removed from Windows 8, as this article and member of Microsoft writes: ———- You bring up a good point about the frequency and long times to complete installations during shutdown. I agree this can be frustrating especially when you are in hurry. On win8, we set out to strike a balance between always allowing user to have a choice and securing the system in a timely manner. We have done a few things here that cumulatively will improve the experience of updating during shutdown.

1) WU will install all updates before the 3 day pending restart message is shown and hence only the system re-initialization and pending file renames for the updates will be left to be completed during shutdown. This will shorten the time taken to “update and shutdown” compared to Win7/Vista where WU also does the installation during shutdown.

2) Since we are consolidating the restarts with the security updates, you should see the “Update and Shutdown” only when there is a pending restart (day 2 and day3 after a pending restart message is shown in login screen) ie 2 days in a month. In addition, on day 1 after the restart message is shown in login screen, you still have a choice to do just a “shutdown”. The intent here being that you can take the proactive action to restart the machine at your convenience. ——— Just for clarification in case other users are going to read my question.

To repeat The option as it it was in Windows 7 is gone and updates must be either scheduled for installation or installed completely manually. The 'Install and Shutdown' option in the start menu is only displayed in case an update has already been installed and requires a reboot. Any news on the KB article for those of us who ticked Upgrades before applying the hotfix? Seeing as WSUS installs as a role under 2012 R2 (we built a new server to replace WSUS 3.0 on 2008 R2), I don’t see how we were expected to know a hotfix even existed before WU updated the server and gave the new features such as Upgrades.

Of course some of us were going to tick the box, never before have I stopped to think 'before I enable this cool new feature to push out the Windows 10 November update, I should check for a WSUS blog and potential hotfix'. For those of you waiting for the article who ticked Upgrades before applying the patch. After many hours and days getting irate, this is what i have just done to solve mine: (Note: Deleting just the upgrade files that i had approved and tried to download didnt solve it for me as per the instructions previously provided in the comments section, i had to remove the lot of them!! Untick the Upgrades classication 2. Decline all 32 Windows 10 Upgrade files 3. Stop the WSUS Service 4.

Open SQL Management Studio and run the following 2 queries againt the SUSDB database select tbu.localupdateid, up. from PUBLICVIEWS.vUpdate up join tbUpdate tbu on tbu.updateid = up.UpdateId where up.DefaultTitle like ‘upgrade to windows 10%’ This should pull back all 32 upgrade files with the UpdateID for each one Then: exec spDeleteUpdate @localUpdateId= Copy the above exec sp command 32 times, put the UpdateID in for each listed from the first command and execute all 32 in one go – remove the obviously! Start WSUS Service 6. Run Server Clean Up WIzard leaving all boxes ticked 7.

Restart WSUS Service 8. Re-tick Upgrade Classification 9. Restart WSUS Service 10. Do a manual Sync 11.

Re-approve what upgrades are applicable to your appropriate Computer Group 12. Wait for your Windows Update on the client PC to grab the Upgrade Hope this helps somebody else!!! Thank you very much 'This Drove me Mad', great post. This worked for me. If you don’t have SQL Management Studio installed you can use SQLCMD.exe in step 4.

SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'select tbu.localupdateid, up. from PUBLICVIEWS.vUpdate up join tbUpdate tbu on tbu.updateid = up.UpdateId where up.DefaultTitle like ‘upgrade to windows 10%’' -o wsusdata.csv -W -w 1024 -s; This will give you a CSV file with ';' as the separator, (you can’t use ',' as it is used inside the fields). Then use: SQLCMD.exe -S.pipeMicrosoft##WIDtsqlquery -d 'SUSDB' -Q 'exec spDeleteUpdate @localUpdateId=137014' Replacing 137014 with the localupdateid from the wsusdata.csv file and do this for every entry. Follow all the other steps in the 'This Drove me Mad' post. Thanks to everyone here for this help. I scripted it into a single sql procedure with some a little bit of verbose output.

Hi folks, and apologies for the delay in getting this out there. We have published official guidance on how to resolve the issue where you synched Upgrades before installing the patch: We are not fond of directly editing the SUSDB, but we do encourage independent thought, so we’ll leave the workarounds (none of which we have confirmed or tested) in the comments section for posterity. We hope that the new post introduces you to the convenience that is PowerShell, if you’re not already familiar.

Thanks to those who were willing to share their expertise to help their WSUS community. For anyone still experiencing issues with the 1511 upgrade, please email us directly (Email blog author). We’ll share the known issues and workarounds in a future post, ideally with better turnaround time! I am uncertain where exactly the KB3095113 needs to be applied.

In our environment the Primary Site Server is still at WinSvr2008 R2 (and 2008r2 is supported for SCCM 1511). Our Primary site server does NOT have the Software Update Point Role (instead that is on a different server which has WinSvr2012 R2). My question is this How does it work with Primary Site Server (with WSUS 3.2 console only) and Software on a different server with WinSvr2012 plus WSUS 4, and KB3095113 patch. Where I am mixed up is Svr2008 supported for SCCM 1511, but the Software Update Role only compatible on WinSvr2012. Can this combination work as long at the latest and greatest is on the server with the SUP role? Or is there a problem leaving the Primary Site Svr at 2008R2 despite it being supported. I have the opposite issue to Bills comments at the end of Page 7.

I dont have the DisableOSUpgrade policy installed (infact i declined both updates in WSUS (KB3065987 and KB3065988) as per this MS article For all my Windows 7 clients they all refuse to pick the upgrade up even though the WIndowsUpdate.log says its found the upgrade applicabel to it – it always just says No updates available. I manually add in the following reg key and voila the WIn 7 machines start to see the upgrade and install it. HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdateOSUpgrade Then a DWORD (32bit) value of AllowOSUpgrade and set it to a value of 1 Really Microsoft it should not be this hard and tiresome to upgrade from 7 to 10. Well this is the KB that handles the Win10 upgrades from 7 and 8 – However it does not apply to enterprise editions nor any domain doined editions.

The config for the GWX.exe shows that it has a value of 'false' set again 'enabledomainjoined' so it stops any domain joined machines from seeing the Upgrade icon in there system trays and manually intstalling the update themselves – which is a good thinguntil it comes to those who want to stage the upgrades through WSUS – of which that KB has never been released to WSUS servers. Piss up in brewery.

I just wonder what testing in domain lab environments MS actually did for 7/8 to 10 upgrading. Because from where i sit it doesnt appear to be an awful lot!!! PS – the way around it is to add the registry key in via GPO but why the hell should we! Jesper: As indicated in, the issue occurs at the metadata level, specifically with parsing the metadata.

Update Not Applicable

Regardless of whether you actually approve the upgrades for installation, you’ll need to go through the steps on that page to delete the content and resync after you’ve installed the patch. Joe N: This KB needs to be applied on every WSUS with which you intend to distribute upgrades. With that said, we recommend installing it on every WS12/R2 WSUS server you have, since there is no major risk to doing so.

Mike Mott: Since Config Manager depends on WSUS for its metadata parsing, you’ll need this hotfix for any WSUS that supports CM 1511. Note that Config Manager does not support upgrade from Windows 7/8.1 to 10 via this mechanism (because that upgrade involves user interaction, and all CM operations are run without UI as SYSTEM): for that deployment, you’ll need to resort to your existing OS Deployment tasks, MDT, or image-based refresh. Brian: Yes, this key is unexpectedly interfering with the WSUS deployment scenario, but this one key isn’t the whole story. I’ve kept it under my hat for the time being because we aren’t done testing the recommended settings that you’ll need to change in order to unblock the Windows 7/8.1 upgrades to Windows 10.

Stay tuned for another post once we’ve gotten all the known nuances worked out for this scenario. ThisDroveMeMad: We feel your pain! It’s equally frustrating for us to light up a new and exciting scenario for the enterprise, only to have it impeded by factors outside WSUS’s control. We’re working on clarifying this scenario for you, and will have something as soon as we’re confident in the solution. The way it’s going now, unfortunately it doesn’t look like there’s any way around making GPO modifications.

More details next week, if not sooner. Oh, and Todd Meyers: We might not have conclusively answered your earlier question regarding MDT. We have tested the scenario, and we recommend keeping the two deployment technologies separate; i.e., either leverage in-place upgrades via WSUS or use your MDT to deploy a new OS, but not both on a given machine.

The two can coexist, but not without occasionally interfering with one another, so it’s best to keep them separate. Everyone: You may have noticed that KB 3095113 is now available via WSUS and Catalog.

This is the same content that was shipped in the original hotfix in October last year, so if you already have it, then there’s no need to deploy this patch. For those that were waiting for the direct release to WSUS, the wait is over. Scott: We in WSUS have no information on the free upgrade deadline at this time. That’s a high-level policy that will likely affect many aspects of our business, but for now we’re continuing to ship upgrades that apply to Windows 7/8.1 machines through WSUS. Bear in mind that any upgrades applying to Volume-licensed devices are not part of this free offering, so essentially the only affected edition is Professional in the WSUS scenario. Dan: What you’re seeing is the UI for 'Get Windows 10,' which is a client-side effort to migrate down-level machines to Windows 10.

It has nothing to do with WSUS-approved content, and if you click through that UI, you will download the upgrade from an external Microsoft site, not from WSUS. If bandwidth is a concern, then I recommend deploying the upgrade only through WSUS. For more information on this, check out. Keep in mind that any settings you change could affect future upgrades via WSUS, and may have to be reverted if you decide to deploy these upgrades at a later date. This Drove Me Mad: Haven’t forgotten your question or our commitment to provide guidance here. Steve — Your comment of Scott: We in WSUS have no information on the free upgrade deadline at this time. That’s a high-level policy that will likely affect many aspects of our business, but for now we’re continuing to ship upgrades that apply to Windows 7/8.1 machines through WSUS.

Bear in mind that any upgrades applying to Volume-licensed devices are not part of this free offering, so essentially the only affected edition is Professional in the WSUS scenario. I’m hoping that’s a misprint or incorrect statement. I’ve not found anything from MS that states the free upgrade doesn’t allow to Volume Licensing?! I have read that it won’t apply to Enterprise versions, but Home and Professional versions (regardless of OEM, retail, or volume licenses) are still eligible for the free Windows 10 upgrade I was lead to believe?

Please clarify, thanks. Hi everybody. I have the following error.

I’ve migrated de WSUS to a Windows 2012, V.6 of WSUS, and Clients (computers) can’t synchronize with WSUS UNLESS i push MANUALLY the button of 'Search Upgrades'. If not, wuauclt.exe /resetauthorization /detectnow or just wuauclt.exe /detecnot doesn’t work.

It happens to me on computers with Windows 10, 8, 7, etc. Can anybody help me with this?? I’ve already done the same migration of another WSUS for SERVERS (Windows 2012, 2008, 2003) and it worked fine. Thank you very much. I have WSUS on my 2012 (not R2) server and I am trying to install KB3095113 and it keeps failing with the 0x8000FFFF error.

I have tried to install it both from Automatic Updates and manually downloading the file and running it and both time it fails. I have tried running it as the Local admin and domain admin I have verified the KB3095113 update was not previously installed.

Attempting to use the WindowsUpdateDiagnostic program results in an error as well and looks like it might be an Elevation issue which is odd given the admin is running it (both local and domain) and there is no option to run in elevated mode right clicking. Please advise as we would like to be able to offer the Upgrade Category in WSUS for Windows 10 and have not checked the box for it. Hello Together, I read the comments well but could not find a solution to my Problem yet: We are running our WSUS on Windows Server 2012 R2. I have two Windows 10 Pro Clients (Build 10240) which don’t apply the 1511 Upgrade. The WSUS has the hotfix 3095113 installed.

The Upgrades, e.g. 'Upgrade to Windows 10 Pro, Version 1511, 10586 – de-de, Retail' are available and approved for a test Group in which both Clients are located. Now neither the Clients are finding this update nor is the WSUS showing any Computers which require the 1511 upgrade. On the Clients I already ran wuauclt /detectnow, /reportnow, searched for updates and rebooted several times.

WindowsUpdateLog schows only '0 Updates found' Since I can’t say for sure if I installed KB3095113 after I enabled the Upgrade download, I performed the suggested steps (deactivate Upgrades, delete Upgrade files, activated Upgrades again). Thanks for help, Christoph. Jesse R I’m hoping that’s a misprint or incorrect statement. I’ve not found anything from MS that states the free upgrade doesn’t allow to Volume Licensing?! Everything I’ve heard from the licensing team at my VAR and VL support confirms what Steve said. There have been a lot of fights on Reddit/Spiceworks about this with people saying they’ve been told things both ways, but I can say that I’ve confirmed with four different people (account manager + 3 different calls to Microsoft) and they’ve all told me the process when it comes to VL free upgrades is as follows: 1) If you purchased VL Windows and it has active SA, you’re good to go under those SA rights you can upgrade to 10.

2) If you purchased a machine with an OEM license and left the OS alone (i/e it’s still running that OEM Windows) you can upgrade under the free offer because you have an OEM instance of Windows 7/8 which is eligible. 3) If however you purchased a machine licensed with OEM, and then re-imaged it with your VL re-imaging rights you can NOT get the free upgrade in it’s current state. Because a VL key was used to activate the machine it’s not eligible under the upgrade offer which only applies to retail & OEM. In this situation you’re supposed to revert the machine back to it’s OEM state, perform the free upgrade which creates the digital entitlement, after which you can re-image the machine with VL 10 as long as you meet the other re-imaging requirements for Win 10, yes that does mean three OS installs and lots of wasted time. I know, that last part sucks, it’s the situation I’m in too which is why I really wanted to disprove it, but I’ve yet to find a legitimate source that says otherwise. A lot of people will point you to a word doc that can be downloaded from Microsoft’s site & signed by a VLSC admin, but all that says is it entitles you to use VL media to complete the upgrade rather than download it from Windows Update, you still have to be starting from an OEM/Retail instance of the OS.

After suffering the pains of this not working for months, I built a fresh Server 2012 R2 box and installed the WSUS role, followed by the hotfix (before ticking Upgrades). Thinking this would work, I was feeling confident. Ah, I hadn’t put the.esd MIME type into IIS on this new server.

That still didn’t work! What else could it be? Fresh clean server, hotfix, MIME type.that’s everything, surely? Then after much web-searching I found reference to an AllowOSUpgrade key (and a potential DisableOSUpgrade key, but we didn’t have that set). I set the AllowOSUpgrade key to 1, rebooted and then went into Windows Update.

I didn’t even have to check Check for updates, as in the middle of the screen was the prompt to Get started on upgrading to Windows 10. I haven’t yet started the upgrade, as in my excitement I wanted to post on here in case anyone needs to make the same change. The registry key by the way is at HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion WindowsUpdate OSUpgrade and the AllowOSUpgrade key needs changing from 0 to 1. Hope this helps someone at least 🙂. Thank you for helping with this issue! We are having the same problem. I looked up the article with the powershell commands.

Would I just run the scripts and that’s it? Or is there something I need to do before that?

Your comment: “Again, be sure that you perform the deletion step on the WSUS server that is highest in your hierarchy first, and then work your way down; otherwise, your deletions may be replaced by the USS on the next sync attempt.” Does this step need to be done first before running the scripts or does the ps scripts take care of that? I can decline and run the cleanup before running this if that is what you mean. Please let me know, Thanks again for your efforts! If you plan to distribute feature updates (Upgrades) in your environment, then we strongly encourage that you migrate all servers to a version of WSUS that can handle this sort of traffic. To answer your question, if you never sync the Upgrades content to the WSUS 3.2 server, then it should be fine; however, any future attempt to do so must be expected to fail. Additionally, you’ll want to install KB3159706 – – and follow the steps outlined in that KB in order to fully enable your servers to sync and distribute this content.