AMT corruption after MeshAgent "amtconfig" (might just be this computer, not a bigger issue)

[shinomen]

I have a Lenovo M90q Gen3 (11U5000SUS) running Intel AMT 16.0.15 which is configured in ACM mode. We got a call about this system because the client uses it wirelessly only and Windows would not find any wifi networks under. We reinstalled the drivers for wifi and made sure it was the latest intel driver from Lenovo. We tried an update to the Intel ME Firmware and it did not appear to install correctly and wireless network still would not show.
I brought it back to my shop for testing, updated the bios and Intel ME Firmware. What I have found is that when the Mesh Agent configures the AMT, wireless in Windows will not find wireless networks, and when I attempt to go into the Bios and access the MEBx, I get a message that the Firmware failed to load.
To fix it (temporarily at least), I can perform an unprovision of the ME from the bios. It take forever to unconfigure, but then I can access the MEBx settings from the bios and perform the initial password configuration. As long as I do not have the mesh agent perform and AMT configuration, wireless works perfectly fine in windows.
I'm assuming this is going to be a hardware issue that I need to have Lenovo fix but I wanted to mention it here to see if anyone had insight into what causes this or if anyone has had a similar issue they were able to fix?