Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

My computer cannot boot after update windows 8


  • Please log in to reply

#1
tingtingz

tingtingz

    Member

  • Member
  • PipPip
  • 57 posts
I have a recovery message stating that the boot configuration data file is missing some required information.

File:\BCD
Error code: 0xc0000034

It says I need to use recovery tools on my installation media. I have previously created a bootable windows USB. I think it is for windows 8 but I am not 100% sure. I dont know where else to download a windows 8 bootable USB.

At first I can not see the boot option for USB when secure boot was enable. I was able to see the USB option after switch to legacy boot with secure boot set to disable.

Under legacy boot I moved the usb storage device up to the top of the list. I press F10 save and exit.

I received a message stating a problem with device connected to PC.

An unexpected I/O error has occurred

error code: 0x00000e9

Is this a problem with my bootable USB? Can anyone help me with this?
  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

You can get a fresh 8.1 copy from:

 

https://www.microsof...oad/windows8ISO


  • 0

#3
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I got a copy of the windows 8.1 and created a new bootable USB. I can now have access to repair my computer. Which repair option should I choose?
  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

See Step 3 on

http://james-ramsden...no-disc-needed/

 

or you can try Fix#4 on

https://neosmart.net...to-be-repaired/


  • 0

#5
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I did step 3, should I do the automatic repair on step 4 first or should I try the fix #4 first?

Edited by tingtingz, 14 November 2020 - 06:33 PM.

  • 0

#6
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

Probably the automatic repair will do the fix#4 as part of its routine.   I've used the automatic repair before (on a win 10 when it got stuck in safe mode without a password) but never tried fix#4.


  • 0

#7
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I did the startup repair. A message startup repair couldnt repair your pc appear. I tried the fix #4.

When I reach the command bootrec /ScanOs, instead of total identified Windows installations being 0 as appears on the fix#4 mine showed up as 1 [1] C:\Windows. The operation completed successfully.

When I do the command bootrec /RebuildBcd, I get
Successfully scanned Windows installations.
Total identified Windows installation:1
[1]. C:\Windows
Add installation to boot list? Yes<Y>/No<N>/All<A>:
I enter Y and I got
The requested system device cannot be found.

Edited by tingtingz, 14 November 2020 - 10:19 PM.

  • 0

#8
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

http://triplescomput...sector-and-bcd/


  • 0

#9
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I did the diskpart
When I type list part, I got There is no disk selected to list partitions Select a disk and try again.

I type list volume instead , I can see a list of the volumes

According to this website https://www.google.c...t-be-found.htmlfor solution#2
the efi partition is a FAT32 type. My volume 2 with a label ESP is a FAT32 partition. Is this the EFI partition that is needed to be created from here http://triplescomput...ector-and-bcd/?

If I click the blue link here on solution#2 to create a EFI partition, I get redirected to the website you provided above.

Do I need to create a new EFI partition or can I use the ESP partition as the EFI partition?
  • 0

#10
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

You said you had changed the BIOS to Legacy Boot.  That may be your problem and why list disk doesn't see .  You probably need to have the hard drive set to use the newer standard (UEFI or GPT vs MDR).  Not sure about the secure boot bit.  Perhaps you need to make a new USB that uses GPT/UEFI so you don't need the Legacy Boot. 

 

Alternatively you could give up on trying to restore the drive and just let it reinstall.

 

You may have had a disk failure so nothing you do will fix it.  You might try making a boot USB with Hiren's

https://www.hirensbo...rg/usb-booting/

See if you can get Hiren's miniXP to read your drive.


  • 0

Advertisements


#11
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I made a mistake I did list part and not list disk first. This is why list part didnt work. This time I follow the step accordingly and I can see all the partitions listed. I have five partition listed.

Partition ### Type. Size. Offset
Partition 1 Recovery 1024 MB 1024 KB
Partition 2 System 500 MB 1025 MB
Partition 3 Reserved 128 MB 1525 MB
Partition 4 Primary 921 GB 1653 MB
Partition 5 Recovery 8 GB 923 GB

