install error 0xc00000e9

Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

If you have external/usb based devices attached to the system, try removing those and start again. Vista might be trying to detect which is causing the error. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"abacus" wrote in message

Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

i get the same error, im thinking its my SD and SM card readers. but they are internal and it is a laptop so if that is what it is i cant take it out very easly so any sugestions would be apreceated.
"abacus" wrote:

Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

If you can't complete the install and want to send a bug report (means including necessary log files):
1. boot back to previous os, 2. change folder options to make hidden folders visible before the search. 3. search all partitions (may not be visible! * -> diskmgmt.msc -> assign drive letter) for .log files. The interesting log files are 4 to 30 MB in size, sometimes at vista partitions windows\inf directory if the setup went that far. Submit these logs to microsoft using Beta Client.
*If there was no vista partition in diskmgmt.msc* then the log files are most likely in the same drive your previous OS was installed (if it had space for the setup files). There should be a hidden, weird named folder, in root of the volume and the logs are somewhere under there (search).
"Mr. Anderson" wrote in message

i get the same error, im thinking its my SD and SM card readers. but they are internal and it is a laptop so if that is what it is i cant take it out very easly so any sugestions would be apreceated.
"abacus" wrote:
Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

I have the same problem and I tried your suggestions but it didn't help, is there any other advises
"droid" wrote:

If you can't complete the install and want to send a bug report (means including necessary log files):
1. boot back to previous os, 2. change folder options to make hidden folders visible before the search. 3. search all partitions (may not be visible! * -> diskmgmt.msc -> assign drive letter) for .log files. The interesting log files are 4 to 30 MB in size, sometimes at vista partitions windows\inf directory if the setup went that far. Submit these logs to microsoft using Beta Client.
*If there was no vista partition in diskmgmt.msc* then the log files are most likely in the same drive your previous OS was installed (if it had space for the setup files). There should be a hidden, weird named folder, in root of the volume and the logs are somewhere under there (search).
"Mr. Anderson" wrote in message i get the same error, im thinking its my SD and SM card readers. but they are internal and it is a laptop so if that is what it is i cant take it out very easly so any sugestions would be apreceated.
"abacus" wrote:
Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

