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

When a 32-bit application is writing the %ProgramFiles% registry value on a computer that is running a 64-bit version of Windows Vista, Windows Vista automatically changes this string to %ProgramFiles(x86)%. This behavior cannot be changed.

This behavior also occurs in the 64-bit versions of Windows Server 2003 and of Windows XP.

A database of many of the configuration settings in Windows.

• Microsoft relents: Vista SP1 available to technical users now
  Mary Jo comments on Microsoft’s SP1 release change.
  (tags: SP1 )
• How to let a user apply a Group Policy that has the “Devices: Unsigned driver installation behavior” Group Policy setting from a Windows Vista-based computer to a client computer
  A registry hack to enable a policy not visible in Vista’s Local Group Policy Editor.
  (tags: GPO Registry )

A registry hack to enable a policy not visible in Vista’s Local Group Policy Editor. Keep reading →

Sorry for the backup! My posting software was giving me problems, I think I’ve got it worked out now.

• Vista’s driver ills aren’t just Microsoft’s fault
  There’s plenty of blame to go around.
  (tags: Drivers SP1 )
• Users blast Microsoft over Vista SP1 schedule
  Lots of users, like me, questioning why SP1 can’t be released to technical users, even if it is held back from Windows Update.
  (tags: SP1 )

Keep reading →