LENOVO ThinkPad P1 Gen3/X1 Extreme Gen3 - Help me!

[nox73732]

Hi everyone, I hope I'm in the right place!?
and sorry for my english!

I have ThinkPad P1 Gen3/X1 Extreme Gen3
I still have 2 months of On-Site Warranty!

initially our IT department
he had set a Supervisor password that blocked only part of the BIOS settings.
Supervisor password = PeP11
it always worked

After a recommended update, (he thinks gone bad at this point)
Performed via Soft Lenovo Vantage
("BIOS Update (Utility & Bootable CD) for Windows 11, 10 (64-bit),
Linux - ThinkPad P1 Gen 3 (Type 20TH, 20TJ), X1 Extreme Gen 3"

"Firmware for Windows 11 (64-bit), 10 (64-bit) - ThinkPad USB-C Dock Gen 2")

I find myself
"Error 0199: System Security - Security password retry count exceeded"
"Press F1 to enter Setup."
Supervisor password = PeP11
it is no longer accepted and also blocks the Machine entirely
example
F12 boot menu
any operation postpones
"Error 0199: System Security - Security password retry count exceeded"
"Press F1 to enter Setup."

Opened a ticket in LENOVO assistance
but they say it's a software problem and not a hardware one
and they cannot intervene!!
incredible !!!!

I just don't know how!
if there is a way to overcome this obstacle?
Or how to possibly repair it under warranty since it's still there!
Any suggestion is welcome!

HI
Thank you

[mon2]

Re: LENOVO ThinkPad P1 Gen3/X1 Extreme Gen3 - Help me!

Go back to their tech support and ask for the supervisor if you receive the same comments for this case. Tell them that you are posting this miserable support experience in the public media and that this will influence their future business dealings.

We had a similar issue with Dell on one of their $1500+ giant tablet ('Maxipad'???). After a few chats with the right support team member, they sent out a replacement and stated that the defective logic board will be restored via JTAG tools that are handled by another group deployed by Dell.

[nox73732]

Re: LENOVO ThinkPad P1 Gen3/X1 Extreme Gen3 - Help me!

good idea!!

I would like to know
if such a problem has already happened, on the same or similar machines?