List of Available Hotfixes for Windows 7

Page 3 of 33 FirstFirst 1234513 ... LastLast

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

    This one is an MVP (Sagar.S) trick:


    Fix: Windows Explorer Crashes in a particular Video folder in Windows 7


    Ever had such a problem, that when you are browsing your files and you reach a folder with Video files, and you encounter a ‘Windows Explorer Stopped Working’ Error’? If you have, then there is a simple solution for it.

    To be read at:
    Fix: Windows Explorer Crashes in a particular Video folder in Windows 7 | The Windows Club
      My Computer


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

    -Article ID: 2430365 - Last Review: October 4, 2010 - Revision: 1.0
    Windows Media Center: Black screen for several minutes when changing channels in Live TV:

    symptoms:
    Consider the following scenario:
    You are using Windows Media Center in Windows 7 to watch Live TV.

    You change to certain TV channels, and you see blank video and audio. If you stay tuned to the channel for several minutes, the video and audio eventually starts playing.

    Alternately, if you close and restart Windows Media Center, and restart Live TV, the video starts playing.

    cause:
    This behavior may occur when the TV broadcast has a larger-than-expected timing difference between the audio and video signal.

    resolution:
    To work around this problem, set the following registry entry to a larger value:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\Video\Tuners\DVR
    REG_DWORD: TimeholeThresholdMs

    This value configures the largest allowable time difference between the audio and video streams, in milliseconds.

    The default value is 2500. In some regions, certain broadcasts have been observed which contain a larger time difference. Changing this value to 3000 may resolve the problem.



    APPLIES TO:
    • Windows 7 Enterprise
    • Windows 7 Enterprise E
    • Windows 7 Enterprise N
    • Windows 7 Home Basic
    • Windows 7 Home Premium
    • Windows 7 Home Premium E
    • Windows 7 Home Premium N
    • Windows 7 Professional
    • Windows 7 Professional E
    • Windows 7 Professional for Embedded Systems
    • Windows 7 Professional N
    • Windows 7 Ultimate
    • Windows 7 Ultimate E
    • Windows 7 Ultimate for Embedded Systems
    • Windows 7 Ultimate N
    Remember backing up your registry before taking any action!:)

    See info here:
    Windows Media Center: Black screen for several minutes when changing channels in Live TV
    Last edited by NoN; 31 Aug 2011 at 13:59.
      My Computer


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

    This one is a "Fix-it" solution provided by MS....


    -Article ID: 2230957 - Last Review: October 8, 2010 - Revision: 3.0
    Error code 0x8007000D when trying to activate a Windows server 2008 or Windows 7 machine using any type of product key.

    symptoms:
    You try to activate a Windows Server 2008 or Windows 7 machine using any type of product key.
    Running slsmgr -dlv or slmgr -ato from a command line generates the following:
    The data is invalid.
    Error code 8007000d.

    cause:
    The System account by default has Full Control permissions to the registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root and any subkeys.
    If those permissions have been altered for the 'Root' key or any subkey(s), we would see the error code 0x8007000D

    resolution:
    Assign the minimum permission of "Enumerate Subkeys" to the System account for the registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root and any of its subkeys.

    Microsoft Fix it 50485 :
    Error code 0x8007000D when trying to activate a Windows server 2008 or Windows 7 machine using any type of product key.
    Last edited by NoN; 31 Aug 2011 at 14:00.
      My Computer


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

    For those working multiple monitors...

    -Article ID: 2353143 - Last Review: October 14, 2010 - Revision: 3.0
    The taskbar is three times wider than expected after you change the orientation and the position of multiple monitors in the Display settings of a computer that is running Windows 7 or Windows Server 2008 R2:

    Symptoms:
    Assume that you attach multiple monitors to a computer that is running Windows 7 or Windows Server 2008 R2. When you change the orientation and the position of the displays of these monitors in the Display settings item in Control Panel, the taskbar is three times wider than expected.


    For example, you attach two monitors to a computer that is running Windows 7. Then, you perform the following operations in the Display settings item in Control Panel:
    1. You set monitor 1 as the main display, and you display the taskbar at the bottom of the screen.
    2. You set the orientation of the two monitors to "Landscape."
    3. You drag the taskbar to the right side of monitor 1.
    4. You arrange the monitors so that monitor 1 is above monitor 2.
    5. You change the orientation of monitor 1 to "Portrait," and then you drag the taskbar to the right side of the monitor.
    6. You change the orientation of monitor 2 to "Portrait," and then you arrange the monitors so that monitor 2 is to the left side of monitor 1.
    7. You set monitor 2 as the main display.
    In this example, the taskbar is three times wider than expected.

    resolution & request the hotfix:
    The taskbar is three times wider than expected after you change the orientation and the position of multiple monitors in the Display settings of a computer that is running Windows 7 or Windows Server 2008 R2
    Last edited by NoN; 31 Aug 2011 at 14:01.
      My Computer


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

    Today's one is an august post, but it seems have been "fixed & revised" on october 18, 2010 to version 2.0.


    -Article ID: 976427 - Last Review: August 27, 2010 - Revision: 2.0
    Computers that are running Windows 7 or Windows Server 2008 R2 stop responding at a black screen if a screen saver is enabled:

    symptoms:
    Consider the following scenarios:

    Scenario one
    • On a computer that is running Windows 7 or Windows Server 2008 R2, you enable a screen saver.
    • You enable the On resume, display logon screen option for the screen saver.
    • In Power Options, you set the Turn off the display option and the Put the computer to sleep option to the same length of time. Additionally, the length of time that you set is longer than the time that you set for the screen saver to trigger.
    • The time for the Turn off the display value elapses and the display is turned off automatically.
    Scenario two
    • On a portable computer that is running Windows 7 or Windows Server 2008 R2, you enable a screen saver.
    • You enable the On resume, display logon screen option for the screen saver.
    • After the screen saver starts, you close the lid of the portable computer.
    In both scenarios, the computer is still running. However, you cannot turn on the display by using the keyboard or the mouse. You may be unable to turn on the display until you force the computer to restart.

    Note: When you set the Turn off the display option to less than 10 minutes, the Turn off the display option automatically changes to the value of the Put the computer to sleep option.

    cause:
    This problem occurs because of a race condition between the CSRSS thread and the WinLogon thread.

    resolution & request hotfix at:
    Computers that are running Windows 7 or Windows Server 2008 R2 stop responding at a black screen if a screen saver is enabled
    Last edited by NoN; 31 Aug 2011 at 14:01.
      My Computer


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

    One more!

    -Article ID: 2345131 - Last Review: October 13, 2010 - Revision: 1.0
    The logon screen appears two times when you resume a Windows 7-based or Windows Server 2008 R2-based computer from Sleep (S3) or from Hibernation (S4):

    Symptoms:
    Consider the following scenario:
    • You have a computer that is running Windows 7 or Windows Server 2008 R2.
    • You install hotfix KB976427.
    • You enable the Require a password on wakeup option.
    • You resume the computer from Sleep (S3) or from Hibernation (S4).
    In this scenario, the logon screen may appear two times. Therefore, you have to enter your credentials two times.

    Cause:
    This issue occurs when there are multiple pending lock signals to be processed when the user is logging in. In this situation, the WinLogon state machine logs the user off.

    Resolution & request hotfix at:
    The logon screen appears two times when you resume a Windows 7-based or Windows Server 2008 R2-based computer from Sleep (S3) or from Hibernation (S4)
    Last edited by NoN; 31 Aug 2011 at 14:02.
      My Computer


  7. Posts : 10
    windows 7 home premium 64 bit
       #27

    Anyone know why the toolbar is disabled in Silverlight 4, what settings need to be changed.
      My Computer


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

    -Article ID: 982674 - Last Review: October 14, 2010 - Revision: 3.0
    "Stop 0x000000D1" error after you enable an iSCSI Initiator data digest setting that uses CRC or that uses checksum in Windows Server 2008 R2 or in Windows 7:

    Symptoms:
    On a computer that is running Windows 7 or Windows Server 2008 R2, you receive the following Stop error message:

    0x000000D1 (parameter1, parameter2, parameter3, parameter4)
    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Notes
    • The parameters in this error message vary, depending on the configuration of the computer.
    • Not all "0x000000D1" Stop errors are caused by this issue.
    This issue occurs after you enable a data digest for a cyclic redundancy check (CRC) function or for a checksum function on an iSCSI Initiator that is used on the computer.

    Cause:
    This issue occurs because the iSCSI Initiator incorrectly processes sense data from a device after it receives a nonfatal check condition when iSCSI data digest verification is enabled. This issue usually occurs when tape devices or other non-fixed-disk SCSI devices are used.


    Review and request the Hotfix:
    "Stop 0x000000D1" error after you enable an iSCSI Initiator data digest setting that uses CRC or that uses checksum in Windows Server 2008 R2 or in Windows 7



    More info about the iSCSI Initiator:
    Microsoft iSCSI Initiator Step-by-Step Guide
    Last edited by NoN; 31 Aug 2011 at 14:03.
      My Computer


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

    -Article ID: 2388142 - Last Review: October 14, 2010 - Revision: 2.0
    A computer that is running Windows 7 or Windows Server 2008 R2 intermittently cannot use a shared network printer to print:

    symptoms:
    You configure a client computer that is running Windows 7 or Windows Server 2008 R2 to use a shared network printer to print. However, the print job intermittently fails. When this issue occurs, you do not receive an error message on the client computer. And, the print job is not printed on the physical printer.

    Note: To recover the print functionality on the client computer temporarily, you can restart the Print Spooler service.

    View info and request the hotfix at:
    A computer that is running Windows 7 or Windows Server 2008 R2 intermittently cannot use a shared network printer to print
    Last edited by NoN; 31 Aug 2011 at 14:03.
      My Computer


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

    Still Hasn't got that Windows 7 SP1 RC installed? So, this New MS hotfix might be for you...:)

    -Article ID: 2353143 - Last Review: October 14, 2010 - Revision: 3.0
    The taskbar is three times wider than expected after you change the orientation and the position of multiple monitors in the Display settings of a computer that is running Windows 7 or Windows Server 2008 R2:

    Symptoms:
    Assume that you attach multiple monitors to a computer that is running Windows 7 or Windows Server 2008 R2. When you change the orientation and the position of the displays of these monitors in the Display settings item in Control Panel, the taskbar is three times wider than expected.

    For example, you attach two monitors to a computer that is running Windows 7. Then, you perform the following operations in the Display settings item in Control Panel:
    1. You set monitor 1 as the main display, and you display the taskbar at the bottom of the screen.
    2. You set the orientation of the two monitors to "Landscape."
    3. You drag the taskbar to the right side of monitor 1.
    4. You arrange the monitors so that monitor 1 is above monitor 2.
    5. You change the orientation of monitor 1 to "Portrait," and then you drag the taskbar to the right side of the monitor.
    6. You change the orientation of monitor 2 to "Portrait," and then you arrange the monitors so that monitor 2 is to the left side of monitor 1.
    7. You set monitor 2 as the main display.
    In this example, the taskbar is three times wider than expected.

    Review and request the hotfix:
    The taskbar is three times wider than expected after you change the orientation and the position of multiple monitors in the Display settings of a computer that is running Windows 7 or Windows Server 2008 R2



    -Article ID: 980382 - Last Review: October 29, 2010 - Revision: 5.0
    The computer stops responding when you rename a folder in Windows Server 2008, in Windows Vista, in Windows 7 and in Windows Server 2008 R2:

    Symptoms:
    Consider the following scenario:
    • You have a computer that is running Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2.
    • There is a volume in an NTFS file system on this computer. There are lots of files that are in a folder on this volume. For example, assume that there are more than 5000 files in this folder.
    • Many files in the folder were opened at least one time previously.
    • You try to rename the folder name.
    In this scenario, the computer stops responding for some time. Therefore, the computer responds to a mouse button click or to a screen update very slowly.

    Note: If the Failover Clustering feature is installed on the computer, the cluster resources that are hosted on the computer fail over to the other nodes because of this issue.

    Cause:
    The rename operation for a directory checks whether a file in the folder is opened by a user. During this operation, a volume control block (VCB) lock is obtained, and any other I/O requests to the volume are blocked. If the number of files in the directory is large, this process of checking whether a file is opened may take an unnecessarily long time. Therefore, the computer stops responding for this long time. However, the computer eventually recovers.

    Resolution & request Hotfix here:
    The computer stops responding when you rename a folder in Windows Server 2008, in Windows Vista, in Windows 7 and in Windows Server 2008 R2
    Last edited by NoN; 31 Aug 2011 at 14:05. Reason: adding infos
      My Computer


 
Page 3 of 33 FirstFirst 1234513 ... 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 04:08.
Find Us