Windows Server 2008 R2 Sp1 Download

NOTE: This blog post was reviewed and approved by peers and program management of the team responsible for production and release of this convenience rollup. Robert Smith here to let you know about a new convenience rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1.

Download complete rom set for mame. Sep 11, 2018 - The latest MAME ROMSET (requires version of MAME to play – download from MAMEDEV) is sporting some huge changes (see below).

1. Windows Server 2008 R2 Sp1 Download

Microsoft has released a one-time convenience roll-up for Windows 7 with Service Pack 1 (SP1) and Windows Server 2008 R2 with Service Pack 1 (SP1). This rollup contains security, non-security, and hotfixes going back to SP1 and up to April of 2016.

Since SP1, there have been well over 1,000 updates released in one form or another, including security updates, “hotfixes”, and other Windows updates. Here are links to the details: This roll-up is currently categorized by Microsoft as “optional”. This means that there is no means by which this update will be automatically applied to any computer.

Feb 27, 2011  Windows 7 and Windows Server 2008 R2 SP1 helps keep your PCs and servers on the latest support level. It also provides on-going improvements to the Windows Operating System (OS), by including previous updates delivered over Windows Update as well as continuing incremental updates to the Windows 7. Nov 30, 2016 - Even more interesting is that Microsoft has finally released Windows Server 2008 R2 Service Pack 1 BETA. I mentioned the requirements for.

1. Feb 22, 2011 - Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new.
2. Windows server 2008 r2 download iso full version free download - Windows 7 and Windows Server 2008 R2 SP1 ISO, Windows Server 2003 R2 Platform SDK ISO Download, Microsoft Windows Server 2008 R2 64-Bit, and many more programs.

This update is available in the Microsoft Update Catalog at the following location: The term “convenience roll-up”, in this context, is not a technical term. The most recent example of a convenience rollup for Windows 7/Server 2008 R2 was the “Slow Boot, Slow Logon” roll-up;, (AKA “ Enterprise Rollup“). Like KB2775511, KB3125574 carries guidance from Microsoft that is different than many updates released from Microsoft, which is as follows: “This article describes a convenience roll-up for Windows 7 Service Pack 1 (SP1)-based and Windows Server 2008 R2 SP1-based computers.

This roll-up package is inclusive of all updates released after the release of SP1 for Windows 7 and Windows Server 2008 R2, up through April 2016. This convenience roll-up is intended to make it easy to integrate fixes released after Service Pack 1 for Windows 7 and Windows Server 2008 R2 computers. We recommend that you include this roll-up package in the image creation process to set-up a machine faster by integrating this roll-up package.” There are several reasons Microsoft has released this roll-up at this time: To help customers “catch up” with available updates, including hotfixes, many of which are not available through any other means except direct download from KB articles, one-by-one. To help customers get consistent code levels with Windows 7 SP1 and Windows Server 2008 R2 SP1 operating systems, both of which are in “extended” support until. To help customers get the most consistent experience with the Windows 7 SP1 and Windows Server 2008 R2 SP1 family of operating systems as they evaluate the next platform. In the event diagnostic efforts are needed in current production environments, there is less chance that an available update needs to be applied before analysis and/or remediation can begin.

The goal is to reduce time-to-resolution for diagnostic or analysis efforts, and helping to reduce the total cost of ownership (TCO). To ensure that Windows 7 SP1 / Windows 2008 R2 SP1 computers have the same updates used by Microsoft servicing team when testing What is included in the Windows KB3125574 convenience rollup: Most of the servicing fixes that were released after the release of SP1 for Windows 7 and Windows Server 2008 R2. Most “hotfixes” released since SP1. Updates to “core”.NET components only (no updates to.NET versions that were not released with Windows 7 and/or Windows Server 2008 R2 SP1 at the time of SP1) Updates for Windows client, Windows server, and most components of each.

What is not included in the Windows KB3125574 convenience roll-up: “Platform updates” to Windows, such as, are not included. KB2670838 was released through Windows Update and WSUS, so may already be installed. KB2670838 should be offered after the installation of this roll-up.

Updates to Internet Explorer 11 (IE11), which were not included with Windows 7 SP1 and/or Windows Server 2008 R2 SP1, are not included. Microsoft releases cumulative security updates for IE11 roughly once per month.

In addition, many enterprises have a complex testing matrix for IE11 updates, based on their catalog of applications, some of which are business critical. Updates to.NET versions not included with the original Windows 7/Server 2008 R2 installation are not included. Updates that require additional actions on the end-user such as registry changes are not included. Some issues that we have documented as part of the testing matrix for the KB3125574 roll-up: When installing this roll-up to a new installation of Windows 7 SP1 and/or Windows Server 2008 R2 SP1: o “Servicing Stack Update” must be installed first, or the roll-up will report “the update is not applicable”. Update KB3020369 is a relatively small update and can be applied with no reboot. This roll-up consumes approximately 2 GB of disk space after installation.

O During installation, this roll-up may use approximately 4 GB of disk space. About ½ of the 4 GB will be released during the restart after installation, as the temporary disk space used by the roll-up installer is released.

The Disk Cleanup Wizard (DCW) can be used to reclaim disk space used by superseded updates on both Windows 7 SP1 and Windows Server 2008 R2 SP1. Some notes on DCW: o On a brand new OS installation, with no previous updates installed there is no space to be reclaimed by using the DCW with Windows Update Cleanup option. O On an OS installation that has been in service for some time and has had a lot of updates installed previously, there is a potential to reclaim the disk space used by superseded updates. O On Windows Server 2008 R2 SP1, the only supported way to get the DCW is to install the “Desktop Experience” feature, which adds the DCW. This may be a good option if preparing a server image. Running the DCW, especially with the “Windows Update Cleanup” option will ensure the disk space footprint will be as small as possible.

O Charity Shelbourne published a great blog post that covers DCW in great detail here: Third-party security software can potentially interfere with the installation of the convenience rollup. If during the rollup installation the installation stops and rolls back, it is possible something was blocked by the third-party security software. You can check the logs of the security software which should document if that is fact the case. There are good troubleshooting steps for this scenario in the following Microsoft articles: You can’t install updates in Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 For those about to create a new image based on Windows 7 SP1 and/or Windows Server 2008 R2 SP1 this roll-up may be for you.

As always, test, test, test, and in as many different environments as possible. And finally, you may be interested in a blog post on Windows updates here because of some changes coming such as monthly rollups: There will be a new class of optional updates coming on the 3rd Tuesday of each month that should be reviewed, evaluated, and tested where practical (these will be made recommended patches on the following 2nd Tuesday (AKA Patch Tuesday) if no issues are found). These non-security updates will be applicable to Windows 7 SP1/Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2/Windows 8.1 operating systems. These updates will include non-security fixes only, and per the TechNet blog post are going to be roll-ups. NOTE: There are different rollups for the individual operating system families; ie, the convenience rollup for Windows 7/2008 R2 would not apply to Windows 2012 or Windows 8.1/2012 R2. Thank you for your consideration. Microsoft Premier Services and the Windows Customer Experience teams.

The reasons given for this rollup leave me confused. These reasons seem to suggest that there are large numbers of Win7 systems running without being kept at current update levels? To me, the single largest reason for a comprehensive rollup is new system deployment.

We need simpler, faster, more reliable and automatable ways to install the OS and get it fully up to date before putting it into daily usage. Personally I would like to see Windows Update become a first-class PowerShell citizen.

Allow fully scriptable reporting and updating, including any necessary reboots. Hi Brandon, Thank you for the detailed explanations, I’ve performed a couple of tests on freshly installed Windows 7 in VM, and some things looks strange for me. Can you please add some additional clarity on why some updates was added to this rollup, and some are not? 1) Rollup doesn’t have any recent Windows Update Client update(s), so after rollup installation next search for updates is taking 2 hours.

