piotrania

I've spent week to learn Vista booting and I've made many tests with various BCD configurations but without success. So now I've started to check other solutions of 0xc000000e problem. I tested below solution: It looks very interesting and ktp claimed "success" but I followed the instruction (btw it's not very precise) and results are negative. Before I'll present results of my tests in details I'd like to know if somebody except ktp can confirm the solution works and what are conditions. The solution was presented almost a year ago and I can't find a clear statement from other people that it is OK. I sent message to ktp asking for more details but I haven't got reply.

First of all I’d like to thank you for your guidance. I appreciate very much your knowledge and activeness. I’ve got some experience ( 25 years with various computers and softs) but “boot land” is fresh area for me. You motivated me to get more info about boot process (it is more complicated then I thought) in order to continue further investigations and tests. ( If I’m doing something I have to understand it). Booting Vista is different process from previous Windows so I started to learn BootMgr , BCD and so on. Usually I’m solving all problems by myself. It is my first time when I’ve asked for help in forum and I don’t know all writing rules. For example I’ve written DISK ERROR in capital letters to emphasize it but you have got it in different way. Of course the error appeared in screen in small letters, and in my language not in English. Comment regarding Chip VistaCE. I know newer VistaPE v.12 and previous versions. I’ve tested many images created by myself and others (Nightman) but I have to say that for me VistaCE is excellent tool (friendly interface, boot time 30-40 secs on average computer, immediate access to mass memories and internet) To improve it I’ve added some additional portable tools and applications in separate folder.

To be frank I do not understand you. I know that it's important to you so I put down an error in capital letters "DISK ERROR" ( see above) I see that you are proposing to go another way. As I said at the beginng I do not want to change method of booting. I want only to get explanation why I can not boot my dektop from my USB-VistaCE ( before I could). I boot another computers easily from my stick ( till now I've checked 20 computers and no failed try). Maybe some more information on my USB-VistaCE stick. It is simply created by formating USB stick using Diskpart and copying files from CD VistaCE ( this CD was attached to Chip Magazine last year) Structure of files is as follows: 1. Boot (folder) containing: BCD, BOOT.SDI, BOOTFIX.BIN, ETFSBOOT.COM 2. EFI (folder) >Microsoft (folder) >Boot (foder) containing BCD 3. Sources (folder) containing BOOT.WIM 4. BOOTMGR If you need I can send you CD image. To summarize: It was confirmed that error "0xc000000e" was not caused by Microdrive Drive Filter or Acronis Disk Director (I disconnected hard disk drives and the error appeared) Probably BIOS of my Desktop is causing "0xc000000e" error but why it was OK before it is mystery. I have not changed hardware or updated BIOS. I use default settings in BIOS.

I followed above instruction and in all cases (Samsung 3, 4, 5 test.dat) no boot at all on my desktop and other computers - DISK ERROR. I think the reason is formating in WindowsXP Explorer I've made additional tests . Stick was formatted with Diskpart and then using HDhacker I changed MBR from dat files (Samsung 3, 4, 5 test.dat). In all cases I could boot to other computers (except my Desktop). I also used mbrfix (fixmbr command) the result was the same.

I've played changing BIOS ( USB function ,Legacy USB support, USB 2.0 Controller, USB storage Device Emulation Mode , Plug and Play O/S) but no positive result. I've formatted by Diskpart two new sticks :Samsung Mighty 1GB and GoodDriveED 2GB and copied VistaCE. Result the same as before I can boot from both sticks many other computers except my desktop. MBR data files enclosed. Data2.rar

Sorry there is no failesafe option in my computer BIOS ( V. 2.51 American Megatrends) Please explain what you mean by properly. I have formated another USB Samsung Mightly stick using as before Partdisk and commands mentioned before. Then I copied files from my "original" USB-VistaCE. Result the same I can boot from this stick other computers except my desktop. As I have not istalled Vista in my computers so I use Diskpart under VistaCE (booted from CD). If stick is formated let say by Acronis it doesn't works at all (non system disk)

As suggested: 1. I dissabled hard disks in BIOS and tried to boot from USB-VistaCE. Result - the error. 2. I run MemTest+. Result no errors. Now I'm a little bit lost and can't find reason why before tests I could boot from USB-VistaCE on this computer. BTW what tool you can recommend for analyzing MBR data file.

