Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Milestone Releases
February Windows Vista CTP
BitLocker/Secure startup
There is a potential BitLocker and Code Integrity interoperability issue with the February Windows Vista CTP build. Before starting the BitLocker feature on computers that have 1.2 TPM enabled, you must modify the Boot Configuration Data (BCD) to enable Code Integrity. However, by default, the CTP build of Windows Vista has Code Integrity disabled. This setting allows ISVs to more easily test unsigned software together with Windows Vista. This configuration is viewed by BitLocker as a potential security issue and requires that users navigate recovery mode every time that the computer is disabled.
To activate BitLocker on a computer that has a TPM-compatible device and that is running the February Windows Vista CTP build, follow these steps:
- In Windows Vista, click Start, click Programs, right-click Command Prompt, and then select " run as administrator" or "run elevated."
- Type the following command and then press ENTER:
bcdedit -set {current} NOINTEGRITYCHECKS false
- Restart the computer.
- Continue activation of the BitLocker feature.
Note- These steps are not required when you run BitLocker on a computer without a TPM device.
Microsoft Windows Vista Beta 1
Windows Vista Beta 1 may enter standby if a user is not logged into the console session. This issue occurs even if the system standby idle time-out is set to
Never in the Power Options tool in Control Panel.
To work around this issue, type the following command at the command line:
reg.exe add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\AbsentiaPowerScheme\381b4222-f694-41f0-9685-ff5bb260df2e\29f6c1db-86da-48c5-9fdb-f2b67b1f44da /v ACSettingIndex /t REG_DWORD /d 0 /f