Here: This update rollup includes the following new features and improvements: Refreshed language packs Defence-in-depth security and Schannel hardening Support for newer hardware (boot order allowance, SD card improvements, USB debugging) Improved Web Services for Devices (WSD) printer support during network switches Performance and reliability improvements in clustered virtual machine mission-critical environments Improved manageability Additional hardware support (devices that have third-party disk encryption software enabled can now be upgraded to Windows 8.1 more easily) We attend a new ESD Refresh
It is the nov rollup. It reports large because it has updated language components. If you download it through Windows Update, it's a lot smaller (130MB for x64 version)
Why Nov 2014 rollup not called "Update 3" ? Is there option to download only the Nov 2014 rollup (not include all previous updates) ?
This is a rollup, not "update2 or 3". Update1 was a significant change, update2 would also be significant (because it would contain the new startmenu) but it was never released.
It is essentially 'Update 2'. Just because it doesn't have clearly identifiable changes it doesn't mean it doesn't contain significant changes and a large number of fixes that would qualify it being classed as a major update. It could be that Microsoft have moved away from the 'Update' moniker, simply because it was causing confusion. Update 1 was hardly the first update for Windows 8.1! In a sense, you could consider 'Rollup' as the new term for 'Update'. It's just a name anyway. You could call it 'Update 2', 'November Rollup', 'Service Pack 1', etc., it doesn't change the content of the update. People seem to think that major updates, those that warrant the label 'Update' etc., should contain clearly quantifiable changes like a new start menu etc. That simply isn't true. Since this update will likely be a requirement to install future updates, like 'Update 1' was, it really should be considered as 'Update 2). Windows seems to have a bit of an identity crisis at the moment, I'm sure Microsoft will work out the naming of the OS and the updates at some point. I disagree with the talk that Windows 10 will be the last major OS, and then all changes after that will be like update packs, so you essentially upgrade the OS continually. This would only lead to confusion, since calling Windows 10 as Windows 10 in 3 years time will be confusing in terms of updatedness, since it will be the equivalent of Windows 11 (for example). People are often stubborn in updating their system, then whinge and complain when things don't work. These issues may just happen to have been resolved in an update, yet they'll still refuse to install the update. A much better system would be to call Windows 10 based on year. So, Windows 2015 is Windows 10, and then bring out a 'new' Windows, with updated ISO's, every year or two years. Sure, it could still be using the same cumulative updating system, but at least in 2017 you will know to install Windows 2017, instead of Windows 10 Update 2 with October 2016 Rollup. Changing the label on the OS would hardly be an issue. Making updates mandatory would also make sense . None of this supporting 10 different variations with updates because people are too stubborn to install an update pack etc!
After installing the complete Nov rollup, comparing the packages.txt files before and after cleanmgr is run the following KB's are superseeded on my system: Spoiler 2950153 2956575 2964718 2966870 2969817 2971239 2971850 2972280 2973201 2977292 2978668 2979582 2981655 2988948 2992611 2993651 2993958 2996205 2996802 2999802 3002653 3002858 3002859 3003743 3004538 3005607 3006178 3006226 3007196 3008242 3008627 I allow no appx to install-disabled offline. Windows Store and UAC are also compltetely disabled. Finnally I disable quite a few "features" offline. This all together may make a difference on the total number of superseeded because, for instance, I have no media KB's installed as both WMP and WMC are disabled. My features.txt Spoiler Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Image Version: 6.3.9600.17031 Features listing for package : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 ----------------------------------------------------- | ----------------- Feature Name | State ----------------------------------------------------- | ----------------- Microsoft-Hyper-V-All | Disabled Microsoft-Hyper-V-Tools-All | Disabled Microsoft-Hyper-V | Disabled Microsoft-Hyper-V-Management-Clients | Disabled Microsoft-Hyper-V-Management-PowerShell | Disabled Printing-Foundation-Features | Enabled Printing-Foundation-LPRPortMonitor | Disabled Printing-Foundation-LPDPrintService | Disabled Printing-Foundation-InternetPrinting-Client | Enabled FaxServicesClientPackage | Disabled ScanManagementConsole | Disabled LegacyComponents | Disabled DirectPlay | Disabled SimpleTCP | Disabled SNMP | Disabled WMISnmpProvider | Disabled Windows-Defender-Default-Definitions | Disabled Windows-Identity-Foundation | Disabled MicrosoftWindowsPowerShellV2Root | Enabled MicrosoftWindowsPowerShellV2 | Enabled DirectoryServices-ADAM-Client | Disabled Internet-Explorer-Optional-amd64 | Enabled NetFx3 | Enabled IIS-WebServerRole | Disabled IIS-WebServer | Disabled IIS-CommonHttpFeatures | Disabled IIS-HttpErrors | Disabled IIS-HttpRedirect | Disabled IIS-ApplicationDevelopment | Disabled IIS-NetFxExtensibility | Disabled IIS-NetFxExtensibility45 | Disabled IIS-HealthAndDiagnostics | Disabled IIS-HttpLogging | Disabled IIS-LoggingLibraries | Disabled IIS-RequestMonitor | Disabled IIS-HttpTracing | Disabled IIS-Security | Disabled IIS-URLAuthorization | Disabled IIS-RequestFiltering | Disabled IIS-IPSecurity | Disabled IIS-Performance | Disabled IIS-HttpCompressionDynamic | Disabled IIS-WebServerManagementTools | Disabled IIS-ManagementScriptingTools | Disabled IIS-IIS6ManagementCompatibility | Disabled IIS-Metabase | Disabled WAS-WindowsActivationService | Disabled WAS-ProcessModel | Disabled WAS-NetFxEnvironment | Disabled WAS-ConfigurationAPI | Disabled IIS-HostableWebCore | Disabled IIS-CertProvider | Disabled IIS-WindowsAuthentication | Disabled IIS-DigestAuthentication | Disabled IIS-ClientCertificateMappingAuthentication | Disabled IIS-IISCertificateMappingAuthentication | Disabled IIS-ODBCLogging | Disabled IIS-StaticContent | Disabled IIS-DefaultDocument | Disabled IIS-DirectoryBrowsing | Disabled IIS-WebDAV | Disabled IIS-WebSockets | Disabled IIS-ApplicationInit | Disabled IIS-ASPNET | Disabled IIS-ASPNET45 | Disabled IIS-ASP | Disabled IIS-CGI | Disabled IIS-ISAPIExtensions | Disabled IIS-ISAPIFilter | Disabled IIS-ServerSideIncludes | Disabled IIS-CustomLogging | Disabled IIS-BasicAuthentication | Disabled IIS-HttpCompressionStatic | Disabled IIS-ManagementConsole | Disabled IIS-ManagementService | Disabled IIS-WMICompatibility | Disabled IIS-LegacyScripts | Disabled IIS-LegacySnapIn | Disabled IIS-FTPServer | Disabled IIS-FTPSvc | Disabled IIS-FTPExtensibility | Disabled MSMQ-Container | Disabled MSMQ-Server | Disabled MSMQ-Triggers | Disabled MSMQ-ADIntegration | Disabled MSMQ-HTTP | Disabled MSMQ-Multicast | Disabled MSMQ-DCOMProxy | Disabled WCF-Services45 | Enabled WCF-HTTP-Activation45 | Disabled WCF-TCP-Activation45 | Disabled WCF-Pipe-Activation45 | Disabled WCF-MSMQ-Activation45 | Disabled WCF-TCP-PortSharing45 | Enabled WCF-HTTP-Activation | Disabled WCF-NonHTTP-Activation | Disabled NetFx4-AdvSrvs | Enabled NetFx4Extended-ASPNET45 | Disabled MediaPlayback | Enabled WindowsMediaPlayer | Disabled Microsoft-Windows-MobilePC-Client-Premium-Package-net | Disabled Microsoft-Windows-MobilePC-LocationProvider-INF | Disabled Printing-XPSServices-Features | Disabled RasCMAK | Disabled RasRip | Disabled MSRDC-Infrastructure | Enabled SearchEngine-Client-Package | Disabled TelnetClient | Disabled TelnetServer | Disabled TFTP | Disabled TIFFIFilter | Disabled Xps-Foundation-Xps-Viewer | Disabled WorkFolders-Client | Disabled SMB1Protocol | Enabled The operation completed successfully. After cleanmgr the follwing had to be reinstalled to satisfy M$ update: Spoiler KB2959977 KB2980654 KB2990967 KB2995004
List of "affected" updates by November Rollup KB3000850 Superseded: Spoiler Code: 2926792 2936111 2950153 2953205 2953212 2955631 2956575 2959626 2959977 2964439 2964718 2966870 2969817 2969825 2971239 2971850 2972280 2972508 2973201 2973940 2977292 2979127 2979582 2980654 2981655 2988948 2991247 2992419 2992611 2993651 2993958 2996205 2996802 2998082 2999802 3002653 3002858 3003743 3004538 3004541 3005607 3005608 / winpe 3006178 3006226 3007196 3007507 iis 3008627 3010788 Included updates: Spoiler Code: 2920189 2917011 iis 2928120 rsat 2953176 iis 2961072 2962140 2958262 2965142 2967165-x64 2970215-x64 2971203 2973351 2978137 2979933 2981330 2981666 winpe 2982998 iis 2986484 2991202 2993100 2995004 3002885 3003727 3004907-x64 3008188 Included Rollups: Spoiler Code: 2955164 May 2014 2975719 August 2014 2984006 September 2014 2995388 October 2014 Code: Superseded = All components are replaced by higher versions Included = Some or all components have the same version Replaced updates that still show up in WU Spoiler Code: Important: 2894852 2920189 2959977 (as 2919355) 2961072 2962140 2973351 2978742 (ProWMC Edition) 3002885 2955164 2965500 (as 2955164) 2980654 (as 2962409) 2965142 2968599 2971203 2975719 2984006 2993100 (as 2975719) 2995004 (as 2975719 and/or 2984006) 2995388 3008188 Optional: 2958262 2998174 thanks to PointZero for help in verifying the list