Bootable Usb Solution
Marquez Feliciano
Not sure whether this was due to 1. An update that may have gone askew, or 2. An app that was suggested by /u/DellCares (on reddit) called superfix causing an issue. The app was a means to fix microphone issues I was having, but wasn't working properly.
Now I've been scouting around and no one seems to have had errors recently... Though, there was a similar issue for 9550s: _15_9550_no_bootable_devices_found_after_bios/ In which the fix was going into BIOS and finding bootx64.efi, of which I cannot find (it does not appear on the list). So this may have been deleted.
Regarding my intermittent UNEXPECTED STORE EXCEPTION errors when resuming from sleep, I do now feel confident they have stopped altogether. Just on the very off chance this did help, I remember disabling the "slideshow" in the lock screen, and I also disabled those random little "fun fact" messages. It seems unlikely that this would make any difference though. As I mentioned before, an Intel update (in Windows Update) did come through as well, so maybe that helped. I should also mention that my machine is refurbished - it was not brand new. (I only bought it very recently)
My reddit link wasn't super clear, but it uses that same method as your above links.
The issue is when I add boot option, there isn't a 'Boot' folder with 'bootx64.efi', on top of this there's no things to tick in the boot sequence.
So the issue must be... Where is the boot manager? and where is bootx64.efi?
I've figured this is my direction; though, I'm having another issue and that's to do with the USB. At the moment I only have access to a MAC; and it's been suggested to format to fat32, use unetbootin (with the downloaded win10 iso) and then use that as a flash drive; however, when plugged into my XPS, it doesn't seem to want to be detected after I press f12 on the dell logo. It came up once, but didn't work, and never came up again. I've messed around with the legacy boot, etc. What do you think would be the reason why it's not being detected as a USB?...
If you answer all my questions as yes, I suggest creating a windows 10 installation media from the link below.You'll need a blank USB flash drive with at least 8GB of space and a good working computer .
After creating the bootable windows 10 installation media, plug it into the computer that needs to be fix. Please use the F12 key to boot off the flash drive. In the windows setup screen, select Repair Your Computer, Advanced Options and then Startup Repairs.
I'm assuming you tried changing the SATA controller mode setting to AHCI (from Raid On) or vice-versa as suggested in the link you have posted ? Is the Hard drive or solid state drive detected in the BIOS? You tried resetting BIOS to defaults.
You'll have to change Legacy to UEFI and enable secure boot in the BIOS. The flash drive usually could be booted from the BIOS but as you have mentioned, certain components are missing, therefore I'm hoping you can boot the flash drive from Dell Pre-boot menu -F12 key). Just to sure you're performing the correct steps to get into Preboot menu:
Ok, thanks for the photos. I can't get to this screen yet. I just plugged in another USB (with an unzipped dell recovery - which said 'couldn't detect windows', or something to that effect), which was detected by my laptop, so I'm gonna try that one as I don't actually have any access to windows computers... lol.
Yep these don't work unfortunately. Nothing appears in the F12 menu under UEFI Boot, unless I go into the BIOS and 'load a boot', of which once I restart and go to the F12 menu again and click the boot I created, it comes up with... 'System was unable to boot. No bootable devices found.'
However could you clarify what you mean by 'Repair your computer tool' Windows 10 creation media, means?
My USB is an unmounted windows 10 x64 ISO, which I downloaded off the website, if that helps. The Creators fall edition was unselectable; and I do recall that my Laptop has the Falls Creators edition.
A relatively new form of problem which has been introduced by the wider adoption of solid-state drives (and other drives with more particular power requirements than standard mechanical hard drives) is that of drive detection and compatibility. This applies most notably to sleep/resume and cold boot detection of these devices, which sometimes are not detected at all on specific systems. Occasionally a BIOS update on the computer or a firmware update to the drive can resolve the issue, but other times, the drive may simply be incompatible.
Interestingly, if the user presses F1 to retry, the machine then boots normally. This indicates that the problem has to do with the machine not detecting the drive quickly enough during POST to continue with the boot process.
I installed a Samsung EVO 850 msata SSD as a primary drive and experienced the issue as described above. However, I had already set the BIOS to AHCI before I installed the drive and did a clean install of Windows 10. Yet it still shows the error above at POST, and pressing F1 pretty much immediately always results in a normal startup with no other problems.
After flowing the above with no luck I discovered that where I had changed to Legacy boot the BIOS had decided that boot from Diskette should be at the top of the boot order. Removed this and put the SSD to the top and all is now fine.
I had this issue with a Dell e6430 (BIOS v.A21) after clean installing Windows onto a new SSD. To fix it go to the BIOS -> System Configuration -> SATA Operation and change it to AHCI. Then reinstall Windows.
hi i have dell inspiron 3330 laptop i installed windows 7 on a SSD, evrything went perfect except when the laptop reboots it says no bootable device found however if i go into bios and select internal hdd as the bootable device then it boots into windows, the bios is on system defaults, any ideas what might be the issue?
I have a Latitude D630 Rundung a Crucial SSD. And After Shutdown because of empty battery i restarted the Maschine and gut the issue Seen above. BIOS Shows noch primary hdd anymore. Eventuell replacing hdd against another Crucial SSD gutes mehr the Same result (noch primary hdd in BIOS). Hdd mode is on ahci.
Had to change two things on my Latitude E6540 with A26 BIOS: First one was the SATA setting from RAID to AHCI, second one was the boot-mode from legacy to UEFI. No way to boot that ugly piece in legacy mode.
Hello experiencing the same problem with Dell Latitude 3480 on AHCI and Ubuntu 16.04 LTS, the system just does not detect the hard drive on boot, but does so if I boot with a LiveCD, I can even Chroot into it and every SMART test runs fine, amy suggestions?
I know I could use diskpart and xcopy to do something similar in the pre-boot menus, but I will have to walk a remote user through the process of doing this and would rather have something with a GUI that I can provide instructions for.
Disk cloning software can be used to create an exact copy of your disk, and copy all data from the source disk to the target disk, including files, disk layout, configurations, etc. This post will introduce 12 free disk cloning software that helps...
I would have to cast my vote to Acronis Cyber Protect Home Business Premium and if you can get your hands on Acronis TI. I have made 2 USB boot drive one for Windows and one for Linux covers both for booting and cloning drives, adding drives and other utilities. Have used them for years very reliable and quick. I even still have a couple of bootable DVD drives with Acronis TI, they work great.
As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. The signed Microsoft Recovery Tool can be found in the Microsoft Download Center: =2280386. In this post, we include detailed recovery steps for Windows client, servers, and OS's hosted on Hyper-V. The two repair options are as follows:
Recover from WinPE (recommended option)
This option quickly and directly recovers systems and does not require local admin privileges. However, you may need to manually enter the BitLocker recovery key (if BitLocker is used on the device) and then repair impacted systems. If you use a third-party disk encryption solution, please refer to vendor guidance to determine options to recover the drive so that the remediation script can be run from WinPE.
Recover from safe mode
This option may enable recovery on BitLocker-enabled devices without requiring the entry of BitLocker recovery keys. For this option, you must have access to an account with local administrator rights on the device. Use this approach for devices using TPM-only protectors, devices that are not encrypted, or situations where the BitLocker recovery key is unknown. However, if utilizing TPM+PIN BitLocker protectors, the user will either need to enter the PIN if known, or the BitLocker recovery key must be used. If BitLocker is not enabled, then the user will only need to sign in with an account with local administrator rights. If third-party disk encryption solutions are utilized, please work with those vendors to determine options to recover the drive so the remediation script can be run.
Additional considerations
Although the USB option is preferred, some devices may not support USB connections. In such cases, we provide detailed steps below for using the Preboot Execution Environment (PXE) option. If the device cannot connect to a PXE network and USB is not an option, reimaging the device might be a solution.
Prerequisites for using the boot media
The BitLocker recovery key for each BitLocker-enabled impacted device on which the recover media is used may be required. If you are using TPM-only protectors and using the safe boot option, then the recovery key will not be required. If you are using TPM+PIN protectors, then you may need the recovery key if you do not know the PIN for the device.