Total identified Windows installations: 0

Question

Please help me.

After updating my Microsoft Surface RT to Windows 8.1, it failed to start up again. 

It will prepair and attempt auto repair, which also keeps failing and will give me:

Log file: C:\windows\System32\Logfiles\Srt\SrtTrail.txt

I tried to recover with the USB, but this doesn't work.

After trying to bootrec/rebuildbcd I find that there are "Total identified Windows installations: 0"

Also I will get either a Bad system config info blue screen.

I really don't know what went wrong, I am just pretty upset that my tablet remains unresponsive.

What else is there to do?

I live in The Netherlands but bought my tablet in the US. Could this be the problem?

***Post moved by the moderator to the appropriate forum category.***

Answer 1

Hi,

1. First Start System Recovery Options. To start system recovery options.

a) Boot from the disk, Once you get the welcome screen of installation with the option “Install now”

b) Click on Repair your computer

c) On the next page click on Advanced Options

d) Now click on Troubleshoot

e) Lastly click on Command prompt and follow the on screen instructions

2. At the prompt, type the bootrec command as shown below and then press Enter:

bootrec /rebuildbcd

The bootrec command will search for Windows installations not included in the Boot Configuration Data and then ask you if you'd like to add one or more to it.
3. You should see the following message.
Scanning all disks for Windows installations.

Please wait, since this may take a while...

Successfully scanned Windows installations.

Total identified Windows installations: 0

The operation completed successfully.

4. Since the BCD store exists and lists a Windows installation, you'll first have to "remove" it manually and then try to rebuild it again.

At the prompt, execute the bcdedit command as shown and then press Enter:

bcdedit /export c:\bcdbackup

The bcdedit command is used here to export the BCD store as a file: bcdbackup. There's no need to specify a file extension.

The command should return the following on screen:

The operation completed successfully.

Meaning the BCD export worked as expected.

5. At this point, you need to adjust several file attributes for the BCD store so you can manipulate it.

At the prompt, execute the attrib command exactly like this:

attrib c:\boot\bcd -h -r -s

What you just did with the attrib command was remove the hidden, read-only, and system attributes from the file bcd. Those attributes restricted the actions you could take on the file. Now that they're gone, you can manipulate the file more freely - specifically, rename it.

6. To rename the BCD store, execute the ren command as shown: ren c:\boot\bcd bcd.old

Now that the BCD store is renamed, you should now be able to successfully rebuild it, as you tried to do in Step 2.

Note: You could delete the BCD file entirely since you're about to create a new one. However, renaming the existing BCD accomplishes the same thing since it's now unavailable to Windows, plus provides you yet another layer of backup, in addition to the export you did in Step 5, if you decide to undo your actions.

7. Try rebuilding the BCD again by executing the following, followed by Enter: bootrec /rebuildbcd

which should produce this in the Command Prompt window:

Scanning all disks for Windows installations.

Please wait, since this may take a while...

Successfully scanned Windows installations.

Total identified Windows installations: 1

[1]  D:\Windows

Add installation to boot list? Yes<Y>/No<N>/All<A>:

meaning that the BCD store rebuild is progressing as expected.

8. At the Add installation to boot list? question, type Enter Y or Yes, followed by the Enter key.

You should see this on screen:

The operation completed successfully.

meaning that the BCD rebuild is complete.

9. Restart your computer.

Assuming that an issue with the BCD store was the only problem, Windows should start as expected.

If not, continue to troubleshoot whatever specific issue you're seeing that's preventing Windows from booting normally.

Important: Depending on how you started System Recovery Options, you may need to remove a disc or flash drive before restarting.

Answer 2

Hi Sandor,

To undo the step 5 provided by Vijay B, replace the -h -r -s  to  +h +r +sin the Command Prompt.

Please let us know how it goes for us to assist you further.

Answer 3

Hi Vijay,

Thank you for your reply.

Unfortunately my tablet doesn't start up normally at all.

What I get is:

-Preparing Automatic Repair

-Diagnosing your PC

And then the blue screen telling me that Automatic Repair couldn't repair my PC

Log file: C:\windows\System32\Logfiles\Srt\SrtTrail.txt

Instead of any of this:

"1. First Start System Recovery Options. To start system recovery options.

a) Boot from the disk, Once you get the welcome screen of installation with the option “Install now”"

But I did find a way to proceed with the other steps, through advanced options-troubleshoot-advanced options-command prompt.

Then I come to step 5.

"5. At this point, you need to adjust several file attributes for the BCD store so you can manipulate it.

At the prompt, execute the attrib command exactly like this:

attrib c:\boot\bcd -h -r -s

What you just did with the attrib command was remove the hidden, read-only, and system attributes from the file bcd. Those attributes restricted the actions you could take on the file. Now that they're gone, you can manipulate the file more freely - specifically, rename it."

But then I get:

Path not found - C:\boot

and I'm stuck again...

Hope it's fixable.

Thanks again!

Answer 4

Hi,

I would suggest you to go to the command line

Execute "bcdboot c:\windows (file:///c:/windows) /s c:"

Answer 5

hello Vijay B, i have exactly the same problem that you guys are talking about, and now im stuck at the step 5 with the message 

Path not found - C:\boot

what i have to do now? i really haven't understood your last message  can you give me a step by step...

i've just bought the surface rt and it is very expensive here in brazil, it is unbelievable that it stops working because of a update!