For testing purposes I’ve installed December WUC before rollup, but rollup reverted some files back to older versions. 2) I see that some security updates was omitted (21 for Windows+3 for.NET 3.5.1), per explanations in article registry change updates, and updates to non-core components were excluded, but I don’t see either of these reasons apply to and, for example, while some rarely useful for users updates like are in rollup. Can you please explain in more details, why part of security updates was excluded?

Hello Px, I ran several new tests on the installation process. What I found was that when installing the rollup to a new installation of Windows 7 w/SP1, several factors can help decrease the overall time. The WU scan after the rollup takes a long time because of sifting through layers of available packages and package dependencies, compared to what is available from WU.

The WU client always performs this analysis to present the smallest list of updates. But here are some things that can improve that time: 1.

Disable your network connection until the reboot after installing the rollup. Otherwise the WU client may try to contact WU and start the process of comparing what is in the OS now versus what is available. It may not make that much difference, but you can set your Power Option to “High Performance”. On a VM this doesn’t make much difference because a VM gets what the host gives.

But if you can control the host, and it’s Hyper-V, you can change the host Power Option also to HP and this helps keep the processors ramped up at the expense of some additional heat and power consumption. When presented the option for Windows updates, choose the option “Ask me Later”. If we choose the option “Automatically install” Windows will start downloading everything in the background, and appears to wait until that process is complete before presenting the list of available updates. I was seeing over 4 GB of content being downloaded to my “C: Windows SoftwareDistribution” folder on an earlier test when I simply checked the “Automatically install updates” setting. Now, enable your network connection, open the WU client (wuapp), change the WU setting to “check for updates but let me choose whether to download and install them”, and then check for updates. This is the WU check that can take a long time. In a Hyper-V VM with plenty of CPU, RAM, and SSD backing disk, I was seeing over 2 hours here before I tried the steps above.

With these different settings the first WU scan after the rollup took about 1 hour. You should get presented a list of about 55 Important and 10 Optional updates, unless you have Enterprise or Pro, in which case you may get presented a list of language packs that are as many as 45 more optional updates in addition to the 65 above. If you don’t need those, you can choose to hide those and you shouldn’t see them again and your OS won’t download and cache all those before offering you the option to choose. I don’t know if Windows deletes the cache if you deselect those, but I prefer to not download them in the first place because I am kind of a disk space hawk.

Now when selecting updates to install, do not select any update that has anything to do with IE 8, unless you are absolutely not going to install IE 11. Also, if you don’t specifically need.NET 4.6.1, de-select that. Every install of.NET takes some time, followed by a security update for the same that also takes quite a bit of time. After selecting the packages I list above, I had 55 Important and 10 Optional updates, one of which was IE 11.

I chose all those and rebooted. After that, I had a list of 30 more updates, many of which were security updates to the.NET packages I installed on the previous step. I still chose not to install.NET 4.6.1 at this time, but installed the others. The 30 updates took my VM about 12 minutes, followed by two reboots back-to-back. After that, one more WU scan detected only one update; the.NET 4.6.1 package that I had chosen not to install previously. I hope this information helps you and others to reduce “time to live” for a new Windows 7 installation.

If you are working with an enterprise customer of nearly any size, and anticipate you might need to do this again, I would recommend using Sysprep and capture an image of what you have right here, using this as a base or “gold” image. The two tools you need; Sysprep.exe and Dism.exe are built into Windows 7. The only other thing you would need is a place to write out the.WIM file. If you have a VM, you could present a.VHD to that VM temporarily on the SCSI interface. You could also use a USB thumb-drive (USB 3.0 highly recommended). If you go down this road, grab the free Microsoft ADK and use that to customize your new image and even help build bootable media.

You can get it down to where you insert your thumbdrive, walk away, and depending on the device come back in 20-30 minutes and the OS is installed, fully patched, and ready to go. For the WU client and files being reverted to older versions, Microsoft Windows updates are not supposed to roll back versions of files that exist and are in use on the target OS. You want to check by “File Version” or “Product Version”, which is what Windows uses to determine which one to keep in the event there are more than one to choose from.

Any activity in this regard will be logged in one of three logs: 1. C: Windows WindowsUpdate.log 2.

