Windows Boot Manager Windiws\system32\drivers\rsteachci.sys error

Hi,
We are using SCCM 2012 R2 SP2, CU3. When I boot up from PXE and after loading files, I get this message:
File:\Windows\system32\drivers\rsteahci.sys
Status 0xc000035a
I already recreated my boot.wim but to no avail. What do I do?

This is clearly an issue with the drivers in your boot image. Yes, for boot image driver issues you must update the boot image and ensure it's been updated on the DPs for it to be effective.
It happens before you get a change to select a TS because its an issue with the boot image itself which must fully load for anything task sequence wise to actually happen.
When testing boot image image issues, always make sure that you know which boot image you are updating and which one was downloaded to the system as its possible they are two different things.
Also, for SP1 CU3, the boot images are based on Win 8 so make sure that you are using Win 8 compatible drivers in the boot image itself.
Jason | http://blog.configmgrftw.com

Similar Messages

Satellite A60-174: system32\drivers\isapnp.sys error

Hello
after many nights and using the recovery CD nd trying everything my Satellite A60 do not want to work. Even after I cleaned and formt everything new.
I got this error: system32\drivers\isapnp.sys
I installed the HDD in another laptop and works fine. If I bring the HDD back to to the Satellite A60 I still get this error.
OR the Toshi stays at Debugger DLL when I try to install another version of win XP Pro.
I think the RAM or something in the motherboard is broken. Can I change the Motherboard RAM?
Would it help if I add some ram in the extra RAM slot?
(I use only the stock ram as it is on the motherboard.
anyother idea what this system32\drivers\isapnp.sys can be.
It says to start the laptop with the original Win XP cd and try with an R.
Well this dos NOT work in this laptop.
I can not come to the WinXP screen. The laptop will break the instalation before that!
Konstantin

Hi
It seems youre right. Have investigated a little bit and it seems that this notebook was delivered with a 256MB internal memory.
I dont think that you will be able to remove the memory or to solve this issue yourself.
I really recommend contacting the Toshiba service partner. The guys have more experience with such reparation procedures.
If you will open the notebook and will try to remove something so I think its possible that you will damage something more on the motherboard.

After Deploying an Image: Windows Boot Manager - Missing ACPI.sys

Hi,
I am currently working on deploying a Windows 7 Pro x64 image to a number of clients over our network using FOG. We used KVM in Ubuntu to build the base image. The image has a small virtual disk for the Windows installation and is deployed to clients with larger
drives. Prior to capture the image, we ran sysprep /generalize /shutdown /oobe /unattend:unattend.xml, then boot the VM to the FOG client and let FOG save off the disk image. We then deploy the image to clients over FOG.
FOG successfully copies the image over, then reboots the PC. The computer attempts to boot from the local hard drive, then fails at the Windows Boot Manager screen, saying:
Windows boot manager
Windows failed to start. A recent hardware or software change might be the cause....
File: \Windows\system32\drivers\ACPI.sys
Status: 0xc0000098
Info: Windows failed to load because a critical system driver is missing or corrupt.
I've updated the client's BIOS, tried a different hard drive, used ATA secure erase to wipe the drive before formatting, and still encounter this same issue with certain client computers. Are there any other steps I can take to resolve this issue?
What files in Panther should I look at (or post) to troubleshoot? I don't see anything too obvious in diagerr, and sestuperr.log is just about empty.

We're using two models of 120GB SSDs, and deploying to 5 different motherboards (4 Intel models + 1 MSI model). The issue is most common with the DH55TC Intel boards.
We're using FOG due to budget limits--otherwise, WDT definitely would have been considered.

Windows 8.0 error 0xc0000185+ \WINDOWS\System32\drivers\mountmgr.sys

So basicly what hapenned I was skypeing with some friends and suddenly my skype froze as it happened very often i pressed the CTRL+ALT+Del button to end skype
But suddenly a message popped up in the left bottom corner of my screen it says windows is not working
I was wondered why it would give me a message like this while i still could play a game at the same time => minecraft
i got the following reports shown at a bluescreen
error: error 0xc0000185
File: \WINDOWS\System32\drivers\mountmgr.sys
There also was an option to press F8 wich would lead me to another vluescreen that gave me different option i tried all of them and it kept showing me this error
I do not have any windows 8 install disc since it was preset on my computer and i don't know what to do if anyone can help me please reply to this and thank you for your time

This is clearly an issue with the drivers in your boot image. Yes, for boot image driver issues you must update the boot image and ensure it's been updated on the DPs for it to be effective.
It happens before you get a change to select a TS because its an issue with the boot image itself which must fully load for anything task sequence wise to actually happen.
When testing boot image image issues, always make sure that you know which boot image you are updating and which one was downloaded to the system as its possible they are two different things.
Also, for SP1 CU3, the boot images are based on Win 8 so make sure that you are using Win 8 compatible drivers in the boot image itself.
Jason | http://blog.configmgrftw.com

Windows Boot Manager - Unable to start windows

I think my system crashed--this is what the screen says at start
WINDOWS FAILED TO START. A RECENT HARDWARE OR SOFTWARE CHANGE MIGHT BE THE CAUSE. TO FIX PROBLEM:
1.INSERT WINDOWS INSTALLATION DISC
2.CHOOSE LANGUAGE AND "NEXT"
3.CLICK "REPAIR COMPUTER"
IF YOU DO NOT HAVE THIS DISC, CONTACT YOUR SYSTEM ADMINISTRATOR OR COMPUTER MANUFACTURER FOR ASSISTANCE.
WINDOWS FAILED TO START. A RECENT HARDWARE OR SOFTWARE CHANGE MIGHT BE THE CAUSE. TO FIX PROBLEM:
1.INSERT WINDOWS INSTALLATION DISC
2.CHOOSE LANGUAGE AND "NEXT"
3.CLICK "REPAIR COMPUTER"
IF YOU DO NOT HAVE THIS DISC, CONTACT YOUR SYSTEM ADMINISTRATOR OR COMPUTER MANUFACTURER FOR ASSISTANCE.
File: \Windows\System32\Drivers\PxHelp20.sys
Status: 0xc0000098
Info: Windows failed to load because a critical system driver is missing, or corrupt
Toshiba Satellite E105-S1402--Vista was installed
intel core2 duo cpu
P8400 @ 2.26GHz
I have Vista DVD--does not load
tried plugging external dvd laptop does not recognize
Please Help

Satellite E105-S1402
Turn the computer on and immediately press and hold the F8 key.
Can you reach the Advanced Boot Options menu?
-Jerry

Windows boot manager - satellite L305-S3892

Everytime I turn the computer on it reads Windows Boot Manager. Windows failed to start. file: \windows\system32\winload.exe status: 0xc000000f Info: The selected entry could not be loaded because the application is missing or corrupt. The disc won't work. Up until now I had no problem with it. How can I restore it back to factory settings?
I changed the BIOS to start boot from CD - I first chose to repair - once completed I rebooted but still will not boot up into windows - I then chose the restore option - it seemed like it was working but then I received an error and the restore aborted.

satellite L305-S3892
I don't find that anywhere.
How can I restore it back to factory settings?
If it is indeed among the Satellite L300 series, see the section Hard Disk Drive Recovery using the Recovery media, starting on p. 66 of the User's Guide.
Satellite L300 Series User’s Guide
-Jerry

Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager

TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)

henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation.

Windows boot manager boots almost fully into windows 8 before letting me select windows 7, at which point it reboots my computer

Hi,
I haven't used my slow HDD with windows 7 on it in a while, but today my SDD with windows 8 on it died. I have kept my old OS in a dual boot setup exactly for this rare possibility. I in fact successfully revived my SSD from windows 7.
During the restore procedure I had to boot into both OSes (7 and 8) several times before I managed to get 8 working. I tried a lot of things before one of them struck. (Is that how the phrase goes?
Me Hungary, no good speak English some times...) I am surprised to have found the following unexpected behavior of the new windows 8 branded boot loader:
The new windows boot manager boots almost fully into windows 8 before letting me select an OS.
If I select windows 7, it reboots my computer and loads windows 7, wasting a lot of time... on the windows 8 portion of the boot process, which is simply thrown away if I happen need windows 7 and not 8.
"This is highly inefficient!" — I almost exclaimed aloud... A boot manager should load just enough of itself so that a simple OS selection menu can be presented to the user with minimal keyboard interaction. Only when a selection is made should
it load an OS. I have no use for the new boot manager's mouse control support, and having it appear on the second screen in my dual screen setup is just plain scary. Use the main laptop monitor where the BIOS messages were displaying, and keep the secondary
off until the OS is done booting! By the time my secondary screen turns on, the boot selection menu disappears anyway.
Yes, I only noticed this problem now because I haven't booted into windows 7 for a long time. (300 MB worth of Windows updates were waiting for me indeed.) My boot selection menu timeout is set to 3 seconds instead of 30 so I don't have to pick windows 8
every time.
I am going to wait at least a week for the forum's input before I switch on my own to a faster, minimalist boot manager. I don't know what to use, I'm familiar with:
some minimalist bootstrap loaders
coreboot/linuxbios (recently learned of it)
bootcamp (not really)
acronis OS selector (discontinued before windows 8 came out, probably doesn't support it)
syslinux/isolinux (Linux only, I think)
old Windows bootmgr
more recent Windows ntldr
then this new "inefficient for dual booting" Windows 8 boot manager
and finally grub
Grub feels like the best option as it keeps the windows boot manager intact and supports mac, windows, and linux. All 3 of which will at one point — or has already — come up as a subject or prerequisite in my university.
I don't know how or why I was able to access windows 8's boot loader while my SSD was dead. Was it installed on the HDD, overwriting the windows 7 boot loader? That too is inefficient. I want to completely boot from my SSD. Don't spin up my HDD while I'm
booting my laptop on the go! The shaking of the vehicle I'm in could seriously damage the disk if I run into a pothole (common in my country) with just the right timing, data could be damaged. The entire reason windows 8 is on an SSD is so that it can boot
without accessing my HDD with all its moving parts. My goal with buying an SSD was for the HDD to remain safely offline while I'm in a shaky environment with potholes! Also, what if I want to disconnect the old HDD in the future... Or what if it dies? Will
the windows 8 boot loader die with windows 7? I want the two kept separately and completely independent from each other for exactly this reason.
In summary:
How can I stop windows 8 from almost fully booting before offering the dual boot OS selection menu? Do I need a better Boot loader?
Why was the boot loader that came with windows 8 still working OK while the SSD with windows 8 on it wasn't accessible? Did it sneak its way onto the old HDD? I want a 100% SSD-based boot process. What is the boot loader doing on a different drive? Its
place is on the SSD, with the operating system it belongs to. Not on the HDD of a different OS. Can I move it?
Sincerely,
Daniel "3ICE" Berezvai
p.s.: For windows 7 I only have a repair disk and hidden RECOVERY partition which I kept (came with the laptop, would rather not use it.) The Windows 8 pro DVD (purchased last year) is fine, but I had it moved to a bootable pendrive so I could remove my
optical drive and replace it with an SSD on which windows 8 is installed now. (I also have a vista ultimate DVD, as they were giving them away for free on a Microsoft conference. Funny story.)
p.p.s.: I am subscribed (☑ Alert me) to this topic and will respond to all questions and try all recommended actions right away.
http://3ice.hu/

Hi,
Thank you for your post.
From your description, I see the issue you are facing is there is no menu to choose OS when booting dual boot(Windows 7 & Windows 8). Please let me know if I have misunderstood anything.
It seems that the Windows 7 entry is missing, currently, we can use a tool –
EasyBCD to get it back. After downloading it, choose the Add/Edit panel item, select the OS you're missing and let the program detect it. Then simply click the Add button to add the missing OS entry.
At the meantime, here is a related link which demonstrates how to keep Windows 7 as the default OS in dual boot, you may use it for a reference.
How to Dual-Boot Windows 8 While Keeping Windows 7 As Your Default OS
http://blog.laptopmag.com/how-to-dual-boot-windows-8-while-keeping-windows-7-as-your-default-os
[Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy
of this information.]
Regarding your second questions in your first post, you can refer to the following link to know more about dual boot.
Dual
Booting Explained: How You Can Have Multiple Operating Systems on Your Computer
http://www.howtogeek.com/187789/dual-booting-explained-how-you-can-have-multiple-operating-systems-on-your-computer/
[Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy
of this information.]
Hopefully the information is helpful. Please let me know if you have any questions. Thanks for your time.
Best Regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Windows Boot Manager

Hello all Support Team,
i Have some problem want to know reason and fix it, please help me.
i'm used the HP ProBook 440 G1. My problem is :
1.When i install OS win7 by disc from Microsoft, after first install complete it's reboot and black screen appear with one option to chose is " Windows 7 install [EMS Enable]". I provisional accept the solution from my friend but i still want to know what reason of this issue.
If choose that without remove disc, the laptop will restart and progress installed windows start again from beginning.
If choose that with remove disc, the laptop start to windows normal and everything maybe is fine ( this is my friend's solution).
2.When I reboot this laptop, the screen "Windows boot manager" appear, even only one option to chose is Window 7, then I check in "Boots" by open msconfig, I see only one OS and it's already default OS. But every time I restart the laptop the screen "Windows Boot Manager" always appear, how can i remove this screen and take my laptop enter directly to window ?
That's all my ploblem, please help me fix it.
Thanks and Best Regards,
Katori.

Remove the disk unless you want to install Windows.
"When I reboot this laptop, the screen "Windows boot manager" appear, even only one option to chose is Window 7, then I check in "Boots" by open msconfig, I see only one OS and it's already default OS. But every time I restart the laptop the screen "Windows Boot Manager" always appear, how can i remove this screen and take my laptop enter directly to window ?"
If you remove the password you are using, then the notebook will boot right into the operating system. That is not a good practice as there is no security at all.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Finding the explanation of all entries of the Windows Boot Manager and Windows Boot Loader sections

Hi
Where can I find the explanation of all entries of the Windows Boot Manager and Windows Boot Loader sections that appear when I write the /store /v options of bcdedit command?
Thanks
Bye
Balubeto

All the BCEDIT command line options are described here:
https://technet.microsoft.com/en-us/library/cc709667%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Jerry
Actually, I wanted to find the explanation of all entries (as inherit or
device or osdevice) of the Windows Boot Manager and Windows Boot Loader sections
that appear when I write the /store /v options of bcdedit command?
Thanks
Bye
Balubeto

After restore windows boot manager says windows failed to start. CQ57 notebook

Had a problem with the FBI scareware. Took it to a cmputer repair place. They wanted $250 to fix it and now it won't boot up at all. It did the HP system restore but when it rebooted the Windows Boot Manager says "Windows failed to start". It wants an installation disc. THen :
File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configuration data.
Is it trying to boot from the wrong partition?

Enter BIOS setup by tapping/holding the F10 key immediately after powering on the laptop.Use Diagnostics to test your hdd.
If you haven't burned a Recovery Disk set, phone HP to order one.Usually around $17. Choose your country here>> Contact HP
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

The \System Root\System32\drivers\NatMotion.sys device could not locate the entry point IoSetDeviceInterfaceState in driver ntoskernal.exe

After installing version 5.1.1 of the Flexmotion driver, and installing f5 update, I got the following message after rebooting the system: The \System Root\System32\drivers\NatMotion.sys device could not locate the entry point IoSetDeviceInterfaceState in driver ntoskernal.exe. OS is Win NT. I see device in MAX , but can not initialise it, and cannot make firmware update.
I do not se device from NT system menager.

The instructions on the f5 update are not 100% explicit about what to do for NT. The NatMotion.sys file should not be replaced on NT systems, only on the specifically listed OSes. Uninstall and reinstall the 5.1.1 driver along with the f5 update, however only install the components that do not specifically mention a particular OS.
Regards,
Brent R.
Applications Engineer
National Instruments

My laptop have refused to start it will just show windows boot manager on the screen,

My laptop have refused to start up, it will just show windows boot manager on the screen,and me to choose an operating system to start or press tab to select a tool but when I tryed all those things none of it will respond

Thanks also Star 1. I have gone the route you suggest also but with the same results as I explained to the hatter. I have about a dozen die-hard Windows friends and they have been trying to help me also. We have tried everything and I have read a several pages on how to do it but nothing looks like what they are saying it does. When in Vista, Vista says it is the default SU OS. When in XP, XP says it is the default SU OS. So there is nothing to change. Only the Windows Boot Manager (which is really not a manager but a boot selector) shows Vista as default and XP next. I've learned again what I already knew. Windows is a conglomerated piece of crap that is hard as heck to use.

[HELP] A300 Desktop Stuck at Windows Boot Manager Page

Hi Community,
I was trying to restore my desktop back to its orginal factory settings but through the process, it encountered an error and the system restarted. When the desktop is back on, the only page it offered was the 'Windows Boot Manager' page (As seen in the picture below). It says to insert the Windows Installation disc which not only do i not have, but also the A300 desktop does not have a disc/disk drive for me to insert any disc.
I have googled for any solutions but all of them require me to insert the disc which i clearly have no ways to do so.
How am i suppose to proceed from here to get my desktop working again?
Thank you in advance for any kind responses.

Hi lyl
The hard disk MBR seems to be corrupted
Kindly boot the desktop into BIOS by pressing F1 key and then press F9 to load default settings and after this press F10 to save and exit.
Check if the system works or recovery from hard disk runs, to run the recovery after the system power on press F2 key and check if the recovery works fine.
If the issue continues then you may need to contact the support center.
Country or Region
Language
Telephone number
Hours of operation
Supported products
Singapore
English, Mandarin
18008185219
9 am - 6 pm Monday - Friday
9 am - 3 pm Saturday
IDEA Products
Best Regards,
Tanuj
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Cant get past "Windows Boot Manager"

The following message appeared after restarting my computer (Toshiba Equium A200 1V0) from a window vista update
Windows failed to start. A recent hardwre or software change might be the cause.
To fix the problem.
1. Insert your windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next".
3. Click "Repair your computer"
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \Boot\BCD
Status: 0xc000014
Info: An error occurred while trying to read the windows boot configuration data
Now my problem is that I cant even change anytthing for my computer to boot from CD - I do not have a windows disc but have the Toshiba product recover disc but nothing at all works. Ive tried pressing F12, F2, F8, DEL .. actually pretty much every key just in hopes it will work.
Anyone else got any ideas on what I can do. Im pretty much resigned to the fact that Im going to lose everything I just need the computer up and running again as soon as I can.
Many thanks

Until one of the experts can give you advice about repairing your Vista system, you might like to try to recover your files. I'm not very computer literate, but managed to achieve this when I "murdered" my Windows 2000 installation. I ASSUME the same process should work with Vista. (Slightly worryingly, Windows passwords don't seem to matter.)
Download a Linux live CD - I found "Puppy" Linux a good one - small download, and easy to use. Burn the resultant .iso file to a CD. Insert the CD in your CD/DVD drive, and start the computer. Let it boot the Linux operating system. (You may need to experiment with BIOS settings to get the computer to boot from CD before its own hard drive.)
You now have a linux operating system running independently of your hard drive. (If it's one of the large Linux programs, it will be slow when run from a CD - not a problem - just requires patience!)
With a bit of luck, the Linux system will see any drives connected to your computer, including your hard drive. (The same as your normal operating system sees a USB stick and can copy files from it, for instance.) You might then be able to browse your hard drive files, and copy them to an external hard drive, or USB flash drive.
I did come across some matter of permissions to write to the external drive - sorry, can't remember the answer off-hand but it was very simple - and only had it once. Again, simply google the problem. There are lots of Linux experts posting threads out there!
This won't enable you to boot your Vista system or anything like that but, if you can get your files copied somewhere safe, then you can simply copy them back once you've reinstalled the offending Vista system.
I'll try to provide a link to an answer I previously suggested here - sorry it's a bit long-winded, but the link in it may be of use, too.
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=44736&tstart=30
One of those things which is easier to do than to describe, perhaps - lots on the internet about Linux rescue CDs.
I found a lot of useful articles on this google link:
http://www.google.co.uk/search?hl=en&q=using+a+linux+live+cd+to+rescue+win dows+files&btnG=Google+Search&meta=
I've never been good at entering search terms; you may well find better stuff.
But the good news is that it might be possible to recover at least some of your data before reinstalling.
If you've not used Linux live CDs before, do a bit of homework first. They're surprisingly easy, especially when you've overcome one or two of the usual initial pitfalls eg trying to burn the live CD as a data rather than an iso CD then wondering why it won't boot. Proabably easier for you to do a bit of googling than for me to write pages here!
Another alternative, if you're better at dismantling computers than me, would be to remove your hard-drive and install it in a suitable external hard-drive enclosure. This can then be connected to another computer via a USB port and you should be able to read your files as if from a USB flash drive, and copy them. I've only tried this with old drives from old desktops with nothing on them that matters too much - but it seemed easy enough. Again, just a way of copying all your stuff before wiping your laptop's hard drive and reinstalling Vista.
Sorry if this was a bit rambling - hope it gives you some ideas.

Windows Boot Manager Windiws\system32\drivers\rsteachci.sys error

Similar Messages

Maybe you are looking for