Consider the following scenario:

• You try to make copies of the registry or of the registry keys on a computer that is running Windows Server 2008 or Windows Vista.
• You use the reg save command to export the registry key into a hive file.

In this scenario, the reg save command does not compress the registry key during the exporting process. Therefore, the size of the hive file may be larger than expected.

Consider the following scenario:

• You have an application on a computer that is running Windows Server 2008 or Windows Vista.
• The application calls the RegLoadKey function to load a registry hive file.
• This application calls the RegUnLoadKey function to unload the registry hive file without making any changes.

In this scenario, the Accessed time file attribute and the Modified time file attribute of the file are updated. However, the expected behavior is that only the Accessed time file attribute is updated.

This scenario may cause an issue in the following environment:

• You configure the Delete user profiles older than a specified number of days on system restart Group Policy to remove the user profiles that are not accessed for some time.
  Note: To find the Delete user profiles older than a specified number of days on system restart Group Policy, do the following. Under Computer Configuration, expand Administrative Templates, expand System, and then click User Profiles.
• You set up some antivirus applications or some anti-malware applications to run on the servers. These applications regularly scan user profiles for security.

In this environment, every time that the antivirus applications or the anti-malware applications scan the user profile registry hive files, the files are updated. Therefore, the configured Delete user profiles older than a specified number of days on system restart Group Policy becomes ineffective.

By default, Windows SteadyState contains an option that restricts shared computer users (SCUs) from accessing the registry directly. This setting might prevent the user from saving changes to some settings in the Internet Options dialog box, such as the following:

• General tab: Home page
• Security tab: Security level for this zone, and Enable Protected Mode
• Privacy tab: Sites, Advanced, and Default
• Content tab: AutoComplete
• Programs tab: Default web browser
• Advanced tab: Advanced Internet Explorer settings

Consider the following scenario. On a computer that is running Windows Vista or Windows Server 2008, you set the registry entry SrvsvcDefaultShareInfo under the following registry subkey to configure the default share permissions for a network share:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\lanmanserver\DefaultSecurity\

In this scenario, after you restart the computer, you cannot access an administrative share on the computer.

For example, when a user tries to access drive C by using the “\\[computer name]\C$” command, the user receives the following error message:

Windows cannot access \\[computer name]\C$
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problem, click Diagnose.
Details:
Error code: 0×80070005
Access is denied

On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you receive the following Stop error message:

STOP 0×0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)

Notes

• The first parameter is 0xc0000005. Other three parameters in this Stop error message may vary, depending on the configuration of the computer.
• Not all “0×0000007E” Stop error messages are caused by this problem.

Additionally, the following event is logged in the System log:

Source: Microsoft-Windows-WER-SystemErrorReporting
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, <address>, <address>, <address>). A dump was saved in: <file path>.

The registry key guidance that is offered in Technet article 91525 (www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/91525.mspx?mfr=true) did not correctly disable AutoRun features. After you set the registry keys to disable these features as described in this Technet article, the AutoRun capabilities, the Double Click feature, and the Contextual Menu feature continue to function as if they were not set. This article describes how to obtain updates that correct these registry key settings.

This article is applicable for all supported editions of the following products:

• Microsoft Windows 2000
• Windows XP Service Pack 2
• Windows Server 2003 Service Pack 1
• Windows Server 2003 Service Pack 2
• Windows Vista

Windows Server 2008 is not affected.

On a computer that is running a 32-bit version of Windows Server 2003, the Reg.exe utility cannot access 64-bit registry keys on a computer that is running a 64-bit version of Windows Server 2003.

Notes

• This problem occurs when the 32-bit computer has Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed.
• This problem does not occur on a computer that is running Windows 2000.
• This problem also occurs on a computer that is running Windows XP or Windows Vista.

When a computer that is running Windows Vista or Windows Server 2008 is under high stress, the TCP/IP Registry Compatibility (Tcpipreg) service may stop responding. Or, a malfunction may occur in the service. Additionally, some applications that are related to the network do not function as expected.

For example, when you resume a Windows Vista-based computer from hibernation (S4) or from suspend (S3), a malfunction occurs in the Tcpipreg service. In this case, when you try to use the net stop tcpipreg command to stop the Tcpipreg service, the command may stop responding.

The Microsoft Storport driver (Storport.sys) is installed on a computer that is running Windows Server 2008 or Windows Vista. Then, you notice that the value of the DeviceType registry entry for storage devices is truncated to half of its length.

Note The DeviceType registry entry is located under the following registry subkey:

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port [x]\Scsi Bus [x]\Target Id [x]\Logical Unit Id [x]

In this subkey, [x] is a placeholder for a one-digit number.

For example, the value of the DeviceType registry entry may be truncated to “MediumChang” when the registry entry that is expected is “MediumChangerPeripheral.”

Therefore, applications may function incorrectly when they retrieve the device type information from the DeviceType registry entry.

You upgrade Windows XP Service Pack 2 (SP2) to Windows Vista or to Windows Vista Service Pack 1 (SP1). However, the following Windows Time Synchronization service (W32Time)-related registry settings are not updated to the default Windows Vista values.

Default registry settings in Windows XP

Default registry settings in Windows Vista