Lenovo confirms Legion Go BIOS V42 can brick handhelds; repair costs still unresolved

What happened

Lenovo has confirmed that a BIOS update can leave its Legion Go handheld gaming PC unusable, following weeks of user reports about bricked devices and steep repair bills.

According to The Verge, the company acknowledged that some Legion Go units hit a blank screen while installing BIOS version V42, known by its file name N3CN42WW. Lenovo has removed the update from its support website while it continues validation work, and says users who already completed the installation successfully do not need to take further action at this time.

The blast radius is limited. As The Verge explains, the update never went out through Windows Update or Lenovo's Legion Space software — it had to be downloaded manually from Lenovo's own site during the roughly two months it was available. Only the original Legion Go 8APU1 is in scope; the Legion Go S and the newer Legion Go 2 are not affected.

Lenovo's advice to affected users

Lenovo's suggested remedy is basic: hold the power button down for roughly ten seconds, wait about a minute, then try powering the device back on. If the machine still will not start, customers are directed to Lenovo Support.

Whether the bug strikes every updated device is unclear. The Verge's Sean Hollister installed V42 on his own review unit and sat through a six-minute sequence of black screens, progress bars and warning messages before the handheld booted normally — and even gained the ability to enter a Windows PIN with the gamepad controls afterward.

On Lenovo's official forums, an account posting as Daniel_Legion, apparently a Lenovo employee, offered a partial explanation: a team in Europe reproduced the failure on three out of three devices tested, while other teams could not trigger it at all. That points either to a specific component used on mainboards in certain production batches, or to particular conditions required for the fault to appear, the poster wrote.

The unresolved repair bill question

The reason the story has lingered is money. Three weeks before Lenovo broke its silence, a Reddit user shared a repair bill of nearly $300 for their bricked handheld, among other reports of damage and costly fixes, according to The Verge.

The same forum post from Daniel_Legion suggested devices under warranty should be repaired at no cost, and that out-of-warranty units should be as well — with the caveat that users should check their local laws.

That caveat matters. The Verge notes that the Daniel_Legion account has no other visible posts on Lenovo's forums, and the publication is asking the company to confirm both the poster's identity and the meaning of the statement. A commitment that appears to hinge on local legal requirements is a weaker promise than an unconditional one, and Lenovo's official statement to The Verge makes no mention of repair costs at all — it only tells affected users to contact support.

The Verge draws a contrast with Framework, the modular laptop maker, which handled its own device-bricking BIOS update by committing to fix affected hardware for free even outside warranty. Hollister argues a company should not need to finish its investigation before reassuring customers that it will repair damage its own update caused.

Why it matters

The incident is a small-scale version of a recurring problem in consumer hardware: a firmware update that fails mid-install can turn a working device into an expensive paperweight, and there is no settled rule about who pays. Lenovo has confirmed the bug and withdrawn the update, but its formal guidance stops at directing users to support, while the most generous signal on repairs comes from an unverified forum account. Until Lenovo states plainly whether it will cover out-of-warranty fixes, owners of bricked units are left negotiating one by one — and the precedent set by companies like Framework shows that a clearer, more reassuring response was available. It is also a reminder that firmware downloaded straight from a vendor's own support site can still ship broken, and that letting early adopters do the testing for you is sometimes the wiser move.