I did the bootrec /fixboot I got a message
The operation completed successfully.

There is no error message element is not found when I type the command bootrec /fixboot but I received an error when I type the command bcdedit/enum the boot configuration data store could not be opened. The requested system device cannot be found.

Does this mean my disk is not corrupt? I do have a system partition that is 500 MB but I am not sure if the ID is EFI. When I did the list volume command under diskpart command my volume 2 is label as ESP partition FAT32 type with a size of 500MB and the status is Healthy. Can this be the EFI partition?

What should I do if I dont have the element is not found error when I do the command bootrec /fixboot?

Edited by tingtingz, 15 November 2020 - 03:59 PM.

  • 0

#12
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

This is what mine says.  I have two drives.  0 is my boot disk:

 

C:\Windows\system32>diskpart

Microsoft DiskPart version 10.0.18362.1171

Copyright © Microsoft Corporation.
On computer: TVGUY

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          931 GB    93 GB        *
  Disk 1    Online         4657 GB      0 B        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery          1000 MB  1024 KB
  Partition 2    System             260 MB  1001 MB
  Partition 3    Reserved           128 MB  1261 MB
  Partition 4    Primary            837 GB  1389 MB

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E   NEW          CDFS   DVD-ROM      654 MB  Healthy
  Volume 1     C   Windows8_OS  NTFS   Partition    837 GB  Healthy    Boot
  Volume 2         WINRE_DRV    NTFS   Partition   1000 MB  Healthy    Hidden
  Volume 3         SYSTEM_DRV   FAT32  Partition    260 MB  Healthy    System
  Volume 4     D                NTFS   Partition   4657 GB  Healthy

DISKPART> exit

Leaving DiskPart...

 

I tried

C:\Windows\system32> bcdedit /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  unknown
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {current}
resumeobject            {521ee725-1530-11ea-8376-18cf5e5ab93a}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {521ee725-1530-11ea-8376-18cf5e5ab93a}
nx                      OptIn
bootmenupolicy          Standard

C:\Windows\system32>

 


  • 0

#13
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I have attached a picture of what I get with the same commands.

Should I do what the website http://triplescomput...sector-and-bcd/says even though I dont have the element not found error?

This is what the website says:
In many cases the failure is evident when attempting to perform bcdedit /enum and receiving a message such as this one:

The boot configuration data store can not be opened.
The requested system device cannot be found.

Performing bootrec /fixboot also provokes the following error:

Element not found

This is bad news on a GPT disk using UEFI rather than BIOS. Essentially, the system is looking for the EFI partition, which in this case is either missing or corrupt.

If its corrupt but still exists, you can simply enter diskpart, select the system partition (usually around 500 MB in size and with an ID of EFI) and assign it a letter, exit diskpart, and then perform a chkdsk command on the new partition assignment. This sometimes will correct it. Other times, forcibly removing the EFI and boot folders from the EFI partition and then executing the bcdboot command with a specific system partition parameter (e.g.: bcdboot X:\windows /s E:, where X: is the Windows partition and E: is the EFI paritition) works.

Attached Thumbnails

  • EB025D2B-768A-41C8-A694-33932D6DF9D2.jpeg

Edited by tingtingz, 15 November 2020 - 04:00 PM.

  • 0

#14
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,363 posts
  • MVP

I'd try the assigning letter then diskchk trick on the 500MB.  Can't hurt anything.


  • 0

#15
tingtingz

tingtingz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I assigned the letter m to the partition and did the chkdsk command.

I have attached two pictures of the results5D8FCC5F-9BE4-4BA4-ABBF-6908BADE982B.jpeg F1C2A537-466D-4ACF-B460-AD3AF971E7F1.jpeg

Edited by tingtingz, 15 November 2020 - 04:02 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP