Inspiron 5441 Windows ARM BSOD after updates

My new Inspiron 5441 Windows ARM laptop crashed while I was setting it up. I updated software with SupportAssist. After a reboot required by Windows update, it crashed with BSOD and I have to send it back to Dell. Dell has rushed out a less-than-half-backed product without adequate preparation.

Are there similar issues with other WIndows ARM (Snapdargon) systems? 

If you're interested in the details, I attach parts of a description which I pasted to the device upon return. It outlines the sorry state of NO-support for Windows ARM OS.

Comment on Dell

My experience and online posts indicate that Dell has rushed out Windows ARM systems as half-baked products. Tech support is completely inadequate, untrained, and mostly unaware of ARM systems (including the fact that they are incompatible with x84/x64). Is Dell committed to emerging technology?

 Summary

re Dell 5441, Windows 11 CoPilot+, i.e. ARM OS, 

Status: Blue screen of death. Self repair failed. I followed on-screen instructions with no luck. 

Problem description

While setting up my new Dell ARM-based PC running Windows 11, I proactively used SupportAssist to install seven recommended updates. The system restarted successfully afterward. However, following a subsequent Windows/Dell update — which probably included a BIOS update — the required restart caused the system to break and give the dreaded BSOD. It now fails to boot and prompts for the BitLocker recovery key.

I followed the on-screen instructions, including re-installing Windows to no avail. I then ran Diagnostics: all tests passed.  I then reset the BIOS to BIOS default; again no success. I can’t attempt a manual recovery as I can’t create a recovery disk on my x64 Dell for ARM OS.

Diagnosis (guess)

The problems appear to be the result of the BIOS update resetting critical configuration settings. As a result:

• Secure Boot, TPM state, and boot mode may have reverted to generic defaults
• The boot chain was broken, triggering BitLocker recovery
• The system is now inaccessible despite recovery attempts