I'm running into a strange issue with a Dell Inspiron 3455 AIO system that came with Windows 10 pre-installed. I started by booting the system up with the existing hard drive to make sure everything worked ok, which it did. I should also note that the system was booting via UEFI w/ Secure Boot out of the box.

I then proceeded to replace that hard drive with a new Samsung 850 EVO SSD, and did a fresh install using a USB drive formatted with the Windows Media Creation Tool. I was able to boot off the USB drive and install Windows without issue. However, upon restart, Windows would not boot. It would just freeze on the Dell logo.

In an attempt to narrow down the issue, I've tried installing Windows using a USB key created with Rufus, installing from a DVD, and installing with Secure Boot off. No matter what I do, Windows will not boot if I install via UEFI, even though the installation finishes without issue every time.

Of course, when I install Windows via CSM/Legacy, everything works fine.

I'm at a loss here. The only thing I can think of is that there is something going on with the Dell BIOS that is preventing this from working. Ultimately, I can just live with CSM, but I'd really like to figure out what's causing this.

  • Try reinstalling Windows with Secure Boot on and CSM disabled, then once it reboots to finish installing Windows, go into the BIOS and turn Secure Boot off. I don't know what the issue is, as I haven't had the time to delve into troubleshooting, however this is an issue with the most recent Windows Update that was pushed around a week ago. I have an AW18, so it could be an issue with Dell's certificate (either on Dell's side or Microsoft's), or it's an actual bug in the most recent update from around a week ago. You can always WIM the old system partition and apply it to the 850 EVO – JW0914 Jul 28 '17 at 0:12
  • Wouldn't it be easier to just disable Secure Boot and disable CSM. Sexy Boot is always optional on OEM machines from Dell (required for Dell to sell the machine) – Ramhound Jul 28 '17 at 0:13
  • @Ramhound Doesn't Secure Boot prevent exploits from rootkits? – JW0914 Jul 28 '17 at 0:17
  • 1
    @JW0914 The general idea would be to get the installation installed and working then turn it on. But if your infected with a root kit your infected with malware that loaded that rootkit more then likely. – Ramhound Jul 28 '17 at 0:21
  • 1
    @JW0914 - why not post an answer? Just put all your comments in a complete answer. – snayob Jul 29 '17 at 14:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.