C: Windows logs cbs cbs.log 3. C: Windows logs dism dism.log You have to copy the CBS.log to another location before you can view it. That log can get quite large, so you’ll either want a fast computer or open it with something other than Notepad.exe if for example it is 250 MB.

The WindowsUpdate.log tells the activity of the WU components in Windows and is good if you want to see exactly what is going on during the “checking for updates” phase. I hope this information was helpful. Let us know if we can be of further assistance.

PFE Microsoft Premier Services. The problem with WU is that it seems there must be some loop in the file/package dependencies, because search on patched W7 machines (without the convenience roll-up – btw. It doesn’t seem to fix that according to reports of reputable computer magazines) can take hours (depending on the speed of the CPU) after every patch day (i.e. Searched for updates in April, fully patched, update search finishes after some minutes (no new updates) update search on patch day in May took 1-3 hours or more and it probably will be the same on the patch day in June). Besides having to install current WU client (latest seems to be that from March 2016) according to reports by other Win7 users installing KB3145739 (released in April, should it not be installed already), KB3153199 and KB3156017 shortened the time to search updates on a computer with the last patches made in April from several hours to not more than about 7 minutes. The problem is that on those KBs probably won’t help on June’s patch day, because they probably will be superseded and so some other KB will be necessary to be installed before searching for new updates to prevent Windows 7 from heating one of your processor cores for very long time in “searching for extended update infos” phase. Maybe some of you could dig into this issue and fix the dependency loop or whatever causes that behavior.

I had reason to re-validate the sequence I have worked up, and I took careful notes about the timings. Here’s what I saw: 01: Starting point is Windows 7 Ultimate, 64bit, including SP1. Not domain-joined, no WSUS. 02: stop-service wuauserv; remove-item c: windows softwaredistribution WuRedir 03: kb3020369.

1 minute 04: kb3138612. 1 minute + restart 05: kb3125574. 11 mins + 5-minute restart 06: WU check for updates via GUI. 74 minutes to list of updates: 53 important, 43 optional (34 are langpacks which I selected and hid) 07: Select 51 important and 9 optional, click install button. 37 minutes + restart 08: WU check for updates. 17 minutes to list of 23 important, 0 other.

09: Select all 23 updates, push install button. 13 minutes + restart 10: WU check for updates. 3 minutes to list of 2 important, 0 other. 11: Select both updates, push install button.

1 minute (no restart) 12: WU check for updates. So that’s about two and a half hours total, to go from a brand new SP1 install to fully updated with no more important, recommended, or optional updates left. This is accurate as of yesterday, June 2, 2016. Still a pain in the ass. But better than all day! This sequence was run on a Hyper-V system. The VM is assigned 4GB RAM.

Host disk is SSD. Steps 3-5 are me double-clicking on those updates in a folder they were previously downloaded to. Downloaded from the Update Catalog. Each one will require another click to confirm.

Step 2, stopping the WU service and removing the WuRedir folder seems to trick wusa.exe (which is the installer for standalone updates) into skipping the “searching for updates” phase, which can sit and spin for hours. The WU service will be restarted and the WuRedir will be rebuilt as the rest of the updates are installed. Step 3, installing KB3138612, resolves some unspecified issues with WU and shaves a lot of time off of the following steps. Step 7, I un-checked two important updates related to IE8. It gets replaced by IE11 anyway.

As noted, I also hid all of the language packs. Hello Chucko, Yes, there is value because not many people notice that rollup contains most of the latest available hotfixes in addition to all the other fixes. Hotfixes used to be rolled up along with all the other updates into the next service pack. Since Windows 7 did not have a next service pack other than SP1, all the hotfixes created since SP1 that were publically released were only discoverable through the respective KB article and had to be downloaded one-by-one, which was a painful process. Windows fixes are cumulative, meaning the highest numeric version of a fix is supposed to contain all the fixes previous to that fix for a given component, such as Tcpip.sys and so on.

