List of Available Hotfixes for Windows 7

Page 22 of 33 FirstFirst ... 12202122232432 ... LastLast

  1. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #211

    -Article ID: 2932722 - Last Review: April 9, 2014 - Revision: 1.0
    Internet Explorer stops responding when you try to save a file from a WebDAV folder.

    Symptoms:
    Consider the following scenario:
    • You install Internet Information Services (IIS) on a server that is running Windows Server 2008 R2 or Windows Server 2012.
    • You configure the server as a Web Distributed Authoring and Versioning (WebDAV) server.
    • You map a network drive to the WebDAV folder on a client computer that is running Windows 7 or Windows 8.
    • You start Internet Explorer 9 or Internet Explorer 10 on the client. On the Tools menu, you click View downloads, click Options, set the network drive in the Default download location box, and then click OK.
    • You access a web server from Internet Explorer 9 or Internet Explorer 10, select a file, and then click Save.
    In this scenario, Internet Explorer stops responding for a while, and the file cannot be saved.

    To apply this hotfix, you must be running one of the following operating systems:
    • Windows 7 Service Pack 1 (SP1)
    • Windows Server 2008 R2 Service Pack 1 (SP1)
    • Windows 8
    • Windows Server 2012
    Review and request hotfix:
    Internet Explorer stops responding when you try to save a file from a WebDAV folder
      My Computer


  2. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #212

    -Article ID: 2932119 - Last Review: April 10, 2014 - Revision: 1.0
    Incorrect DNS queries cause unnecessary network traffic when you start GPMC or GPUpdate in Windows 7 SP1 or Windows Server 2008 R2 SP1.

    Symptoms:
    You have a computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1. When you start the Microsoft Group Policy Management Console (GPMC) or Group Policy Refresh (GPUpdate), some incorrect DNS queries are generated. This causes unnecessary network traffic.

    Cause:
    This problem occurs because queries to service location (SRV) resource records are not bypassed correctly when Group Policy APIs are called.

    Review and request hotfix:
    Incorrect DNS queries cause unnecessary network traffic when you start GPMC or GPUpdate in Windows 7 SP1 or Windows Server 2008 R2 SP1
      My Computer


  3. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #213

    -Article ID: 2916915 - Last Review: April 10, 2014 - Revision: 4.0
    Outlook may take two to three minutes to connect to an Office 365 mailbox.

    Symptoms:
    Consider the following scenario:
    • You have a third-party proxy server that enables communication only over port 80.
    • You configure a computer that is running one of the following operating systems to use this proxy server for all protocols:
      • Windows 8.1
      • Windows Server 2012 R2
      • Windows 7
      • Windows Server 2008 R2
    • You configure the proxy bypass list to contain settings for internal servers.
    • You enable the Bypass proxy server for local addresses option.
    • You configure Microsoft Outlook 2010 or Microsoft Outlook 2013 to connect to the newest Microsoft Office 365 mailbox (Wave15).
    • You start Outlook 2013, and it tries to connect to Outlook.Office365.com.
    In this scenario, it takes two to three minutes to obtain the initial connection.

    Cause:
    This problem occurs because RPC waits for the direct connection to time out before it selects the proxy server. This causes the delay.

    This hotfix adds the following non-user-configurable registry key:

    Registry location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc

    DWORD name: ConnectionOptionsFlag
    DWORD value: 00000001
    Note: Changing this registry key will not change the RPC behavior. This key is added only to indicate the presence of a new HTTP connection option.

    Note: See chapter "Resolution" for further explanations on the "How to".

    Applies to

    • Windows 8.1
    • Windows 8.1 Enterprise
    • Windows 8.1 Pro
    • Windows Server 2012 R2 Datacenter
    • Windows Server 2012 R2 Essentials
    • Windows Server 2012 R2 Foundation
    • Windows Server 2012 R2 Standard
    • Windows 7 Professional
    • Windows 7 Enterprise
    • Windows 7 Ultimate
    • Windows Server 2008 R2 Datacenter
    • Windows Server 2008 R2 Enterprise
    • Windows Server 2008 R2 Foundation
    • Windows Server 2008 R2 Standard
    • Microsoft Outlook 2013
    • Microsoft Outlook 2010
    Review and request hotfix:
    Outlook may take two to three minutes to connect to an Office 365 mailbox
      My Computer


  4. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #214

    -Article ID: 2927111 - Last Review: April 11, 2014 - Revision: 1.0
    A BITS multirange transfer of a large file fails.

    Symptoms:
    On a computer that is running Windows 7 Service Pack 1, a Background Intelligent Transfer Service (BITS) multirange transfer of a large file fails consistently.

    A .wim image may typically be over the 4 gigabyte (GB) limitation. In this case, the download of the image through BITS fails. Additionally, the following error message is logged in the PullD.log file:

    Code:
    <![LOG[CPullDPResponse::ReportPackageState return value 0x00000000.]LOG]!><time="time" date="date" component="PullDP" context="" type="1" thread="4252" file="pulldpresponse.cpp:375">
    <![LOG[Created FullDownload DTS job for package WKS00084, version 2]LOG]!><time="time" date="date" component="PullDP" context="" type="1" thread="4252" file="pulldppkgcontjob.cpp:634">
    <![LOG[Start Download package WKS00084 version 2]LOG]!><time="time" date="date" component="PullDP" context="" type="1" thread="4308" file="pulldppkgjob.cpp:331">
    <![LOG[ExecuteJob (2-InProgress) WKS00084.2 for package WKS00084, version 2]LOG]!><time="time" date="date" component="PullDP" context="" type="1" thread="4252" file="pulldppkgcontjob.cpp:179">
    <![LOG[WKS00084.2, 0x0 : DownloadingData]LOG]!><time="time" date="date" component="PullDP" context="" type="1" thread="5104" file="pulldpservice.cpp:721">
    <![LOG[WKS00084.2, 0x80004005 : BITS error: 'Unspecified error
    ' Context: 'The error occurred while the remote file was being processed.
    The following error message may also be logged many times in the DataTransferService.log from the pull-distribution point:

    Code:
    datetime CDTSJob::HandleErrors: DTS Job '{9AA2CAA8-FFF9-466F-AB4C-F5E7DA828AF0}' BITS Job '{733409C7-C94C-4483-8BFC-7E440451FC82}' under user 'S-1-5-18' OldErrorCount 0 NewErrorCount 1 ErrorCode 0x80004005 3888 (0x0F30)
    Then, after the retries are completed, you may find the following error message in the DataTransferService.log:

    Code:
    datetime DTS job {A810A272-FE69-4E3C-B2EF-8B4FDB533806} BITS job {C72D8837-6C8D-4A8F-9D62-4EC3804D3429} failed to download source file http://SCCM.server.com:80/SMS_DP_SMSPKG$/LAB0002D/sccm?/win8-base.wim to destination E:\SMS_DP$\LAB0002D\LAB0002D.1\win8-base.wim with error 0x80190194 3552 (0x0DE0)err 80190194
    # for hex 0x80190194 / decimal -2145844844
    BG_E_HTTP_ERROR_404
    # 1 matches found for "80190194"
    Applies to

    • Windows 7 Service Pack 1
    • Windows Server 2008 R2 Service Pack 1

    Note: Might superseded the
    -Article ID: 2863374 - Last Review: August 13, 2013 - Revision: 1.0
    The BITS bandwidth limitation transitions are not applied to the ongoing transfers in Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1


    Review and request hotfix:
    A BITS multirange transfer of a large file fails
      My Computer


  5. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #215

    -Article ID: 2939180 - Last Review: April 11, 2014 - Revision: 2.0
    RDP session freezes when you connect to a remote virtual machine that is running Windows 7 SP1.

    Symptoms:
    Consider the following scenario:
    • You have a virtual machine that is running Windows 7 Service Pack 1 (SP1).
    • You install the Remote Desktop Protocol (RDP) 8.0 Host, and you enable it by using Group Policy.
    • You connect remotely to the virtual machine.
    In this scenario, the remote desktop occasionally hangs, and then it recovers automatically in one of the following situations:
    • You wait for 120 seconds.
    • You minimize and then maximize the remote desktop client window.
    Applies to

    • Windows 7 Service Pack 1, when used with:
      • Windows 7 Enterprise
      • Windows 7 Home Basic
      • Windows 7 Home Premium
      • Windows 7 Professional
      • Windows 7 Starter
      • Windows 7 Ultimate
    Review and request hotfix:
    RDP session freezes when you connect to a remote virtual machine that is running Windows 7 SP1
      My Computer


  6. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #216

    -Article ID: 2931129 - Last Review: April 21, 2014 - Revision: 2.0
    "0x0000007E" Stop error on IPMIDrv!KCSRequestResponseEngine in Windows Server.

    Symptoms:
    On a computer that is running Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2, you receive a Stop error message that resembles the following:
    Code:
    STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4)

    Notes
    • This Stop error occurs in IPMIDrv!KCSRequestResponseEngine.
    • This Stop error describes a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED issue.
    • The parameters in this Stop error message vary, depending on the configuration of the computer.
    • Not all "Stop 0x0000007E" errors are caused by this issue.
    Cause:
    This issue occurs because the baseboard management controller generates a non-communication interrupt, and then the Intelligent Platform Management Interface (IPMI) driver sets an event for the interrupt unexpectedly.

    Resolution:
    To resolve this issue for Windows 8.1 and Windows Server 2012 R2, install update 2919355, or install the hotfix that is described in this article.
    To resolve this issue for Windows 8 and Windows Server 2012, install update rollup 2934016, or install the hotfix that is described in this article.
    To resolve this issue for Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1, install the hotfix that is described in this article.

    Applies to

    • Windows Server 2012 R2 Datacenter
    • Windows Server 2012 R2 Essentials
    • Windows Server 2012 R2 Foundation
    • Windows Server 2012 R2 Standard
    • Windows 8.1 Enterprise
    • Windows 8.1
    • Windows 8.1 Pro
    • Windows 8.1 RTM
    • Windows Server 2012 Datacenter
    • Windows Server 2012 Essentials
    • Windows Server 2012 Foundation
    • Windows Server 2012 Standard
    • Windows 8 Enterprise
    • Windows 8
    • Windows 8 Pro
    • Windows Server 2008 R2 Datacenter
    • Windows Server 2008 R2 Enterprise
    • Windows Server 2008 R2 for Itanium-Based Systems
    • Windows Server 2008 R2 Foundation
    • Windows Server 2008 R2 Standard
    • Windows Web Server 2008 R2
    • Windows 7 Enterprise
    • Windows 7 Home Basic
    • Windows 7 Home Premium
    • Windows 7 Professional
    • Windows 7 Starter
    • Windows 7 Ultimate
    Review and request hotfix:
    "0x0000007E" Stop error on IPMIDrv!KCSRequestResponseEngine in Windows Server

    Note: Might superseded the:
    -Article ID: 2674913 - Last Review: March 14, 2012 - Revision: 1.1
    IPMI subsystem cannot obtain power information when the BMC interrupt is enabled on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. => see post: #186
      My Computer


  7. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #217

    -Article ID: 2791738 - Last Review: April 29, 2014 - Revision: 3.0
    Network device has a number at the end of the device name in Windows 7, Windows 8, or Windows 8.1.

    Summary:
    On a computer that is running Windows 8.1, Windows 8, or Windows 7, when you install, remove, and then reinstall two versions of a network driver to the same device, it can cause the device name to have a number (such as "#2" or "#3") after the name in Device Manager, even though a single device is installed.

    The following picture shows an example:

    (See Attached Images)

    Resolution:
    A hotfix is available that prevents the duplicate friendly name issue from occurring, but the hotfix must be installed before the new version of the driver is installed. The link for this hotfix is available at the following Microsoft website:

    -Article ID: 2846340 - Last Review: April 21, 2014 - Revision: 6.0
    Duplicate friendly names of network adapters are displayed in Windows
    Duplicate friendly names of network adapters are displayed in Windows


    To apply this hotfix, you must be running one of the following operating systems:
    • Windows Vista Service Pack 2 (SP2)
    • Windows Server 2008 SP2
    • Windows 7 Service Pack 1 (SP1)
    • Windows Server 2008 R2 Service Pack 1 (SP1)
    • Windows 8
    • Windows Server 2012
    Note: just above resolution hotfix does not apply to Windows 8.1 (Only the article ID: 2791738).

    Infos:
    This occurs because of the way that Windows builds the friendly name for the device. It does not affect the functionality of the device.

    Applies to

    • Windows 8.1 Enterprise
    • Windows 8.1
    • Windows 8 Pro
    • Windows 8 Enterprise
    • Windows 8
    • Windows 7 Professional
    • Windows 7 Enterprise
    Review and request hotfix:
    Network device has a number at the end of the device name in Windows 7, Windows 8, or Windows 8.1
    Attached Thumbnails Attached Thumbnails List of Available Hotfixes for Windows 7-2791737.png  
      My Computer


  8. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #218

    Microsoft .NET Framework 4.5.2 for Windows



    Microsoft .NET Framework 4.5.2 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2.


    The Microsoft .NET Framework 4.5.2 is a highly compatible, in-place update to the Microsoft .NET Framework 4, Microsoft .NET Framework 4.5 and Microsoft .NET Framework 4.5.1. The offline package can be used in situations where the web installer cannot be used due to lack of internet connectivity.

    This version of the .NET Framework runs side-by-side with the .NET Framework 3.5 SP1 and earlier versions, but performs an in-place update for the .NET Framework 4, .NET Framework 4.5 and .NET Framework 4.5.1.

    Download The Microsoft .NET Framework 4.5.2 (Offline Installer):
    Download Microsoft .NET Framework 4.5.2 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2 from Official Microsoft Down


    Microsoft .NET Framework 4.5.2 Language Pack (Offline Installer) for Windows
    The .NET Framework 4.5.2 Language Pack contains localized resources for supported languages.

    Download The Microsoft .NET Framework 4.5.2 Language Pack (Offline Installer):
    Download Microsoft .NET Framework 4.5.2 Language Pack (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2 from Official
      My Computer


  9. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #219

    System Update Readiness Tool for Windows 7


    System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2014]

    This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found.

    x64bits

    x32bits
      My Computer


  10. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
    Thread Starter
       #220

    -Article ID: 2918550 - Last Review: May 8, 2014 - Revision: 3.0
    Computer leaks nonpaged pool memory when IPSEC traffic is configured to use AuthIP without encryption in Windows.

    Symptoms:
    Assume that a Windows-based computer is configured by using a specific IP Security (IPsec) rule (AuthNoEncap - AuthIP with NULL Encryption). When the computer receives User Datagram Protocol (UDP) traffic, a nonpaged pool leak occurs. If there is a large volume of traffic, the computer may become unresponsive.



    For example, you may encounter this issue in the following scenario:
    • You configure the computers in a domain to use Authenticated IP (AuthIP) only for IPsec and without encryption.
    • In the domain, a computer sends a large volume of UDP traffic to a remote computer.
    In this scenario, nonpaged pool memory usage increases on the remote computer. High UDP network traffic can completely exhaust the nonpaged pool memory. This causes the remote computer to become unresponsive until it is restarted.

    Note Windows-based computers that host the DNS Server role are an example of a workload susceptible to this memory leak, because they service UDP-formatted DNS queries from a large collection of unique clients. However, the issue can apply to any remote computer that receives sufficient UDP traffic.

    Prerequisites: To apply this hotfix, you must be running one of the following operating systems:

    • Windows 7 Service Pack 1 (SP1)
    • Windows Server 2008 R2 Service Pack 1 (SP1)
    • Windows 8
    • Windows Server 2012
    • Windows 8.1
    • Windows Server 2012 R2
    Review and request hotfix:
    Computer leaks nonpaged pool memory when IPSEC traffic is configured to use AuthIP without encryption in Windows

    ------------------------------------------------------------------------------------------------------------

    -Article ID: 2958122 - Last Review: May 13, 2014 - Revision: 1.0
    NetLogon 3210 events are logged after MSA renews it password in Windows 7 SP1 and Windows Server 2008 R2 SP1.

    Symptoms:
    On a computer that's running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1, the Managed Service Account (MSA) renews its password one time every 30 days. After MSA renews its password, the system starts to report NetLogon 3210 events, and the security channel connection to the domain controller is disrupted. The NetLogon 3210 events are logged in the System log, and they resemble the following:

    Log Name: System
    Source: NETLOGON
    Date: datetime
    Event ID: 3210
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: computer_name
    Description:
    This computer could not authenticate with \\computer_name, a Windows domain controller for domain domain_name, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.


    Note To recover from this problem, you must restart the computer or restart the NetLogon service.

    Applies to

    • Windows 7 Service Pack 1
    • Windows Server 2008 R2 Service Pack 1
    Review and request hotfix:
    NetLogon 3210 events are logged after MSA renews it password in Windows 7 SP1 and Windows Server 2008 R2 SP1

    -------------------------------------------------------------------------------------------------------------

    -Article ID: 2956671 - Last Review: May 13, 2014 - Revision: 1.0
    High memory usage by mobsync.exe when you try to synchronize items in Windows 7.

    Symptoms:
    You have a computer that is running Windows 7. When you try to synchronize items that have long file names, the computer slows down, and the mobsync.exe process experiences high memory usage.

    Cause:
    This problem occurs because of an issue in the Client-Side Caching extension (Cscui.dll) when files have long paths.

    Applies to

    • Windows 7 Enterprise
    • Windows 7 Professional
    • Windows 7 Ultimate
    Review and request hotfix:
    High memory usage by mobsync.exe when you try to synchronize items in Windows 7

    ------------------------------------------------------------------------------------------------------------

    -Article ID: 2952507 - Last Review: May 13, 2014 - Revision: 1.0
    "0x00000050" Stop error when you browse files by using Windows Explorer on a remote desktop in Windows 7 SP1 or Windows 8.1.

    Symptoms:
    Consider the following scenario:


    • You have a computer that is running Windows 7 Service Pack (SP1), Windows 2008 R2 SP1, Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2.
    • You use Windows Explorer to browse files through remote desktop.
    In this scenario, the operating system crashes, and you receive a Stop error message on the computer that resembles the following:


    Code:
    STOP: 0x00000050 ( parameter1, parameter2, parameter3, parameter4 )


    Notes
    • This Stop error describes a PAGE_FAULT_IN_NONPAGED_AREA issue.
    • The parameters in this error message vary, depending on the configuration of the computer.
    • Not all "0x00000050" Stop errors are caused by this issue.
    Applies to

    • Windows 8.1 Enterprise
    • Windows 8.1 Pro
    • Windows 8.1
    • Windows RT 8.1
    • Windows 7 Service Pack 1, when used with:
      • Windows 7 Enterprise
      • Windows 7 Home Basic
      • Windows 7 Professional
      • Windows 7 Home Premium
      • Windows 7 Starter
      • Windows 7 Ultimate
    • Windows Server 2008 R2 Service Pack 1, when used with:
      • Windows Server 2008 R2 Enterprise
      • Windows Server 2008 R2 Datacenter
      • Windows Server 2008 R2 for Itanium-Based Systems
      • Windows Server 2008 R2 Foundation
      • Windows Server 2008 R2 Standard
      • Windows Web Server 2008 R2
    Note: just above resolution hotfix does not apply to Windows 8.1.
    Refer inside this Article ID: 2952507 to the "Resolution" chapter: To resolve this issue for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2, install update rollup 2955164.


    Review and request hotfix:
    "0x00000050" Stop error when you browse files by using Windows Explorer on a remote desktop in Windows 7 SP1 or Windows 8.1

    --------------------------------------------------------------------------------------------------------

    -Article ID: 980380 - Last Review: May 14, 2014 - Revision: 3.0
    Windows stops responding if SMB v1 protocol is used to access shared files.

    Symptoms:
    When you use Server Message Block (SMB) version 1 protocol to access some shared files by using a computer that is running Windows Server 2008 R2, Windows 7, Windows Server 2008, or Windows Vista, the computer stops responding under a heavy stress situation. Additionally, the computer does not recover until you force the computer to restart.

    Cause:
    This issue occurs because of a deadlock in the Mrxsmb10.sys driver.

    Applies to

    • Windows 7 Enterprise
    • Windows 7 Professional
    • Windows 7 Ultimate
    • Windows Server 2008 R2 Datacenter
    • Windows Server 2008 R2 Enterprise
    • Windows Server 2008 R2 for Itanium-Based Systems
    • Windows Server 2008 R2 Foundation
    • Windows Server 2008 R2 Standard
    • Windows Vista Business
    • Windows Vista Enterprise
    • Windows Vista Home Basic
    • Windows Vista Home Premium
    • Windows Vista Starter
    • Windows Vista Ultimate
    • Windows HPC Server 2008
    • Windows Server 2008 Datacenter without Hyper-V
    • Windows Server 2008 Enterprise without Hyper-V
    • Windows Server 2008 for Itanium-Based Systems
    • Windows Server 2008 Standard without Hyper-V
    • Windows Server 2008 Datacenter
    • Windows Server 2008 Enterprise
    • Windows Server 2008 Standard
    • Windows Web Server 2008

    Review and request hotfix:
    http://support.microsoft.com/kb/980380/en-us
    Last edited by NoN; 14 May 2014 at 16:25.
      My Computer


 
Page 22 of 33 FirstFirst ... 12202122232432 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:07.
Find Us