# DGX Spark corrupted TCG OPAL password and UEFI administrator after unexpected shutdown

**URL:** <https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949>\
**Category:** DGX Spark / GB10\
**Tags:** dgx-spark-issue\
**Created:** [May 4, 2026, 9:11pm UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949 "2026-05-04T21:11:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cvella](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@cvella](https://forums.developer.nvidia.com/u/cvella)\
**Post date:** [May 4, 2026, 9:11pm UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949/1 "2026-05-04T21:11:18Z")

</div>

I purchased 2x dgx sparks founder edition and set them up identically.

They were both running fine, however one shut down on its own and when I booted it back up, the TCG OPAL password I had configured didn’t work to unlock the drive. I used PSID to reset the drive, during which I also noted that the administrator password for UEFI was now blank (as in, I had to just press enter without entering my usual password as my configured UEFI administrator password did not work).

Now the spark is back up and running, however I cannot update any firmware. When I attempt to update firmware I’m prompted to enter the administrator password for the capsule update, however nothing works here (pressing enter with a blank password, my previous configured administrator password, etc).

It appears somethings got corrupted in UEFI alongside the TCG OPAL password when the spark shut down for some reason, I assume a bad automatic update or some form of crash. The other spark which was setup identically remains fine.

---

<div class="post-metadata">

**Author:** ![aniculescu](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/aniculescu/32/382649_2.png) [@aniculescu](https://forums.developer.nvidia.com/u/aniculescu)\
**Post date:** [June 2, 2026, 4:46pm UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949/3 "2026-06-02T16:46:09Z")

</div>

Please try reimaging your unit. You may have ended up with a corrupt EFI paritition

---

<div class="post-metadata">

**Author:** ![cvella](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@cvella](https://forums.developer.nvidia.com/u/cvella)\
**Post date:** [July 9, 2026, 4:00am UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949/4 "2026-07-09T04:00:51Z")

</div>

Hi,

I have performed this, however as the bios administrator password somehow got corrupted, I cannot disable secure boot or authorise the capsule update that attempts to occur after a system image, leaving firmware updates still locked out for the device.

---

<div class="post-metadata">

**Author:** ![aniculescu](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/aniculescu/32/382649_2.png) [@aniculescu](https://forums.developer.nvidia.com/u/aniculescu)\
**Post date:** [August 13, 2026, 3:32pm UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949/5 "2026-08-13T15:32:41Z")

</div>

Please reach out to customer care and request an RMA

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [August 27, 2026, 3:33pm UTC](https://forums.developer.nvidia.com/t/dgx-spark-corrupted-tcg-opal-password-and-uefi-administrator-after-unexpected-shutdown/368949/6 "2026-08-27T15:33:12Z")

</div>

Closed on August 27, 2026, 3:33pm UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
