Join Us!

Windows 10 will not...
 
Notifications
Clear all

Windows 10 will not boot  

Page 1 / 2
  RSS
wotsits
(@wotsits)
Active Member

Windows 10 PC, no recovery partition.

I installed Windows updates, did the restart to finish installing updates and then ran into this problem.

The only thing that can be accessed is the BIOS. I turn the computer on it goes past the BIOS and then just goes to a black screen with flashing white cursor. It is unresponsive to any keys entered and doesn't go any way beyond this screen.

As it doesn't go to Windows I can't do Safe Boot or any of those tricks.

I inserted a Windows bootable installation USB and went to the repair Windows page.
-Tried Startup repair - it said couldn't be repaired
-Went into CMD - tried to repair the boot record, still didn't work
-As a final recourse I went to the reset Windows option with keep files - it said couldn't reset Windows

Finally I used the Partition Wizard bootable .iso and still couldn't get it fixed.

Can anyone advise me what else I can do? I've followed every option I can find and nothing has worked

Quote
Posted : 26/05/2017 9:02 pm
RolfGutmann
(@rolfgutmann)
Community Legend

You destroyed the BIOS/UEFI. Check your mainboard's support site to download a flasback file to put on a USB flash drive and to push into the mainboard (often specific USB port ON! THE MAINBOAD) not outside.

Windows 10 Home can do this.

ReplyQuote
Posted : 26/05/2017 10:08 pm
wotsits
(@wotsits)
Active Member

I didn't touch the BIOS how could I have destroyed it?

I can enter the BIOS setup and all seems normal, the BIOS is the one thing I can enter!

ReplyQuote
Posted : 26/05/2017 10:50 pm
wotsits
(@wotsits)
Active Member

This is a Sony Vaio BTW

ReplyQuote
Posted : 26/05/2017 11:12 pm
RolfGutmann
(@rolfgutmann)
Community Legend

A month ago we had a W10 machine and run WinUpd, after the BIOS/UEFI was damaged and we had to flashback. Dont ask me how this can go, it just happened. Was a 2012 Asus mainboard and a machine which had W10 not native but by step-up W7, W8, W8.1 and W10.

ReplyQuote
Posted : 26/05/2017 11:56 pm
jaclaz
(@jaclaz)
Community Legend

The blinking cursor (or a g or a j not blinking) in the top left of screen is traditionally connected to issues with the early booting code, that would reside in the MBR and/or the PBR on BIOS and directly into the firmware if UEFI or with wrong data in partition table and/or filesystem bootrecord.

Is it BIOS (or UEFI in CSM) or is it UEFI?
Is the disk MBR or GPT?
Which EXACT model is the PC?
Which EXACT model is the hard disk or SSD inside it?

Dump the first 2100 sectors of the device (the PhysicalDrive) via dd or similar, then compress them in a .zip or .7z archive, upload the archive somewhere and post a link to download it, I can easily check at least the partition data.

jaclaz

ReplyQuote
Posted : 27/05/2017 12:52 am
wotsits
(@wotsits)
Active Member

Some more diagnostics seems to indicate it's a problem with the bootmgr - if my limited understanding is correct then from what I can gather the system partitions are not linking to the bootmgr

I've tried a lot of the cmd commands I've found out there to fix the bootrec, can anyone give any further advice?

This is a BIOS setup

ReplyQuote
Posted : 27/05/2017 2:51 am
wotsits
(@wotsits)
Active Member

As a last effort, the only thing left I can think of is to go to Install Windows instead of trying repair.

Will this work and more importantly will I lose all my files if I do this? I know I will lose all installed programs, but what about files?

ReplyQuote
Posted : 27/05/2017 4:00 pm
jaclaz
(@jaclaz)
Community Legend

Some more diagnostics seems to indicate it's a problem with the bootmgr - if my limited understanding is correct then from what I can gather the system partitions are not linking to the bootmgr

I've tried a lot of the cmd commands I've found out there to fix the bootrec, can anyone give any further advice?

This is a BIOS setup