If you have a laptop with internal device giving trouble, you can try disable them from BIOS but that is probably not going to help. Finding the right log files and submitting bug report just after it has happened is more likely to help in the long run.. If it's a desktop try disconnecting all hardware possible, USB devices too and disable all that you can from BIOS.
Here are revised log finding instructions:
Finding setup logs, reporting and attaching logs to report, figuring out what device or driver causes hangs or crash during setup:
1. google -> beta client (http://go.microsoft.com/fwlink/?LinkId=43655) The first link should be Microsoft link. It needs .NET but I think it will be installed if you try to run it without it..
2. finding and identifying the correct logs
setupapi.app.log setupapi.dev.log <<-- last 100 lines here may indicate the hanging driver
These are the primary setup logs, there are others but these are the major.
Hint: Before searching logs try Folder Options and enable viewing of hidden folders and files. Also try Run diskmgmt.msc -> assign drive letters for partitions with no drive letters.
A:
There can be multiple logs with the same name, but they are different! First look at the drive you tried to install Vista to, if it has Vista Windows\INF\ directory and the mentioned logs files.
B: early setup failure
If you can't find Windows VISTA directory (if setup did not get so far) then look all volumes/partitions in the drives that were on the machine during the install for directories starting with $. There are 2-4 of them (possibly in different partitions) depending on when the setup failed. Search for .log under all the *:\$WINDOWS
A & B:
Make sure the date and Minute timestamp of the log files are around the time when the setup failed, sometimes a setup/install failure causes the computer to automatically reboot and the setup will run again but failing in different way than the first time (making the bug report less useful). For best bug report it's better to catch the failure when it first happens. Yes it means starting the install all over again and keeping eye on it. But this will guarantee that the last line in the log will be around the time of the failure. If it is a driver crash then you can figure out the offending driver yourself just by looking at the last lines of setupapi.dev.log.
You wouldn't want to be looking at or submitting the wrong logs, right?

"game.freaks" wrote in message

I have the same problem and I tried your suggestions but it didn't help, is there any other advises
"droid" wrote:
If you can't complete the install and want to send a bug report (means including necessary log files):
1. boot back to previous os, 2. change folder options to make hidden folders visible before the search. 3. search all partitions (may not be visible! * -> diskmgmt.msc -> assign drive letter) for .log files. The interesting log files are 4 to 30 MB in size, sometimes at vista partitions windows\inf directory if the setup went that far. Submit these logs to microsoft using Beta Client.
*If there was no vista partition in diskmgmt.msc* then the log files are most likely in the same drive your previous OS was installed (if it had space for the setup files). There should be a hidden, weird named folder, in root of the volume and the logs are somewhere under there (search).
"Mr. Anderson" wrote in message i get the same error, im thinking its my SD and SM card readers. but they are internal and it is a laptop so if that is what it is i cant take it out very easly so any sugestions would be apreceated.
"abacus" wrote:
Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

I understand this error comes very early in the boot?
It would be best if you detailed every piece of hardware you have exactly. This can be done easiest by getting this program "PCI" or "PCI32"
http://members.datafast.net.au/~dft0802/downloads.htm
You also need to copy this file:
http://members.datafast.net.au/~dft0802/downloads/pcidevs.txt
To the same location as you have the PCI.exe or PCI32.exe. It has updated device definitions.
If you still have installer or can install XP on the computer, run the PCI32.exe like this: PCI32.exe > devices.txt
now open devices.txt with notepad and copy paste the content here in your reply.
If you don't have and can't get XP back there, get the DOS version on a disk or bootable USB stick that uses DOS. Then do PCI.EXE > devices.txt and open this file where you have Internet access.
You can also try enabling boot logging from the boot menu advanced options and this would yield a net*.log in root of that drive.
If possible, I also recommend installing the Beta Client on that computer and submitting a bug including the boot log if you got such made.
"Mr. Anderson" wrote in message

i get the same error, im thinking its my SD and SM card readers. but they are internal and it is a laptop so if that is what it is i cant take it out very easly so any sugestions would be apreceated.
"abacus" wrote:
Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

I understand this error comes very early in the boot?
It would be best if you detailed every piece of hardware you have exactly. This can be done easiest by getting this program "PCI" or "PCI32"
http://members.datafast.net.au/~dft0802/downloads.htm
You also need to copy this file:
http://members.datafast.net.au/~dft0802/downloads/pcidevs.txt
To the same location as you have the PCI.exe or PCI32.exe. It has updated device definitions.
If you still have installer or can install XP on the computer, run the PCI32.exe like this: PCI32.exe > devices.txt
now open devices.txt with notepad and copy paste the content here in your reply.
If you don't have and can't get XP back there, get the DOS version on a disk or bootable USB stick that uses DOS. Then do PCI.EXE > devices.txt and open this file where you have Internet access.
You can also try enabling boot logging from the boot menu advanced options and this would yield a net*.log in root of that drive.
If possible, I also recommend installing the Beta Client on that computer and submitting a bug including the boot log if you got such made.
"abacus" wrote in message

Windows Boot Manager - Windows did not start correctly...
Status: 0xc00000e9
Indo: Windows encountered a problem communicating with a device connected to your computer. This error can be caused by unplygging a removable storage device while the device is in use.
Error appears after "Windows is Loading Files" straight after booting from the DVD.

LO ÚNICO QUE TIENEN QUE HACER ES PONER SU UNIDAD LECTORA DE DVD's COMO MAESTRA EN EL IDE QUE ESTE CONECTADO.
-- ferguson ------------------------------------------------------------------------ ferguson's Profile: http://forums.techarena.in/member.php?userid=24591 View this thread: http://forums.techarena.in/showthread.php?t=527695
http://forums.techarena.in