We just started using the Latitude 5320 after 5310 was discontinued. We use MDT to create and deploy images. We set the storage in BIOS to AHCI, and Secure Boot off. This is standard practice. What we can not disable all the time is HTTPSBOOT, which is something new I have not seen previously. I built the image from scratch using the Windows 10 media creation tool and 20H2 build. After I installed the OEM version, installed all drivers, I captured using MDT and deployed the image. Everything was working fine for a day, but then randomly when shutting the lid , which I have set to sleep on battery, and waiting about 10 minutes, we open the lid and when it would normally come back up to Windows, we get the attached error. After that, going into BIOS doesn't show the M.2 at all until a couple more reboots. This doesn't happen every time but is happening.
"HTTPSBOOT Failed to initialize network connection"
Didn't know if anyone else has ran into similar situation and had a fix or not. I do not believe this to be a driver issue since we are not using RAID in the BIOS and because this typically happens after coming out of sleep or when first trying to boot the device up. And then when the BIOS no longer shows an M.2 drive at all.
Thanks in advance for any assistance.
|Hello, I haven't received the Service tag or Express Service Code yet. Could you share any of them in the text format so that I can assist you with your query?|
Social Media Support
To help us troubleshoot, click our Dell-Cares name and send us a private message with your Dell PC or Monitor Service Tag number
Even though it shouldn't matter, we are going to try imaging after using PXE boot with the RAID driver injected only along with RAID set in BIOS. I am not expecting a miracle on this, but will report back if this somehow fixes the problems we have been having.
@ToddMR74 I am having the same error here - latitude 5520 and 5320.
I have traced the issue down to the machine being in AHCI. If you check the event view do you see any volmgr errors?
Looking in the community forums I am seeing a few other people have this issue as well. I have been working with pro support for the last couple weeks, and the solution I have gotten is create a new golden image using RAID and image the machines in raid.
I went through the last 15 pages of the forum and found the following articles also having similar issues.
I already switched to a RAId image and so far everything has been acting normal. Not sure the advantage to using a RAID confit with a single drive. It’s been working this far so I am sure that is the solution. I just figured it didn’t hurt to try before speaking with Dell.
Hi! I have exactly the same issue on Latitude 5320 (with touchscreen) and <Service Tag removed>.
Any solution to solve it without doing updates in the corporate image for now? Update any BIOS setting? Update a certain driver? Hope someone can let me know a "quick fix" so I can hand it over to user starting next week...
@CeciliaD unfortunately no quick fix as of now. The current word and solution from pro support is that "Dell does not support AHCI or custom images, so use Raid."
I am working with my account manager and trying to escalate, while keeping an eye on any driver updates dell releases, but I haven't heard anything yet.
In the bios you can turn off the HTTPSBoot but that doesn't help with the machine crashing.