So even though there may have been 15 fixes for Tcpip.sys since SP1, we only need the latest one to included that fix and all previous, including security fixes. That’s where this rollup comes in. I personally spent a lot of time tracking Windows hotfixes because there were some that were nearly mandatory for things like Failover Cluster, SMB server, and so on. There were fixes that weren’t on Windows Update or anywhere else that I would recommend to customers for performance, reliability, and data integrity issues that were only found in hotfixes.

I have had very good success with proactive hotfix recommendation, especially when we get a fix deployed for say a blue-screen, and the customer never experiences the blue-screen. So back to the roll-upwe are getting most (not all) of the latest fixes for most components in the operating system; both client and server. That’s why there is good value in applying this roll-up to a system that has been in production for some time and is already up-to-date as far as Windows Update is concerned. I would like to add that if you have such a system, you will be sure to want to run the Disk Cleanup Wizard with the Windows Update Cleanup option, which you will see if you start Cleanmgr elevated, or click “elevate” button. This only applied to Windows 7 systems and Windows Server 2008 R2 systems that have the Desktop Experience component added in though “Add Roles and Features”.

Windows Server 2008 R2 Sp1 Download

It’s worth it because I have seen numerous systems where I was able to reclaim 2-3 GB of disk space. Not only that, you decrease the number of fixes on disk, the number of catalog files for those fixes, the number of fixes in the local WU database, so subsequent Windows Update scans should complete in less time. Note that once you run the Disk Cleanup Wizard and WU Cleanup, you will need to reboot for that cleanup to occur. On a system that has been in production for years and never had this run, this could take a few minutes or more to complete.

A fellow PFE Charity Shelbourne wrote a blog on how to automate that, here: Thanks, Robert M. Greetings Microsoft engineering team, This document contains detailed information about issues that end users are experiencing with Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1. These issues are not a result of a misunderstanding or misinterpretation; they’re real issues that degrade the experience of the rollup. Therefore we sincerely hope you take this seriously and urge you to fix these issues as soon as possible. For simplicity’s sake, convenience rollup KB3125574 will be referred to as “the rollup”. Recommendation suggestion: The rollup doesn’t include the following optional feature packs, but it does contain their updated components (which were previously released as individual hotfixes or updates): Platform Update KB2670838, Remote Desktop Protocol 8.0/8.1, Windows Management Framework 4.0, Work Folders, DirectAccess Connectivity Assistant 2.0, Active Directory Lightweight Directory Services, Remote Server Administration Tools, Virtual PC, Server Essentials Connector, Active Directory Federation Services, KB2483177 Desktop Experience Decoder Update for Windows Server 2008 R2.

This means that the user needs to install those feature packs first (before rollup) so that the updated components contained in the rollup get installed when it’s installed afterwards. This should eliminate all their individual updates released before the rollup. The suggestion is: Add a notice or recommendation to the rollup KB article explaining that those feature packs or platform updates should be installed first. Like: Important: If you install one of those features after you install the rollup, you must reinstall the rollup. Therefore, we recommend that you install any of those features needed before installing the rollup. Known issues: Issue 1: Symptom: After installing the rollup, every SFC integrity scan reports and fixes an error regarding this file:%windir% system32 drivers en-US usbhub.sys.mui (en-US differs based on OS language).

Cause: The issue occurs because usbhub.sys.mui is referenced and linked in two winsxs components: usb.inf.resources usbport.inf.resources In the “Vanilla” Win7 image, both have the same file version: 6.1.7600.16385. But the rollup only includes the usbport.inf.resources component, and usbhub.sys.mui is updated to version 6.1.7601.23403. Now, when SFC is run First it checks component usb.inf.resources (version 6.1.7600.16385) and it finds the newer file (version 6.1.7601.23403) in System32 drivers en-US, so it replaces it from the winsxs store with (version 6.1.7600.16385). Second it checks usbport.inf.resources (version 6.1.7601.23403), but now it finds the older file (version 6.1.7600.16385) in System32 drivers en-US, so it replaces it from the winsxs store, this time with version 6.1.7601.23403. And so on With each scan, it performs the same replacement operations.

