Microsoft Hotfix Download

[Lorin Searing]

Weguide you through the steps to search the Windows Update Catalog to find the updates that you want. Then, you can download the updates to install them across your home or corporate network of Microsoft Windows-based computers.

This content is designed for an advanced computer user. We recommend that only advanced users and administrators download updates from the Windows Update Catalog. If you are not an advanced user or an administrator, visit the following Microsoft Web site to download updates directly:

Windows Update: FAQ

Click the updates link on the pop-up page and Save to the default path, or right-click the link and select Save target as to the specified path. You can either type the full path of the folder, or you can click Browse to locate the folder.

Double-click each update, and then follow the instructions to install the update. If the updates are intended for another computer, copy the updates to that computer, and then double-click the updates to install them.

IT Professionals can use the Windows Update service to configure a server on their corporate network to provide updates to corporate servers and clients. This functionality can be useful in environments where some clients and servers do not have access to the Internet. This functionality can also be useful where the environment is highly managed, and the corporate administrator must test the updates before they are deployed.

For more information about how to use Automatic Updates in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

306525 How to configure and use Automatic Updates in Windows XP

Administrators Only (-2146828218) To install items from Windows Update, you must be logged on as an administrator or a member of the Administrators group. If your computer is connected to a network, network policy settings may also prevent you from completing this procedure.

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 316524 You receive an "Administrators only" error message when you try to visit the Windows Update Web site or the Microsoft Update Web site

The hotfix installer that is included with Windows XP and with Windows 2000 post-Service Pack 3 (SP3) updates includes functionality to support multiple hotfix installations. For earlier versions of Windows 2000, the command-line tool that is named "QChain.exe" is available for download.

For more information about how to install multiple updates or multiple hotfixes without restarting the computer between each installation, click the following article number to view the article in the Microsoft Knowledge Base:

296861 How to install multiple Windows updates or hotfixes with only one reboot

For more information about how to download files from the Microsoft Download Center, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scri...@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Microsoft releases a hotfix rollup when there are a several fixes for a component such as the Volume Shadow Copy Service (VSS). These rollups are more thoroughly tested than individual hotfixes but not to the same extent as service packs. When dealing with problems relating to a particular component, rollups can be a good solution. If you need to find rollups for a component, search on the word "rollup" and the component name or a description of the problem. Code distribution paths

Updates and service packs follow the GDR path, while hotfixes follow the LDR path. When you install a hotfix, it's a version not known to the GDR path. To prevent components from going backwards in the version, Microsoft releases both LDR and GDR components in the updates, which are smart enough to know which one you have and keep you on that path.

For example, say you installed a hotfix of volsnap.sys, a component used in creating volume snapshots. In this knowledge base, there are components for x86, x64 and IA64 platforms, and there are three x64 components:

Before installing any hotfix, check out the file version, release date, and required operating system and service pack. Make sure that the version of the component on your system is older than the one in the hotfix. If you have a newer version, then another hotfix has been applied.

Now, suppose you installed this hotfix on your server, and then a Windows update is installed with volsnap.sys. Since installation of the hotfix branched down to the LDR path, when updates come, this server will get them from the LDR path -- not the GDR path.

For example, let's say Service Pack 3 was released for Windows 2003. The fixes in the service pack have been tested, and this pack contains all the fixes in the LDR path. Once the service pack is applied, the machine returns to the GDR path moving toward the next Windows version. Updating to the next Windows version often requires installing the latest service pack for the existing OS.

Before installing a hotfix, test it in your lab and have the installation go through the normal change management process. In other words, treat a hotfix like a component that hasn't been thoroughly tested. Ultimately, it will end up in the next service pack or the next Windows version. In addition, a newer version of a hotfix contains the fixes from the older version. This makes it difficult to pinpoint what the older versions fixed. Therefore, on main components like NTFS.sys, it's good to update with the newest hotfix if you are having problems that you have isolated sufficiently to suspect these components. The table here lists the primary components related to Microsoft clusters:

The exception is storage drivers, including Microsoft's Storport.sys miniport driver, and the MPIO (Multipath I/O), DSM (device specific module) and HBA (host bus adapter) drivers. The drivers have to align with the supported versions of one another (not necessarily the newest ones) and storage vendors and Microsoft are continually releasing new products. If you do not pay attention to the drivers, it's easy to end up in an unsupported configuration. Your storage vendor will be able to tell you which versions you should have.

The most frustrating thing about keeping the storage drivers updated may be the treasure hunt that's required to find the latest Storport.sys driver. Microsoft releases it to solve specific problems, but like any other hotfix, old fixes are rolled into newer ones. While you may not have the problem the newest version is released for, you always want the latest version, and finding it isn't easy. Searching Google for Storport.sys is a good start -- then look at the knowledge bases to find the newest one. Again, make sure your current storage components support the latest version of Storport.

ABOUT THE AUTHOR:

Gary Olsen is a systems software engineer in Global Solutions Engineering at Hewlett-Packard. He authored Windows 2000: Active Directory Design and Deployment and co-authored Windows Server 2003 on HP ProLiant Servers. Olsen is a Microsoft MVP for Directory Services and formerly for Windows File Systems.

Microsoft Scripting Guy, Ed Wilson, is here. It is an absolutely lovely day down here in Charlotte, North Carolina in the southern portion of the United States. I mean, absolutely lovely. I am sitting outside on the porch, sipping a delightful cup of English Breakfast tea. I put in some lemon grass, jasmine, orange peel, and hibiscus flower. I also added a cinnamon stick for sweetness. The tea is robust and complex. If I close my eyes, it feels like I am in Florida, and I can hear the seagulls squawking. The breeze coming across the lawn adds to this effect. I am checking my email via my Surface Pro 3.

When I use the Get-Hotfix cmdlet, it returns the source of the information (my computer name), the type of update, the Hotfix ID, who installed the hotfix, and when it was installed. This information returns by default. The command and a typical output are shown here:

To answer the question about how many hotfixes per month are installed, I can use the Get-Hotfix cmdlet and pipe the results to the Group-Object cmdlet. I can then select the InstalledOn property as the property upon which to group. I can also get rid of the elements to have a cleaner display. Here is the command:

Cool. Now I have a list of the number of hotfixes that were installed and a sorted list of dates. I can see that in August 2014, there were three separate hotfix collections of 2, 13, and 1 (a total of 16 hotfixes for August).

One thing I discovered yesterday is that the hotfix you download comes in a password locked zip file. I didn't have access to the email that contained the password at the time, so it was a bit of a problem.

I just read this thread and although I'm not seeing symptoms, I thought I'd do the fix anyway as a preventive measure, based on what you said. In the process of starting to download the fix, I encountered this:

WARNING - WinXP Service Pack 3 is NOT including the REQUIRED WinXPUSBHotFix. For USB NI DAQ-6211, Warning at install upon first NI Max open and explore USB 6211, AND Yellow Triangle inside Icon. Means you NEED this:

Windows 7 Mainstream support ended January 13, 2015. Microsoft only provided security fixes after that. Your hotfix is not considered a security vulnerability. If you needed Extended support, then you would have paid for it. I can understand your frustration but your expectations are your own.

Applying (installing) a hotfix generally involves the same process as any software update. Most modern operating systems and desktop applications can download and apply updates automatically. Network administrators may use software programs to automate and simplify applying updates to the machines they manage.

3a8082e126