Windows Installation Missing

RCon

Commendable
Oct 25, 2016
10
0
1,510
So, I have a weird problem. A friend brought me her laptop. An Alienware 13. It has two hard drives. One with windows and one for general storage (or so I assumed). On startup, it ends up at the screen saying "No bootable devices - Strike f1 to retry boot, f2... etc. I tried the onboard diagnostic. Everything checked out. It sees the hard drives (I assumed the hard drives went bad at first). In the boot option priority it has Windows Boot Manager as it's #1 (is that normal? I normally see hard drive, cd/usb, etc).

What I've tried:
-Using the windows media creation tool, I created a usb. I tried the startup repair. Nothing.
-I went into the cmd and tried the bootrec routes such as fixing the mbr. Nothing
-When I tried bootrec /scanos it said that there were 0 instances of windows found (weird).
-Made a bootable iso for Windows 7 (she upgraded from that to 10. I thought maybe the startup was funky.. So, why not try it?). Nothing

This is a computer that was put into standby by shutting the lid, and reopened to an off computer. Then started up to this.

What could cause the Windows installation to just... disappear? Is there any way to repair windows? Nothing too important on the computer if not. I feel like it may be a problem to reinstall Windows since I have no key and on all of her paperwork that came with the laptop, there was no key (could Microsoft do something about that?).

Any additional info can be provided. I'm sorry, just at a total loss on this one.
 

Colif

Win 11 Master
Moderator
windows boot manager is normal for a UEFI system. If the PC was an ex Win 7 PC, it could be the bios has randomly reset and is trying to find GPT drives where MBR drives are. See if you can find a boot screen in bios and see if you can swap boot method from UEFI to Legacy

did you try a chkdsk /f on the drives? I say drives as you seemed questionable about what purpose of storage is.

Reinstalling win 10 easy, you don't need a key anymore as all the information stored on Microsoft servers. All you do is run the installer, and when you reach screen asking for a key, click "I don't have a key" and win 10 will install and then check the servers to confirm its OK. when she upgraded to Win 10 she got a digital entitlement to always install win 10 on machine again. Its got a licence for its lifetime, not the owners
 

RCon

Commendable
Oct 25, 2016
10
0
1,510
Sweet! I'll try that right now. I didn't do the chkdsk /f. I assumed it was scanning all drives (I even switched to the C: in cmd and did it just in case). I forgot to mention, I did try legacy. However, that wouldn't load either. I'll do the chkdsk /f soon and let you know the results.
 

RCon

Commendable
Oct 25, 2016
10
0
1,510
Ok, so I did chkdsk on the x: drive (I'm assuming that is the windows installation drive). It said The type of file system is NTFS. Cannot lock current drive. Windows cannot run disk checking on this volume because it is write protected.

I switched to C: and did the same thing and got the same thing along with:

Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPEN HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N).

Any suggestions? Should I dismount?
 

RCon

Commendable
Oct 25, 2016
10
0
1,510
Sorry, wow. I completely mixed up chkdsk and bootrec in my first reply (Rereading it, it is all jumbled up). So, I did do a chkdsk to the C:. Came out fine. I did a chkdsk to the x: drive and it did say to do a chkdsk /f to fix the problem. As stated above, I can't since the drive is telling me it is write protected.