Here is a snippet of CBS.log: CBS.txt found at http: windows-update-checker.com FAQ CBS.txt Possible Resolution: Release a hotfix that includes the usb.inf.resources component with an updated usbhub.sys.mui file to match rollup version 6.1.7601.23403, or a hotfix that includes both components with a higher version. Issue 2: Symptom: If the rollup is integrated into an offline image and update KB2603229 is installed on a live running system that was installed from the updated image, KB2603229 will have no effect and won’t fix the registry value.

Cause: The rollup supersedes the component of KB2603229, which represents a generic command: UpdateWowRegisteredOwner.exe, which must be executed on live running systems. However, since the rollup version of this component is higher (6.1.7601.23403), it prevents UpdateWowRegisteredOwner.exe from running when KB2603229 is installed because its versions are 6.1.7601.17671/6.1.7601.21795. Resolution: Release a refreshed KB2603229 or a new update with a higher component version than 6.1.7601.23403 If you don’t, advise users to install KB2603229 first and not to integrate the rollup. Or, if the rollup is integrated, advise users to execute this command manually through an admin command prompt:%windir% winsxs amd64microsoft-windows-g.ewowregisteredowner31bf3856ad364e356.1.7601.23403nonee48b101cd455f329 UpdateWowRegisteredOwner.exe Update: As we have unfortunately found out, the command above does not work if you integrate the rollup into an installation DVD. After the system is installed, the registry values of: HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows NT CurrentVersion RegisteredOrganization HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows NT CurrentVersion RegisteredOwner are no longer “Microsoft”. For the command to work, you would need to reset the tow values to “Microsoft” first. But if the values are to be changed anyway, it makes more sense to use the correct values that can be found in these keys: HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion RegisteredOrganization HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion RegisteredOwner If you install the rollup on a live system, the values are correctly set and KB2603229 is not required.

Windows Update will still want to install it regardless. I have the update installed and last patchday it still took some time to get the updates on my Win7 PC.

The WU scan builds a large chain of updates, so in case you hide an update, Wu Shows the last update and so on. The Speed diffs have something to do with the updates released each month. If updates are offered that includes files that get updates very often you have such a large chain of updates. But if Microsoft Releases updates for files that don’t get regular updates (like Media Center updates) Wu doesn’t have to build this large chain and you see an improvement. The only real fix is the way MS build it in WIn10.

Release 1 large update each time and only provide Flash patches alone. It’s “Patch Day June 2016” To speed up searching for Windows updates you might want to install the updates from the KBs below (download them, reboot without network to stop WU searching), install them and plug in your network again and let the now very fast search begin) KB3145739 WU Update from April – if not installed yet (i.e.

Directly after installing convenience rollup) Current security updates for win32k.sys and graphics engine (also replacing win32k.sys) – the old KB numbers have been superseded: KB3161664 KB3164033 KB3164035 If you need the download links try those from the security bulletin summary if you can’t find them in the download center (BING didn’t find them some minutes after patch day begun). Many thanks to the people who found this workaround. Maybe some people responsible for WU/MU could have a look and create some other way to shorten the long update history of win32k.sys (or whatever else is causing the long delay) (or making interactive WU work in two steps (first offering the most recent version of these patches without searching for hours and then offering the remaining updates after reboot).

Microsoft has finally released the much awaited Windows 7 Service Pack 1 and Windows Server 2008 R2 SP1. The same Service Packs were made and then to and now they’re available to everyone. You can download SP1 from Windows Update but if you want to keep the installation setup with you, you can download SP1 from the links given below. Windows 7 Service Pack 1 is available to the users in the form of an ISO image which is about 2GB in size. Microsoft requires Windows Genuine Advantage validation in order to download the Service Pack 1. Just go to the below location, select your language, validate your Windows and download Windows 7 Service Pack 1 or Windows Server 2008 R2 SP1. If you don’t want to validate your Windows, you can download SP1 from the following direct link from Microsoft: 1.91 GB If you have previously installed Windows 7 SP1 Beta or, you’ll need to first and then install this final release.

If you're a creator or digital artist, you need to check out Clip Studio Paint.

You may want to read about. You can also automatically from Windows Update.