locked
After Update 1607 no TPM function RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    4
    Sign in to vote

    Hi all,

    I'm just install the Update 1607 Windows Update in the RC on a Dell Latitude 7440.

    The update went through without any problems. When I have restarted the PC, the information was immediately that would start the automatic repair.
    Recovery - the PC could not properly start 0xc0000001
    Recovery - PC / device needs to be repaired. It can be not loaded properly the BitLocker key. 0xc210000

    After this I disabled the TPM chip in the BIOS. I could start Windows using the recovery key.
    I reseted the TPM chip - no improvement
    then disables BitLocker and reactivated, there is now also the message that the TPM could not be used.
    At the TPM MSC the chip is available.

    Have anyone an idea?
    Stefan
    Tuesday, August 2, 2016 1:53 PM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote

    Hello,

    Another Update on this thread:

    how to avoid getting into this bitlocker recovery situation

    When does a user hit the bitlocker recovery issue?

    1. User has upgraded from Th1 to Th2 and then now upgrading to RS1
    2. User either has Hyper-V ON or want to turn it on in RS1 after OS upgrade
    3. First reboot after Hyper-V is enabled in RS1 will hit bit locker recovery – this can be soon after OS upgrade if Hyper-V was already enabled downlevel
    4. Due to separate Bitlocker issue even after entering the Bitlocker key we fail to recover.  Still under investigation.

    Workaround – here are the 4 workaround that customers can choose from to avoid getting into this situation:

    1. Keep Hyper-V disabled during OS upgrade and keep it disabled till servicing update on 8/23 comes through
    2. Reset the Device guard RegKeys (delete the DG regkey node) and then enabled Hyper-V in RS1
    3. Reset the Device guard RegKeys (delete the DG regkey node) and then upgrade to RS1 while keeping Hyper-V however customers want (ON or OFF is both fine)
    4. Disable Bitlocker till 8/23

    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Monday, August 15, 2016 11:20 PM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi Stefan,

    I recommend you update your chipset and BIOS from manufacturer's website and see if your issue can be fixed:

    The official site is:

    http://www.dell.com/support/home/us/en/19/product-support/product/latitude-e7440-ultrabook/drivers/advanced

    Here are the chipset update and BIOS update:

    http://downloads.dell.com/FOLDER02265227M/1/Chipset_Driver_3664N_WN_9.4.0.1027_A03.EXE

    http://downloads.dell.com/FOLDER03692525M/1/E7440A18.exe

    Please Note:  This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 3, 2016 2:48 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi , I have the same problem with Lenovo X1 Carbon 20A7. The problem occurred after activating Ubuntu on Windows feature. I saw the same errors as you and disabled Bitlocker. And there were no errors on boot anymore. Next, I updated my BIOS to last version (1.25 - 08.04.2016). Finally I tried to enable Bitlocker again, but the message that could not be activated was displayed.

    I have read that Win10 anniversary update require TPM 2.0, so I enabled it in BIOS too. But without any success.

    Tmp.msc does not display any problems. Event Viewer (log) shows errors related to TPM:

    The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer.

    The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically.  To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.
    Error: The operation completed successfully.
    Additional Information: 0xc0000


    So can anybody help? Thanks!

    Wednesday, August 3, 2016 9:51 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    Will do more research on such issue and update you later.

    Generally, it's compatible issue, would you please help to feedback this issue on Windows Feedback app?　

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 5, 2016 2:58 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Another thread on the subject is https://social.technet.microsoft.com/Forums/en-US/d6530d19-6ca6-4697-bf81-6d7c08492bdb/windows-10-14393-1607-enterprise-issues-with-tpm

    Just a thought: could everybody post their TPM chip info? Run tpm.msc and look under TPM Manufacturer Information.

    Mine is ATLM (= Atmel), Manufacturer v41.1, Spec v1.2

    Friday, August 5, 2016 10:03 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I have the same problem on my HP laptop: I needed to run system repair and disable bitlocker. After that, Windows Hello and Bitlocker wouldn't activate anymore.
    Saturday, August 6, 2016 8:21 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    So, there is my TPM info on Lenovo X1 Carbon 20A7 (Intel i7):

    • Manufacturer Name: INTC
    • Manufacturer Version: 9.5
    • Specification Version: 2.0

    NOTE: I have tried both TPM 1.2 and 2.0 options in BIOS

    Sunday, August 7, 2016 1:09 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    So, there is my TPM info on Lenovo X1 Carbon 20A7 (Intel i7):

    • Manufacturer Name: INTC
    • Manufacturer Version: 9.5
    • Specification Version: 2.0

    NOTE: I have tried both TPM 1.2 and 2.0 options in BIOS

    I will also do the feedback on my side. Hope it can be resolved in next updates.

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 8, 2016 7:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    HI Alex,

    thanks for linking.

    Dell E7440: ATML, Manufacturer v41.1, Spec v1.2

    Lenovo Thinkpad T430S: ATML, Manufacturer v41.1, Spec v1.2

    Surface Pro 1: IFX, Manufacturer v3.19, Spec v1.2

    this is really annoying and should be fixed before of the global rollout....

    Cheers,

    Matthias

    Monday, August 8, 2016 9:07 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    Can we collect the following information from the machines that are failing?

    1. MSINFO32 output from the machine.  From the commandline run msinfo32 and save the output as a text file.
    2. Registry key information under HKLM\System\CurrentControlSet\Control\DeviceGuard .  Export the regkey  and save as a text file.
    3. Output of  the command: “powershell $(Get-CimInstance -classname Win32_DeviceGuard -namespace root\Microsoft\Windows\DeviceGuard)”

    From a CMD prompt run this : powershell $(Get-CimInstance -classname Win32_DeviceGuard -namespace root\Microsoft\Windows\DeviceGuard) >dguard.txt

    Compress the files into a ZIP file and send to darrellg-removethis-@microsoft.com

    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, August 8, 2016 9:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    thank you ;-)

    Dell 7440 ATML 41.1. TPM Version 1.2

    Tuesday, August 9, 2016 2:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I tried to send you the data you requested, but it failed with

    The error that the other server returned was:
    550 5.4.1 [darrellg-removethis-@microsoft.com]: Recipient address rejected: Access denied

    Does the address still exist?


    Wednesday, August 10, 2016 11:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You must remove the removethis string ;-)
    Wednesday, August 10, 2016 11:03 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello

    Thanks for the log files, we have identified the issues and are working on a solution.

    We do not need any more logs, will update when I have more information.

    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, August 11, 2016 10:50 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    Hello,

    Another Update on this thread:

    how to avoid getting into this bitlocker recovery situation

    When does a user hit the bitlocker recovery issue?

    1. User has upgraded from Th1 to Th2 and then now upgrading to RS1
    2. User either has Hyper-V ON or want to turn it on in RS1 after OS upgrade
    3. First reboot after Hyper-V is enabled in RS1 will hit bit locker recovery – this can be soon after OS upgrade if Hyper-V was already enabled downlevel
    4. Due to separate Bitlocker issue even after entering the Bitlocker key we fail to recover.  Still under investigation.

    Workaround – here are the 4 workaround that customers can choose from to avoid getting into this situation:

    1. Keep Hyper-V disabled during OS upgrade and keep it disabled till servicing update on 8/23 comes through
    2. Reset the Device guard RegKeys (delete the DG regkey node) and then enabled Hyper-V in RS1
    3. Reset the Device guard RegKeys (delete the DG regkey node) and then upgrade to RS1 while keeping Hyper-V however customers want (ON or OFF is both fine)
    4. Disable Bitlocker till 8/23

    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Monday, August 15, 2016 11:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a lot for investigation! So i'm looking forward to the next update with the fix :)
    Tuesday, August 16, 2016 7:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Darrell,

    Is this servicing update still going to be released today?

    Chris

    Tuesday, August 23, 2016 4:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just want to add that I have a Surface Pro 3 with the same issue (TPM not found after latest Win10 build). Anyway...I, too, am waiting for this 8/23 servicing release.


    Tuesday, August 23, 2016 4:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same kind of problem. I have Dell XPS 9550 with TPM 1.2 After upgrade to latest preview build, 14905, TPM disappears from BIOS and BitLocker keeps asking for recovery key.

    I have this thing happened to my laptop two times. First time I thought it must be a hardware issue and I got my laptop replaced. But it happen again on my new laptop after replacement. after installing latest insider build 14905, TPM disappears from machine.


    Tuesday, August 23, 2016 10:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Try to apply update https://support.microsoft.com/en-us/kb/3176936 for 1607.
    Wednesday, August 24, 2016 5:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    is the update already released? Which KB is it?

    Thanks,

    Alex

    Wednesday, August 24, 2016 10:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Nothing changed with the latest batch of KB updates. TPM is still non-functioning in Windows 10 (enabled in UEFI)
    Wednesday, August 24, 2016 8:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same here. With Lenovo W540 - after applying the Windows 1607 update and "Update for Windows 10 Version 1607 for x64-based Systems (KB3176936)" - when you do your first reboot it does not allow to unlock the drive and all you can do is either user Command Prompt or restore to previous build. When selecting these two options unlocking the drive actually works but there is no way to proceed to Windows.

    I also tried Command Prompt and "Manage-BDE -protectors -disable c:" but then when you type "exit" it reboots again and you are back at square one.

    So the fix did not fix - at least not this scenario.

    Avishay

    Thursday, August 25, 2016 11:51 AM