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.

    Infineon TPM 3.0.1 YES, 3.5 NO?

    Discussion in 'Windows OS and Software' started by jxtx, May 18, 2009.

  1. jxtx

    jxtx Notebook Consultant

    Reputations:
    10
    Messages:
    189
    Likes Received:
    0
    Trophy Points:
    30
    I have been trying to reconfigure my ASUS F3Sa to run Windows 7 with all of the features I was able to use running Vista. While all of my hardware is recognized and installed, I cannot use it as I would like. I have had a very difficult time trying to install Infineon TPM software. The latest version, 3.5, which is advertised as Vista compatible, advances through the installation process and then fails. When it fails, the install program reports Error 1722. Strangely, an out-of-date version, 3.0.1, installs with no problems.

    Any suggestions? I would like to run the more up-to-date version.

    A broader question: do I need Infineon's TPM software to use the TPM in Windows 7? I see BitLocker is included with this RC. Does BitLocker accomplish the same thing?

    Jeremy
     
  2. timtravel42

    timtravel42 Notebook Virtuoso

    Reputations:
    827
    Messages:
    2,004
    Likes Received:
    1
    Trophy Points:
    56
    did you try installing it in vista compatible mode

    i think infineon TPM has more features because BitLocker only does drive encryption
     
  3. Nara

    Nara Notebook Guru

    Reputations:
    0
    Messages:
    63
    Likes Received:
    0
    Trophy Points:
    15
    I believe you need to install both versions. I don't think you can install just v3.5 without v3.0.1. I tried that on Vista and Windows 7 and had the same error. After installing v3.5 on top of v3.0.1, everything's fine.