New
#161
One that had been missed being put in this sevenforums section from August 16, 2011 and recently being mentioned in this tutorial:
Theme - Specify Default Theme to Load for New Users
-Article ID: 2462182 - Last Review: August 16, 2011 - Revision: 1.1
The "Load a specific theme" Group Policy setting is not applied correctly for a new user in Windows 7 or in Windows Server 2008 R2.
Symptoms:
Consider the following scenario:
In this scenario, the Load a specific theme Group Policysetting is not applied correctly on the computer. The theme and the first desktop background are applied. However, the desktop background does not change.
- You enable the Load a specific theme Group Policy setting and point to the path of a valid theme file.
- The theme has a configuration that changes the wallpaper in an interval.
- You enable the Prevent changing desktop background Group Policy setting.
- You apply the Group Policy settings to a computer that is running Windows 7 or Windows Server 2008 R2.
- You log on the computer by using a new user account.
Note You can find all the Group Policy settings that are mentioned in this section in the following location:
User Configuration/Administrative Templates/Control Panel/Personalization.
Review & request Hotfix:
The "Load a specific theme" Group Policy setting is not applied correctly for a new user in Windows 7 or in Windows Server 2008 R2
------------------------------------------------------------------------------------------------------------
Others available Fixes not related to above one...
-Article ID: 2577550 - Last Review: August 10, 2011 - Revision: 1.0
You may wait for up to 30 seconds when you use a smart card to unlock a computer that is running Windows 7 or Windows Server 2008 R2.
Symptoms:
When you unlock a computer that is running Windows 7 or Windows Server 2008 R2 by using a smart card, you may have to wait for up to 30 seconds before the desktop is displayed. However, the unlocking process is supposed to complete within several seconds.
Note After this issue occurs one time, every successive unlocking operation that uses the smart card will be affected until you restart the computer.
Cause:
This issue occurs because the smart card module incorrectly manages its cache. This causes a long delay if the smart card is accessed multiple times. The expected behavior is that the smart card module uses cached information when it performs Kerberos authentication.
Review & request hotfix:
http://support.microsoft.com/kb/2577...rss&spid=14019
------------------------------------------------------------------------------------------------------------
-Article ID: 2524249 - Last Review: August 10, 2011 - Revision: 2.0
Video capture and playback stop, or most video frames are dropped, when you connect an IEEE 1394 digital video camera to a computer that is running Windows 7 or Windows Server 2008 R2 .
Is superseded by:
-Article ID: 2707135 - Last Review: June 14, 2012 - Revision: 3.0
An IEEE 1394 isochronous device does not function in Windows 7 SP1 or in Windows Server 2008 R2 SP1.
Symptoms:
Consider the following scenario:
In this scenario, the IEEE 1394 device may not function, or the device may be unable to communicate with a custom application.
- You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
- You have an IEEE 1394 isochronous device.
- A bus reset occurs, and then you free the isochronous bandwidth that was previously allocated.
- You reallocate a bandwidth. Although the allocation succeeds, the amount of available bandwidth shows that the bandwidth was not allocated.
Note
Cause:
- An IEEE 1394 bus reset occurs when any change is made to the IEEE 1394 topology.
- This issue occurs only when you enable the Windows 7 Monolithic IEEE 1394 bus driver.
- This issue does not occur if you enable the legacy version of the IEEE 1394 bus driver.
This issue occurs because of a miscalculation of available bandwidth when the isochronous bandwidth is freed.
Review & request hotfix:
http://support.microsoft.com/kb/2707135/en-us
-----------------------------------------------------------------------------------------------------------
-Article ID: 2480641 - Last Review: August 31, 2011 - Revision: 3.0
XPS Viewer does not handle permissions for a group named "Anyone" correctly in Windows 7 or in Windows Server 2008 R2.
Symptoms:
Consider the following scenario:
In this scenario, the permissions for the "Anyone" group are not added to the permissions list of the XPS document.
- You open an XML Paper Specification (XPS) document by using XPS Viewer on a computer that is running Windows 7 or Windows Server 2008 R2.
- You set the permissions for the XPS document by using an Active Directory Rights Management Services (AD RMS) template that specifies a group that is named "Anyone."
Note: "Anyone" is spelled by using any capitalization other than "Anyone." For example, "Anyone" is spelled as "ANYONE" or "AnyOne."
Cause:
This issue occurs because of an error in XPS Viewer. XPS Viewer runs a case-sensitive comparison. Therefore, when you do not spell "Anyone" with the exact capitalization that is described in the "Symptoms" section, this issue occurs.
Review & request hotfix:
http://support.microsoft.com/kb/2480641/en-us
----------------------------------------------------------------------------------------------------------
Last edited by NoN; 14 Jan 2014 at 18:26. Reason: added Article ID: 2524249; 2480641
Quote
Windows Management Framework 4.0 
Microsoft Rights Management service (RMS) whitepapers