If you have a blinking cursor, as stated, this is usually connected to either the MBR or more commonly the PBR code and data.
The normal booting sequence (BIOS) is
1- BIOS
2- MBR code reading MBR data (partition table)
3- MBR code chainloading the PBR of the active primary partition found in partition table
4- PBR code reading PBR data (filesystem data)
5- PBR code chainloading the loader stated in PBR (BOOTMGR)
6- BOOTMGR reading \boot\BCD settings
7- BOOTMGR chainloading WINLOAD.EXE
8- Winload.exe loading windows

The blinking cursor typically can happen because something is wrong in #2 to #5, if anything is a problem in #5 (last action) to #8 the result is either a text error message or a BSOD (or frowny face in Windows 10).
Both the code and the data in both the MBR and in the PBR of the active partition may cause it, and you need to check those.

You can restore the code of both the MBR and the PBR using bootsect.exe, but it is more likely that the issue is in the data that you will have to check manually.

Before anything else, I would try booting from USB a grub4dos instance and check if directly chainloading the BOOTMGR on the internal disk (i.e. bypassing steps #2 to #5) the system boots.

You can make easily a USB stick booting grub4dos using RMPREPUSB
https://www.rmprepusb.com/

Once you have it booting, press c to get to command line and in it type
find –set-root /bootmgr
chainloader /bootmgr
boot

jaclaz

ReplyQuote
Posted : 27/05/2017 4:08 pm
wotsits
(@wotsits)
Active Member

What about if I just Install Windows again? Will that work and can I keep my files?

ReplyQuote
Posted : 27/05/2017 4:17 pm
jaclaz
(@jaclaz)
Community Legend

What about if I just Install Windows again? Will that work and can I keep my files?

I don't know if you are serious. ?

You have a defective spark plug in your engine.
Do you replace the engine with a new one?
Do you also ask if you can keep the wheels and tires?

Of course it depends on HOW EXACTLY you are going to reinstall the OS, but additionally until the cause of the issue is found, how can you expect (with 100% certainty) that the reinstall procedure
1. will work
2. will work without overwriting your files (of which you should already have made not 1 but 2 backups)

Right now your PC is in an "indeterminate" state, "something" doesn't work and there is nothing that can tell you whether this "something" that isn't working will (or will not) affect the reinstall procedure and/or the overwriting of your files.

The only thing I can say is
http//www.imdb.com/title/tt0097216/quotes?item=qt0362962

jaclaz

ReplyQuote
Posted : 27/05/2017 4:30 pm
wotsits
(@wotsits)
Active Member

Even further diagnostics have revealed it appears that the volume where Windows is installed is 'locked' - yet still no solution found

Can anyone direct me further?

ReplyQuote
Posted : 28/05/2017 2:28 pm
kacos
(@kacos)
Member

Even further diagnostics have revealed it appears that the volume where Windows is installed is 'locked' - yet still no solution found

Can anyone direct me further?

What do you mean 'locked' ? and how did you find that?

PS1 did you check the boot order settings in BIOS?
PS2 do you have any USB/external devices plugged in? If so remove them.

after you check the above and try to boot, if it still doesn't boot, start the USB win installation in recovery mode, go to advanced settings and CMD prompt, try these commands

bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot

remove the USB stick, and reboot

ReplyQuote
Posted : 28/05/2017 2:40 pm
wotsits
(@wotsits)
Active Member

Already tried all that so many times

I tried to completely reinstall the system as a last resort and then it said the Windows volume was 'locked'

ReplyQuote
Posted : 28/05/2017 3:19 pm
kacos
(@kacos)
Member

Is the drive a normal HDD or an SSD?

You could also go to a cmd prompt and check if the drive is set as read-only

diskpart.exe
list disk
select disk X <———– from the output of the previous command X is the system disk (eg 0)
attributes disk <——– display the attributes of that drive

if it is indeed set as read-only, type

attributes disk clear readonly
exit

and reboot

EDIT

while in diskpart, if the disk listing shows the system disk as 'offline' you may want to enter this command to fix it

SAN POLICY=OnlineAll

ReplyQuote
Posted : 28/05/2017 3:21 pm
Page 1 / 2
Share: