Autopilot.dll WIL error

Nope. Resetting the TPM did nothing for me. Still getting oodles of these autopilot errors.

I didn't really expect resetting the TPM to work since entire, clean Windows installs didn't help either. But, it was worth a try.

For most of us, I assume it's a problem with 22H2 (Windows 10 and 11) and not with any configuration on our side.

Looks like the fix is to reset the TPM!! Woo-hoo!! I wasn't using bitlocker, but understand that more complexities are involved.

I reset it via typing "tpm.msc" in the search area to the right of the start menu symbol.

You are then forced to re-enter your Microslop password again and afterwards re-entering your PIN.

This was a no biggie step...

Somehow Microslop managed to corrupt the TPM data, which resulted in a flurry of NULL message errors. Nice error message - not.

I didn't clear the TPM in Windows prior to re-installing; just disabled it in BIOS (which also disables it in Windows).

Good point about Bitlocker. I had actually forgotten that when I disabled the TPM and suddently couldn't boot past Bitlocker without entering the recovery key.

Thankfully, Microsoft automatically keeps a record of the keys generated by Bitlocker in your MSFT user portal and you can get them by going to: aka.ms/recoverykey and entering your account info.

... If I understood chris__74's 09-Feb-2023 post <above> (and Google Translate is accurate) they were able to stop these errors by resetting their TPM module . I haven't tried that yet, but on my Win 10 OS I assume a TPM reset can be done at at Windows Security | Device Security | Security Processor | Security Processor Details | Security Processor Troubleshooting and then clicking "Clear TPM" or by entering tpm.msc in a Run dialog box (Windows key + R) to open the TPM Management Console and clicking "Clear TPM". Have you tried this possible workaround?...

I should also warn users that if they use Bitlocker Disk Encryption and plan try chris__74's suggestion to reset their TPM module that they should probably suspend or disable Bitlocker first (e.g., at Control Panel | Security | Bitlocker Drive Encryption for Professional editions of Windows) and ensure that they have their 48-digit Bitlocker recovery key on hand before starting. Bitlocker is currently turned off on my Win 10 Pro v22H2 laptop and I have no idea what unexpected problems might arise if you reset your TPM module while Bitlocker is enabled.

I'll add that warning to my earlier post.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.2486 * Firefox v109.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.21.231-1.0.1890 * Dell Update for Windows Universal v4.7.1 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 (Version 2301 / Build 16026.20146) Click-to-Run

FIXED (mostly)

1. Disabled the AMD TPM module in system BIOS
2. Disabled Bitlocker Encryption on the C drive
3. Reinstalled Windows 10-2H21
4. Ran Windows Updates and applied all except for the 2H22 rollup
5. Updated system drivers using Alienware/Dell Support Tool
6. Re-downloaded Alienware ACC, Realtek, and NVIDIA drivers from source (instead of using the Windows update versions) as there were numerous errors in the logs after the Windows Updates pertaining to these applications.

The TPM failures are no longer showing in event viewer since the last reboot as 12:12pm PST. Additionally, the sheer number of crashes and hangs being reported in the logs has dropped 10-fold. While that hasn't completely fixed the instability (as I believe there is an underlying HW issue); it has brought a considerable amount of stability to the Operating System considering where it was this morning.

So far, no reboots, hangs, or resets since the laptop was finished updating. Normally, I'd hit a crash within 15-20 minutes.

Here is the system log after the updates: