On a computer that is running Windows 7 or Windows Server 2008 R2, an error that resembles the following is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: Date and time
Event ID: 4107
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Computer name
Description:
Failed extract of third-party root list from auto update cab at: www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Or, on a computer that is running Windows Vista or Windows Server 2008, an error that resembles the following is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: Date and time
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Computer name
Description:
Failed extract of third-party root list from auto update cab at: www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

If you reboot a Windows Vista DHCP Client during a timeframe when the DHCP Server is unavailable, the client will configure its IP address to 0.0.0.0, even thougth you have set the registry value DontPingGateway to 1 as decribed in KB958336.

In Windows Firewall with Advanced Security, you configure an outbound firewall rule which requires the corresponding traffic to be authenticated and optionally encrypted. This is done by either enabling “Allow only secure connections” in the user interface or by using “NETSH ADVFIREWALL” at a Command Prompt with the arguments “security=authenticate” or “security=authenc”.

A corresponding Connection Security (IPsec) rule is configured.

Attempting communication with a host that meets the criteria for the rule you created will fail.

Accessing a folder under a mapped network drive to a Distributed File System Namespace (DFSN) folder target may fail on Windows Vista and later with error “Access is Denied”. Vista clients do not receive errors accessing the mapped folder, only its subfolders. Pre-Vista clients are able to successfully access the same subfolders without issue.

Accessing the subfolder from Windows Explorer will result in the following error message:

“You do not have permission to access \\dfsnroot\dfslinktarget\share. Contact your network administrator to request access.”

Accessing the subfolder from the command prompt results in error “Access is denied.”

Consider the following scenario:

• You attach a USB 2.0 audio device to a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.
• The USB 2.0 audio device has a MIDI out port.

In this scenario, the USB audio device may not work correctly. Additionally, the MIDI ports may not appear or not work as expected if you use software that supports the MIDI protocol.

Consider the following scenario:

• You install Microsoft Windows Installer (MSI) 4.5 on a computer that is running Windows Server 2008 or Windows Vista.
• You try to install a Windows Installer package on this computer.

In this scenario, the installation fails, and you receive the following error message:

Disk full: Out of disk space -- Volume: <volume>; required space: <number> KB; available space: 0 KB. Free some disk space and retry.

Consider the following scenario:

• You are using a computer that is running Windows Server 2008 or Windows Vista.
• You try to access some shared files or shared printers that are hosted on a remote server.
• The computer is running under a heavy load.

In this scenario, you cannot access the shared files or shared printers. Specifically, the process becomes unresponsive.

Note: From the captured network trace, you find that the Server Message Block version 2 (SMBv2) protocol is being used when this issue occurs.

Consider the following scenario:

• You set up an offline file synchronization partnership between a network share and some computers that are running Windows Vista or Windows Server 2008.
• You set an automatic resolution policy to resolve conflict in the synchronization process.
• You configure the policy to “keep all changes” when a conflict occurs.
  Note: To do this, follow these steps:
  1. Click Start, type regedit in the Start Search box, and then press ENTER.
  2. Locate and then click the following registry subkey:
     

     HKEY_LOAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\NetCache

  3. On the Edit menu, point to New, and then click Key. Type SyncConflictHandling, and then press ENTER.
  4. Right-click SyncConflictHandling, point to New, and then click Expandable String Value. Type the path of the network share as the value name.
  5. Right-click the value name, and then click Modify. In the Value data box, type 3, and then click OK.
• You update a file at multiple locations when the file is offline.
• You conduct a synchronization operation for the network share. It triggers a conflict in the synchronization process when it synchronizes the file.

In this scenario, the automatic resolution policy does not keep all changes for the conflicted file. Additionally, you receive an error message that resembles the following:

Cannot create a file when that file already exists.

Consider the following scenario:

• You access some shared files from a computer that is running Windows Vista or Windows Server 2008.
• The computer is working under a heavy stress situation.
• The connection to these shared files is lost. For example, you log off the computer.

In this scenario, the computer may restart unexpectedly. Additionally, you receive a Stop error message that resembles the following:

STOP: 0x0000007F (0×0000008, parameter2 , parameter3 , parameter4 )
UNEXPECTED_KERNEL_MODE_TRAP

Notes

• The parameters of this Stop error message vary, depending on the configuration of the computer.
• Not all “0x0000007F” Stop errors are caused by this issue.

Consider the following scenario. You have a computer that is running Windows Vista or Windows Server 2008. From this computer, you try to access shared files or shared printers that are hosted on a remote computer. However, the access operation becomes unresponsive.

Notes

• When this issue occurs, you cannot access shared files or shared printers that are hosted on any remote computers.
• The collected network trace indicates that the Server Message Block (SMB) Version 2 protocol is used to access shared files or shared printers.