Fully agree. Please take into account that I had no problems to boot from USB-VistaCE on my computer before USB stick tests with partitioning and I have no problem to boot from CD-VistaCE right now. I can run suggested tests but I think ( maybe I'm wrong) the problem is located in Registry entries made by Acronis. According to some information from net some Acronis drivers ( mainly) snapman.sys Registry entries can cause boot problems. It is remomended to remove some entries ( lowerfilters and upperfilters keys) I'm trying to get more information on it.

My USB stick (see my first post) was formated using Diskpart ( commands: select disk x; clean; create partition primary ;select partition 1; active; format fs=fat32; assign) My hard disks ( 2 pcs, 6 partitions) were formated using Acronis Director Suite 10. I used also Try&Decide function of Acronis True Immage 11 (part of disk is blocked) Additional info: I've sacrificed my new laptop and repeated all steps previously done and there is no error on my laptop. I've checked differences between my desktop and laptop. In my desktop there is additional disk drive- snapman.sys (installed during instalation of Acronis Director Suite or True Image) two others drives: Microsoft disk.sys and PartMgr.sys. Now I suppose we are close to solve the matter. Probably changes were made when I created partitons on my test-USB stick using Acronis DS. Some people reported problems with boot devices after using Acronis DS.

Thanks for detailed comment. Your summary is fully correct and I confirm my USB stick works perfectly on other computer. Nothing has happened to my computer. it has worked good before I started to test microdrive drive filter and now is also OK (except mentioned error) All happened in one evening in following order: 1. I showed my friend how my USB-VistaPE works on my computer (everything was OK) 2. I took another USB stick and wanted to create partitions so I installed drive filter. 3. I resigned from further tests with USB partitions so I reverted to Microsoft drives 4. I tried to use my USB-VistaPE on this computer but the error occured. One more thing. The reason of my post is to try understand what happened not to remove cause of the error without knowing what going on (let say by cleaning disk). I still can use my PC and I can boot VistaPE from CD.

Many thanks jaclaz for your kind post (as usual) You are expert but to be frank I do not understand presented approach. I have USB-VistaPE (discribed in my first post) which I've been using succsfully on many computers for long time. I didn't use this USB stick (Samsung Mightly) when I installed filter drive under Windows XP. I used similar but not the same USB stick testing partitions on USB stick. I used my USB-VistaPe on my PC before I started tests with multiboot USB stick and everyting was OK. After I finished tests with drive filter I could not boot from my original USB-VistaPE any longer. Maybe I'm wrong but the reason of the error is not my stick (all time the same) but PC (which behaviour is different after drive filter test). Of cource I can send requested files Data.rar

Yes I agree title of post should be "Problems after installing Microdrive Filter Drive" (if possible should be changed) but if somebody read the post I think he/she has no doubt that I'm writing about drive filter not Microdrive (storage device) especially when post was put in multiboot subforum. In my second post I put clearly "filter driver" The problem is closely connected with process of creating partitions on USB stick. Nevertheless I confirm that problem started immediately after I installed Microdrive Filter Drive. Would be obliged if somebody could answer question in my second post. I don't want to get instruction how improve my bootable pendrive (I dit it already) jaclaz dont be its better ,I read hundreds of your posts, always professional, kind with sense of humor and I do hope you could comment my problem not technical mistakes only.

Referring to my previous post I do hope that in this forum attended by so many experienced guys somebody give me a clue. In the meantime I checked hundreds other post here and on others forums. I’ve find that problem of error 0xc000000e was deeply discussed ( link )but there is no answer to my question: What changes in my computer have been made during installation of drive filter (Hitachi) and how remove these changes ? In mentioned post there are information how modify USB stick, using Grub4Dos to avoid the problem. Author (ktp) assuming that problem concern only some BIOS. In my case I’ve used the same computer (same BIOS) and problem appeared after installing drive filter. There is no Grub4Dos on my USB-VistaPE and as I mentioned before I have no problem to boot almost all PCs.

Problems after installing Hitachi Microdrive Disk Filter. Facts : My PC : 2 hard disks, 4 partitions, 2 OS (XP Sp3) I wanted to check multiboot from USB drive, so I installed Hitachi Microdrive drive filter. It was OK. USB Pendrive was seen as fixed disk. Then I decided to revert to previous standard Microsoft disk drivers for USB device. I did it with no problem using Device Manager. Now almost everything came back to previous state except one thing I can not boot any longer from my USB-VistaPE. When I’m trying to boot from my USB-VistaPE following message appears: "File: Boot\BCD Status:0xc000000e Info An error eccured while attempting to read the boot configuration data" Few words about my USB-VistaPE : it is Samsung Pedrive which was formatted using simply diskpart commands (select disk 1; clean; crate partition primary ;select partition 1; active; format fs=fat32; assign) and then files from CD VistaCE were copied on it. It works excellent. I can boot from it on almost all PCs. I successfully tested it on 12 various computers. It was OK for my computer too until I installed Hitachi Microdrive. I guess (I’am not sure) that during installation of Hitachi Microdrive drive filter some changes were made in MBR on my first hard disk. I have no enough knowledge about MBR to find which sector is responsible for it and how to change it back. Unfortunately I haven’t got copy of previous MBR and I don’t want to reinstall systems. Help appreciated