Salta al contenuto principale

Rilasciato a Gennaio 2015, l'XPS 13 ambisce ad essere il rivale commerciale del MacBookAir, con lo schermo senza bordi e il Touch-screen opzionale.

75 Domande Visualizza tutte

Dell XPS non-bootable after SupportAssist, glance over my proposed fix

Summarized: SSD issues, not booting due to missing EFI, primary volume recognized as RAW. The concern: losing data. I believe I'm comfortable with rewriting the EFI with bootable image, but will relabeling the RAW volume to NTFS where my primary data storage is have a chance of losing data? My understanding is the command will re-label the volume without formatting.

Dell XPS 13 9343, Win10 x64, Lite-On L8T128L9G-11 (128GB)

Daily driver with usage within 24 hours previous, boot up to error "No bootable image" - have seen this issue with this very Dell XPS (and many other reports online) prior due to updates and usage a toggle of the UEFI to legacy boot or verifying secure boot is disabled fixed it.

This case is different, UEFI shows two partitions with neither bootable. When manually attempting to set path for \EFI\Boot\bootx64.efi is nowhere to be found under file system 0 or 1. I only see a BOOTSECT.BAK file and IndexerVolumeGuid under system volume information.

So it seems to me my EFI volume needs to be rewritten which I can follow along from this guide:

Desired outcome: Get bootable again, no loss of data.


Planned solution: Rewrite MBR and rebuild Boot Configuration File as advised above to get bootable. Targeting Volume 1 labeled ESP.

Then set the primary storage volume back to NTFS using command "format fs=ntfs label=volume label quick"

My questions: Am I misunderstanding/missing anything here or have you some additional guidance? Further, is the above command necessary and will it risk losing my data, does it actually format the partition? Or are we simply telling the filesystem to be NTFS and that's all?

Why do I show 3 more additional RAW filesystems and should I change them to NTFS also?

I don't understand why I show so many volumes (5) and partitions (7) on this disk - 3 recovery partitions, one of which nears 7GB, but I am not able to use that as a bootable image to get to command prompt like I am the bootable USB...


Volume 1 - ESP FAT32 PARTITION 500MB




Previously attempted solutions:

Changing UEFI/Legacy Ensuring Secure Boot is disabled Adding boot delay Attempting to manually navigate to bootx64 Startup repair via Win10 bootable image Updating BIOS to latest

During this process, before trying the BIOS update solution, I noticed it said I was on A03, I know I did a BIOS update last year, the newest BIOS is A20 - how in the world did that happen?

Additional details:

I noticed some battery abnormalities, I went to run a diagnostic (forgetting there was onboard diagnostic) and via the Dell website SupportAssist was installed. Apparently there's some security vulnerabilities with this and it was just after the install and diagnostic ran that my machine became non-bootable. Diagnostics showed me what I already knew that battery is in fair health. Ran a thorough diagnostic on SSD via onboard and it passed.

Thank you for your time

Block Image

Block Image

Block Image

Rispondi a questa domanda Anch'io ho questo problema

Questa è una buona domanda?

Punteggio 1
8 Commenti

BEFORE doing ANYTHING clone the drive or bootup with USB flash drive and copy important files to another drive.


Thanks Mike, but how can I do that? The filesystem is unreadable


@IT FixUp

You said the drive passed the Dell diagnostics test didn't you? The cloning software would be on the bootable USB flash drive and cloned onto or files copied over to another drive. I'll come back later. Key to troubleshooting is to keep things simple. The initial problem is OFTEN very slight and simple. W10 booting often gets "screwed up".


Correct, it passed thorough diagnostic check.

Which avenue would you recommend for most likely to recover data?

A) using bootable Win10 USB, rewrite EFI, then perform chkdsk to repair remaining RAW partitions

B) using USB enclosure for SSD mount to another machine and use a program like TestDisk (or other you may recommend you've had success with) to repair and recover?

C) other

Test Disk - CGSecurity

Thanks in advance


I'd suggest before trying to repair anything you connect the drive to another machine (through a SATA/USB adapter, or however you can) and run I've had success with EaseUS Data Recovery. That should be able to find lost partitions and lost files within them. Depending how much datsa you've got you may be able to recover it all with the free trial. Then re-setp your SSD as new, reinstall Windows and copy your data back.


Mostra altri 3 commenti

Aggiungi un commento

1 Risposta

Risposta Più Utile

This is not so much an answer but rather a possible pathway to try. Data recovery can be very complex. The "RAW" problem can be corrupted partitions and/or filesystems.

You will most likely need a professional data recover program. I've mainly used freeware Testdisk, which you mentioned, and Active, which will cost you. It is your choice. Here is Active's url:

That’s the full package partitions and file recovery. You can try the freeware evaluation version. They also have a freeware program which could initially help you get a better idea of what's what:

Sorry but I don't think there is a simple solution here. It looks like the Dell website SupportAssist really mangled things. For myself, for sport, I try all kinds of little tweaks but for clients I just do the data file recovery. After files are recovered you can always fiddle around with the partitions, etc. if you are curious. I once used EaseUS to convert GPT to MBR partition and then back again and it fixed! Booted.

The extra partitions are for the Windows Recovery programs, boot strap, etc. They do like to make things complicated.

Good luck.

Again I have re-read your questions.

Regarding “During this process, before trying the BIOS update solution, I noticed it said I was on A03, I know I did a BIOS update last year, the newest BIOS is A20 - how in the world did that happen? “ Have you reflashed to A20, of course ensuring that this is the correct BIOS/UEFI for your system?

The following may or may not help. The thing to remember is that the files are all still physically sitting on the HDD/SSD it is just the access to them that is corrupted. This involves just assigning a drive letter to the ESP partition which is already FAST 32.

Regarding Diskpart here is a possible path, again after backing drive up. Most of this you already know but have put it all in for others who may be reading this.

Using the Windows 10 Installation Media :

1.  Insert the Media (DVD/USB) in your PC and restart.

2.  Boot from the media.

3.  Select Repair Your Computer.

4.  Select Troubleshoot.

5.  Select Advanced Options.

6.  Choose Command Prompt from the menu :

i.   Type and run the command : diskpart

ii.     Type and run the command : sel disk 0

iii.    Type and run the command : list vol

7.   Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):

i.   Type and run the command : sel vol <number of volume>

ii.   Type and run the command : assign letter=<drive letter>:

iii.   Type and run the command : exit

8.  In order to repair the boot record :

i.   Type and run the command : cd /d <drive letter>:\EFI\Microsoft\Boot

ii.   Type and run the command : bootrec /FixBoot

End for now but likely more to come later.

Questa risposta è stata utile?

Punteggio 1
Aggiungi un commento

Aggiungi la tua risposta

IT FixUp sarà eternamente grato.
Visualizza Statistiche:

Ultime 24 Ore: 0

Ultimi 7 Giorni: 2

Ultimi 30 Giorni: 23

Tutti i Tempi: 624