Announcing Windows 10 Insider Preview Build 17093 for PC Fast+Skip Insider

dencal said:

Curiosity on my part.....posted 0xc 1900101 in M$ Support forum.....the answer was supplied by a Microsoft technician...the problem being way above my station computer wise.....see link....do note I did state "You could try" not that it was an infallible method to solve the problem.

As for CitRix It certainly shows up in my Insider W10 Registry....though whether it can be applied to solve this particular problem, I leave to those more knowledgeable.

https://support.microsoft.com/en-us/...-second-system

Constantly getting 0xC1900101-0x40017. Drivers all up to date, checked 3 times manually and with driver program. Ran clean boot and everything else known and posted here and on the web with ISO and download tries. Went back to slow builds but may try the CitRix fix offered by M$.

Winuser said:

I not sure what those two setting do so I agree that it's best to wait.

I would not touch them as I did and I had to re install the operating sys and reset the cmos it made a mess of my system. It put me in an endless boot loop. after I reloaded I just demised it lost my skip ahead setting obn this computer.

Hi,

kevin2017 said:

I would not touch them as I did and I had to re install the operating sys and reset the cmos it made a mess of my system. It put me in an endless boot loop. after I reloaded I just demised it lost my skip ahead setting obn this computer.

It looks as if these settings are going to replace tpm.msc.
@AndreTen : It looks your machine is running a Infineon (IFX) TPM. Has it been patched yet ?

Cheers,

Hi,

AndreTen said:

Don't think so. It's an HP box. Any special instructions?

I'm running a similar TPM to yours and it was vulnerable. My OEM delivered a patch for it somewhere in November last year.
You can check in device manager if the TPM is vulnerable or not. The security device shows a yellow bang if it is as would EventViewer in its logs.

Either way, it's up the HP and other OEMs for that matter, to make the patch available for all the vulnerable machines.

Cheers,

Hi,

Maybe I should just update (or reset) it, as I never did it before... and that's the problem with them.

Are you experiencing problems with the TPM then ?
For more info follow the HP link here:

https://www.infineon.com/cms/en/prod...es/tpm-update/

If you run this machine on a private basis then there's a good chance the module is empty except perhaps if you secured your UEFI/BIOS using passwords. Other then that it may well be empty.
Running TPM.msc should tell you more about the firmware you're module is on. Not all 1.2 modules are vulnerable.

This tool will tell you the TPM exact firmware version:

http://support.ts.fujitsu.com/content/InfineonTPM.asp

Cheers,