The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    tvt_bitlocker_status error when installing backup?

    Discussion in 'Lenovo' started by wkearney99, Jun 30, 2011.

  1. wkearney99

    wkearney99 Notebook Consultant

    Reputations:
    66
    Messages:
    212
    Likes Received:
    0
    Trophy Points:
    30
    I'm trying to use Lenovo's rescue and recovery backup program, but when I try to install it I'm getting the error
    Anyone seen this? Or have a solution?

    This is on a T420 running Win7 Professional x64. And from what I've read bitlocker is a feature only present in Enterprise or Ultimate versions of Win7. I don't recall attempting to install or otherwise configure anything related to drive encryption. This is running on an SSD restored using the Lenovo disks made by this machine. All other programs seem to be working fine. And I tried using the rnr software from lenovo's site, same error.
     
    wkearney99, Jun 30, 2011
    #1
  2. wkearney99

    wkearney99 Notebook Consultant

    Reputations:
    66
    Messages:
    212
    Likes Received:
    0
    Trophy Points:
    30
    Think I figured out the problem. The installer is picky about whether the TEMP environmental variable for the SYSTEM account can find it's directory. In my desire to avoid using the SSD for unnecessary writes I configured the TEMP variable to be %USERNAME%.%USERDOMAIN%. This works OK if the machine is joined to a domain. But when it's standalone (workgroup) this results in Windows creating a folder named "SYSTEM.%USERDOMAIN%" instead of actually resolving %USERDOMAIN% to it's proper value. Which for an actual user on the machine resolves to the machine's name. Chalk this up to a really obscure bug somewhere...
     
    wkearney99, Jun 30, 2011
    #2