You'll find here some Hotfixes Packages directly downloadable from the Microsoft Download Center for this October 25, 2011 day Patches. Those were not automated on Windows Update
-Article ID: 2619572 - Last Review: October 12, 2011 - Revision: 1.0
"HTTP Error 401.1" error message when Msiexec.exe updates an MSI file in Windows Vista, in Windows 7, in Windows Server 2008, or in Windows Server 2008 R2.
Symptoms:
Assume that you deploy an application to a client computer that is running one of the following operating systems by using System Center Configuration Manager 2012:
- Windows Vista
- Windows 7
- Windows Server 2008
- Windows Server 2008 R2
When the deployment of the application is finished, the Microsoft Installer Package (MSI) file is removed from the local drive. Then, the ConfigMgr client updates the MSI source list by accessing the content server. This behavior is controlled by the self-healing functionality. When the self-healing functionality is triggered, Msiexec.exe tries to access the content path anonymously instead of by using the credentials of the user who currently logs on the client computer. However, the Secure Windows Initiative (SWI) guidelines do not allow anonymous access to content servers. Therefore, you receive the following error message:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Note The issue occurs only when the content server is indicated by using a URL.
Resolution:
This hotfix adds an automatic logon level that determines when it is acceptable for WinHTTP to include the default credentials in a request. The hotfix adds the following logon level:
- WINHTTP_AUTOLOGON_SECURITY_LEVEL_LOW
- WINHTTP_AUTOLOGON_SECURITY_LEVEL_MEDIUM
- WINHTTP_AUTOLOGON_SECURITY_LEVEL_HIGH
By default, the level is set to WINHTTP_AUTOLOGON_SECURITY_LEVEL_MEDIUM. This is the recommended logon level. For more information about optional security levels, visit the following Microsoft website:
General information about the automatic logon policy (
http://msdn.microsoft.com/library/aa383144(v=VS.85).aspx#auto_logon)
To set the automatic logon security level, set the following registry entry under the
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer registry subkey:
Name
WinHttpAutoLogonLevel
Type
String
Value
Available values are listed in the following table:
Collapse this tableExpand this table
ValueMeaning:
L:WINHTTP_AUTOLOGON_SECURITY_LEVEL_LOW
M: WINHTTP_AUTOLOGON_SECURITY_LEVEL_MEDIUM
H: WINHTTP_AUTOLOGON_SECURITY_LEVEL_HIGH
After you install this hotfix and configure the logon level, Msiexec.exe uses the
WinHttpSetCredentials function to pass the required authorization credentials to the content server if the first anonymous access request fails.
Download the Package at MS Center:
for x64:
http://www.microsoft.com/download/en/details.aspx?id=27792
for x32:
http://www.microsoft.com/download/en/details.aspx?id=27779
-Article ID: 2618301 - Last Review: October 25, 2011 - Revision: 1.0
"Error 633" error message and you cannot establish a dial-up connection after you resume Windows 7 or Windows Server 2008 R2 from sleep or from hibernation.
Symptoms:
When you resume a computer that is running Windows 7 or Windows Server 2008 R2 from sleep or from hibernation, you cannot establish a dial-up connection through a modem. Additionally, you may receive the following error message:
Error 633: The modem (or other connecting device) is already in use or is not configured properly
Note When this issue occurs, you must restart the computer or reset the modem device to establish the dial-up connection.
Cause:
This issue occurs because a flag is not reset after the device state is cleaned up when the computer is put to sleep or into hibernation. Therefore, the flag is in an inconsistent state when you resume the computer.
Note The flag is set when the computer is put to sleep or into hibernation. The flag indicates that the states of various internal structures for the modem device have to be cleaned up.
Direct Package Download at:
"Error 633" error message and you cannot establish a dial-up connection after you resume Windows 7 or Windows Server 2008 R2 from sleep or from hibernation
-Article ID: 2578214 - Last Review: October 25, 2011 - Revision: 2.0
An application crashes when it tries to retrieve file information from an invalid or corrupted file in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2.
Symptoms:
Assume that you use an application to view the properties of a file that is invalid or corrupted on a computer that is running Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2. In this situation, the application may crash.
Note This issue occurs when the application uses the
GetFileVersionInfoSizeExW function to retrieve file information.
Cause:
This issue occurs because the
GetFileVersionInfoSizeExW function has assumptions about the layout of version resources. If a file has invalid resources that violate these assumptions, then an access violation may occur.
Direct Package Download at:
An application crashes when it tries to retrieve file information from an invalid or corrupted file in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2
