The hal. Users can try to copy the hal. Basically, there are 3 files related here: hal. The rule is that, if the computer is a multi-core PC, halmacpi. Else, for single core PC, halacpi.
Thus, depending on the number of CPU core of your processor, copy the corresponding file halacpi. Then, copy and replace both halacpi. Note that for hal. Type Exit to close the command window. Restart the computer. Windows Vista computer should be able to boot up properly now.
I have almost the same problem and I need help. I have two partitions on the same drive the one created by bitlocker preparation tool and when I try to repair from Vsta boot DVD, it finds the operating system on the wrong drive. I do not wnat to do a clean installation of Vista but rather revert to a previous stage. For those of you who have done this and the install still fails please do the following:. This file will then be scooped into the application event log under the wininit source, event id Many thanks,.
Carl D. Windows Beta Team. When a file is updated it is written to a new location on the disk. In my case it helps connecting the disk with the OS to another PC and defragmenting it there.
After WU downloaded my updates I unchecked the update to WU and hid it, then installed the rest of my updates. I do have UAC turned off too. All the advices here seem to be useless. I am also getting the same missing ntoskrnl. Except that I am also getting one more error;. To my surprive it went into the Volune System Information folder and rectify all the indexes in side the files pointers. After rebooting one more time and getting the above mention error, I tried to use the BCDedit.
So I decided to find out who own those files:. To my surprice those files are own by TrustedInstaller group and by System I was expecting. Well I was to give up and follow my own advice to run Knoppix and recover my files and them reinstall.
But to test one more theory I decided to try to fix the MBR and see if that works. In this case it is a sub article that I will test today and post if this actully fix my issue. Currently I only have one computer running Windows and it is for my school classes.
Bottum line is I am tired to pay for halfve way done products, Windows is taking many features from Linux in that case why stay with Windows when I can run Linux or Unix with less problems, worries, time waste and with less security issues.
I am doing a follow up to my previous post as I promise and here is more information:. I tried the resolution from and as spected it was totally useless. I also tried several other solutions and nothing. If any one knows where the logs are located please let me know.
After SP1's install; vista fails to boot and I'm getting missing or corrupt ntoskrnl. What the hell! I've tried everything from inside the repair disk including trying to system restore and chkdsk! I ran some other utilities in my pc plus, finally find the log which I think finally told me what is wrong with my pc. Here is the output of my log. Startup Repair diagnosis and repair log Number of repair attempts: 1.
Test Performed: Name: Disk failure diagnosis Result: Completed successfully. Repair action: Partition table repair Result: Failed.
Wikipedia has a nice small article that can help to place some light in this mess. If you are at some level computer techie then I will suggst to get a partition utility and try to rebuild the partition table. I will try the same some time today. They should of place the SP1 for Vista in a way that Windows update couldn't find it as a regular release.
Iam not sure what king of QA they have but, they really need leave too much to be desire. There are some utilities available to fixe the partition table. Most of them are commercials. I won't recommend a specifict utility as for personal experience defferenc users prefere deffirent utilities.
I haven't have the time to work on my but hopefully I will be doing it soon enought. As you I have over programs in my comp I don't feel like installing all of them. Again, if you wan stability move to Linux or Unix.
Alright guys, Here's what I did to boot my Windows up again and re-install SP1 Already confirmed working by other users :. You'll need to manually restore some files again to the version that came with your Windows installation DVD. Use the Windows DVD to boot into repair mode and restore these files using the command prompt:. Make sure to rename or backup the files you're going to replace just in case you do something wrong. HINT: If you're not too comfortable using the command prompt, you can use the notepad's file browser to copy and paste files from inside the repair DVD.
Just type "notepad. It's highly recommended to reinstall SP1 again because eventhough after you're going to boot, Windows will say that it's removing all SP1 files because the install failed, it actually doestn't replace most of the system files.
Your copy is going to be a hybrid between no SP and SP1. When you reinstall SP1, Stage 3 is going to be repeated twice, once before Stage 1 and then again after Stage 2. But that is completely normal. You should'nt need to restore any other files for you Windows to boot. I used the debug boot log file from inside my Windows folder ntbtlog.
Sorry about that. Also, I just remembered something; hal. You will likely see that hal. That's because it's exactly the same file just copied and renamed. Basicly if you have a multi-core PC you'll need to use halmacpi. The "winsxs" folder only has these two files and not hal. Now that I think about it, It's probably better if you replace both halacpi.
Koben Haven wrote: First, i missed msiasdrv. Second, in my boot DVD did not had a hal. I did all as you said, to back old files, and then replaced them with new from boot DVD. For hal. Then restarted Laptop, it did not boot, as hal. And also yes; hal. Thanks for this info, I may have to try it soon. My first SP1 install from Windows Update corrupted acpi.
After that went on all day and through about 4 reboots, I downloaded the full SP1 installer and ran it, and got bit with the ntoskrnl. After manually replacing all the files it complained about as I kept rebooting ntoskrnl. DLL, tcpip. No system restore point, and Microsoft Support tried to get the registry restored but that did not help. I'm waiting for another callback from support tomorrow I'm being elevated for the second time , but I'll keep this post in my back pocket in case they can't fix it.
If only the Vista DVD would let me install the OS again like XP would, but that process complains that in order to use the same product key that's already on the hard drive, I'd have to re-run install from within Windows, which of course I can't get to right now Did not work for me either. Still bluescreening on a normal reboot, still just rebooting after it hits crcdisk. I'm going to keep playing around with it to see if I can get it going again.
Guys, after having the same problem I rang microsoft and if you are thinking about doing the same. Dont bother they have no idea what is going on with this issue. I have surcome to the fact I am in data recovery, reformat and roll back to XP mode.
This is a shame as I have been a fan of Vista until now. I thought SPs where to enlighted the experience not crash it??? The same missing ntoskrnl. I got lucky though.
I haven't been brave enough to try another attempt at SP1 yet. I first want to back some more stuff up from my Vista partition. Fortunately almost all of my data is already on another partition shared by my XP multi-boots.
For some reason, not only did startup repair refuse to fix my problem completely useless if you ask me but it also managed to delete all my pre SP1 restore points and my partition shadow clones. For people who still have restore points created, don't do a system restore; try restoring your windows partitions' shadow copy to Pre SP1. It's the repair tool right under system restore called "Full System Restore" or something.
Running system restore will not prevent Windows from trying to continue the installation eventhough some of the files were restored. But if you restore the whole partition it'll probably forget the whole installation ever happened. Other than that follow the instructions I posted here earlier and hope for the best. And for those who get bluescreens at crcdisk.
I had the same bluescreen because I skipped restoring a couple of files from that list at first eventhough they didn't give me an error at boot. You must replace all SP1 files that load at boot, regardless of weather they give you an error or not.
Well, I followed it step-by-step, including double-checking which hal. I replaced them all. I had this problem too. The patch would appear to install, even display the "successful" message, but when the computer rebooted the ntoskrnl. The only way back for me was to insert my Vista DVD and choose to repair. Back to square one. My problem seemed to be rooted in Bit Defender antivirus version 10 still.
I uninstalled it, which was harder than I thought it would be because even though it was no longer installed, Vista still used 2 components of it as the firewall and a virus screen.
These had to be stopped too as they prevented the SP1 installation. The way I did it was not to go into SafeMode but to have Windows Defender show me which BitDefender files were still running and then fire up Task Manager to stop them.
Once BitDefender was gone I used a download of the SP1 to install for about the 8th time and this time it worked. The computer rebooted, took 30 mins to install the 3 stages and now has the SP1 installed and working. Also, BitDefender has been upgraded to , which they kindly offer for free.
So, thank you for all of your knowledge on how to fix their problem. It still however does not work for me. The system will still not boot up with the boot disc 32 bit , hence I do not have access to the files I need to replace. Do you know of any other way to boot to repair mode? Any help would be great. Thanks again.
Wow again, thank God for people like you. I will try this tonight, I had just about given up and was going to re-format tonight. I have the same problem with that missing file ntoskrnl. But I heard from someone that may exist a hidden partition where is a Windows copy. Does anyone know how can I acces that partition without a CD to repair my notebook?
Or where could find that kind of CD? They can help with restoring the system. We had a small batch of these reported in March and early April when the Vista SP1 was first released, but have had almost no support calls on this issue since then, so the suspicion is that it's something unique to enthusiasts who are likely to be the first ones to install the SP directly from the WU sites.
Please click on this link and open up a case with our product support services teams:. Thank you for taking the time and we look forward to hearing from you. If you have a problem accessing the above link, please:. First of all, going to the "no-fee" support is a complete waste of time.
When I first had this issue they were of no help at all. I'm not saying that they didn't want to help, I'm saying that they were NOT able to help. All their suggested solutions were useless because they had no clue what so ever about what caused the issue. Also, the guy handling my issue kept telling me to hold on for a minute while he looks for a possible solution, then all of a sudden the support session would end and I would be kicked out.
So much for support. Secondly, So far I've not found any other working solutions except for the ones found in this thread and the other one I started. So you're definatly going to need a Windows Vista installation DVD to go through with the repair steps. It doesn't have to be the one you used for the install, any installation DVD will do because you're just going to use the repair tools.
So anyone missing their own DVD can borrow one from a friend or something. I didn't have a dual boot configuration when my PC failed to boot. The problem is due to a faulty install process due to a crappy SP1 installer. MS can deny that all they want, but there was nothing wrong with my system before installing SP1. Sorry to disillusion you, but you have a problem with SP1. Mine was an install done with automatic updates. Then low and behold, after all the trouble of doing the fresh install, installing all the drivers an automatic update of SP1 killed the PC again.
I am once again spending an evening restoring the Operating System instead of spending time with my family. My PC just did that about an hour ago. I had to system restore which removed the service pack which the first time around installed perfectly.
Just now however at some point between steps 2 and 3, the computer restarted. The screen loaded black with white lettering rushing across the screen. I'm assuming it was the loading files. The error that came up wasn't like yours though. Mine was something like 0xca or something near to that effect. I had to do another system restore to get my computer back to at least get On. I'm half afraid to log off it now. I have just finished upgrading Vista to SP1 on my brother's Dell desktop. It took me almost a month.
If this had been my OWN machine, where I would have been intimately familiar with all the programs, the important data, the configuration tweaks, etc. Although I am late to this particular party it seems from all the forums on the net that many people have had similar frustrations with SP1.
Since I would not have been able to complete my goal of preserving my brother's "stuff" without all the helpful postings from the other victims, I felt that it was my duty to give back and post my experience with the hope that I may help someone else.
Note that I had considered upgrading my brother to Windows 7, but you can't do that unless the installed Vista OS is at least at the SP1 level - Catch22? I did find it quite interesting that Microsoft is still providing free support for people with SP installation problems and I spent several hours on the phone with them. Based on my experiences and what I could glean from other postings, I would suggest the following pre-requisites if you are just starting out on the SP1 upgrade path as it MAY make your life easier:.
Download the standalone SP1 exe rather than using Windows update. You can Enable All again after SP1 is installed. If Roxio products came pre-installed on your machine and they are quite popular for that role , perform a full uninstall. This may not be as easy as it sounds, but more on that later. Download and run the pre-install package from Microsoft KB and run it just before you start the SP1 exe.
It didn't help me, but it doesn't seem to hurt the effort. Get your hands on a re-installation disk for your version of Vista. There are "Vista Recovery" disks which you can download if you do a bit of research I believe Microsoft has one available but I would suggest that your original disk is the best bet. If you didn't get one with your machine, there may be an option to burn one or order one cheaply from your computer manufacturer. You could also borrow one from someone else; the disk itself has no real commercial value - it's your license key that is valuable.
I'm in IT and one of duties used to be part-time pc support, so I'm not completely a civilian. These last 2 items came in handy as a way to access all the files on the Windows drive without actually running the host Windows. I initiated the SP1 upgrade process dozens of times and failed every time - sometimes doing damage - until the last one the last place that you look, etc.
I spent hours researching on the Net and trying any number of different solutions which were offered. I made a mess of the installed Windows and spent days just trying to get back to a point where I could start working again. The two most helpful threads which I found on the net were both under social. Along my journey, these were the "solutions" which worked for me note that SOMETIMES,the automatic repair option on the re-installation disk can actually FIX your problems, so try that first but prepare to be disappointed or to find yourself back at square one :.
When the patch is ready for a re-boot, do it manually and hold F8 as Windows is loading so that you can select Safe Boot. Babysit the future re-boots to keep using Safe Boot. Problem: By trying all the different and novel solutions to get ALL the upgrade stages to work, you damage the boot sector. Solution: You will find other possible solutions for the "ntoskrnl" issue if you do some research on the forums using the Automatic Repair option on your Vista re-install disk, copying in a fresh version of ntoskrnl and some other files and it may work for you.
If your Vista bootloader is toast, there is an excellent set of manual re-build instructions posted by the good people at Neosmart. Go to neosmart. I used Option Three: Nuclear Holocaust. During my long journey to finish the upgrade, I ran these manual instructions at least 10 times: sometimes because I knew that the bootloader was corrupt, sometimes as a precaution and sometimes out of sheer desperation.
Kudos to Neosmart for making this available and bullet-proof. If their software is as good as these instructions, it is worth a look if you are into multi-boots. Pre-requisite: you will need a copy of bootsect. Apparently, Microsoft has been a bit inconsistent about including this utility on the re-install DVD's.
SYS file is missing or corrupt. You then need to copy in the pre-SP1 versions to the same sub-directory. Problem: You get an error message that HAL. DLL is missing or corrupt, but you cannot find a fresh copy. Solution: There are two similarly-named files and one of them is actually the same code as HAL.
SYS is loading. The worst-case scenario is when the Startup Repair function cannot automatically repair your system AND none of your Restore points are working. Solution: As you might discover from other posts, the CRCDISK message is misleading because Windows keeps loading other drivers after this point, but it doesn't report those subsequent drivers to you.
Consequently, you will find a number of solutions in other posts. This will not be an immediate fix because your machine will still not boot from the C: drive, but when you run Startup Repair again from your re-installation disk, Windows will miraculously be able to find a working restore point and you can start the process all over again. This no-boot, no-restore situation cost me days and I almost gave up, but when the Microsoft first-line support person told me that my files were so corrupted that I would have to re-format, I went back to the forums and found this solution.
Problem: You can't get to Stage 3 or it will not complete. The first time that I saw this happen, I was stunned: more than 3 weeks of work to get to that point and then SP1 throws everything back in your face with no warning and no explanation!
What The Frack? Solution: Warning - very radical. As soon as I saw the message "Reverting", I held the power button down to shut off the machine. Most machines make you hold the button for 3 seconds before actually shutting down. I re-booted with the re-installation disk; selected the repair option; cancelled the auto-repair; opened the command prompt and re-built the bootloader using the manual instructions from our friends at Neosmart.
When I tried to re-boot from the C: drive, I got the blue screen of death from the normal boot, but the Safe boot option was now working AND showed that I was running Vista SP1; however, everytime that Safe boot was closing down it indicated that the system was "configuring updates". Solution: At this point in my journey, Microsoft Support had assigned a senior analyst to help me. He actually was quite helpful in the trouble-shooting. When you go into Safe mode the first time after getting the Blue screen of death from a normal boot, Vista will point out to you the existence of a mini-dump file which can be used to trouble-shoot the memory conflict.
I can't read these dump files myself, so I provided them to the Microsoft analyst. In my case, the dump file seemed to point to a file called CDD. The analyst decided to experiment with my computer and had me rename this file.
DLL is an important Windows file which is used to help drive your display. Without the use of this file, my display went totally black as soon as I booted into normal mode. Needless to say, I had to restore the original name of this file. A bit of research on the Net revealed that CDD. EXE when it appears on the Programs list; select Run as administrator.
The SFC process refused to run because there was a "pending repair" - this was, apparently, the Reversion control file that kept "configuring updates" in Safe Mode. Sure enough, the file existed and was rather large I assume with all the steps necessary to remove SP1. I was told to delete it but Vista wouldn't allow me to until I had sufficient rights Right-click on the file; select properties; use the security tab to change the Owner to "Everyone" and then grant full rights to "Everyone".
SFC fixed my file version issues and I was able to boot in Normal mode. Only one error came up in Normal mode: it was from a Roxio driver. Hence my suspicion - with no hard proof whatsoever - that it was Roxio which may have been the root of my difficulties all along.
After I was finally able to completely uninstall Roxio, I installed SP2 with absolutely no difficulties whatsoever. When I did a re-install of Roxio after creating a restore point with SP2, one of the bundled utilities would not install because it recognized that it was not compatible with Vista. Problem: Cannot uninstall Roxio. Be forewarned: this procedure is not for the faint of heart and will be difficult to accomplish if your Roxio was pre-installed by the computer manufacturer.
There are multiple Roxio programs which will show up in Programs and Features and will have to be uninstalled one-by-one. Note that, even after I followed all the steps in the "Complete Uninstall", I still found two orphan lines in the Registry which I had to remove. Good luck to all you hackers and I hope that this journey will save you some late nights - note that I cannot claim to be the originator of most of the solutions detailed above, so I would like to thank the on-line community in general for their generous postings.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English.
Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Trying to do a System restore doesn't work either as there are no restore points existing even though I created a restore point and then the RC1 update created one before the install. I now have a dead machine and would like any advice on restoring my PC back to some normality. Cheers Gav. Friday, December 28, AM. I had the same problem and it is to do with the indexing of the file.
To fix: Boot to a command prompt select from F8 menu or use a boot disk I used the vista install disk then selected Fix my computer then command prompt. Wednesday, January 2, AM. Some Extra info: I have Vista on 2 different hdds I never bothered with having boot manager setup to handle both OS' because it was just as easy to make the selection via bios boot drive options Sata hdd: is the main auto boot option IDE hdd: redundant OS not used for months, accessible via bios boot-time drive selection options I installed RC1 while in the SATA vista but somehow the update has recognised the IDE vista and updated it's bootmgr and clobbered the SATA bootmgr.
Is there any information that can help me?? Saturday, December 29, PM. I do not wnat to do a clean installation of Vista but rather revert to a previous stage Cheers, Vassilis. Sunday, December 30, AM. I even cannot get the dvd to boot. Just after loading the drivers all i get is the sam error you do. I used to be able to get the plain vista ok - by disabling the AHCI modus in the bios on the sata-drives.
But this doesn't help anymore. Vista bit runs better, even installs fine, but gets sometimes realy slow. I know it's only a pre-release, but i do hope microsoft will be able to fix this AMD chipset issue before SP1 gets out! I could even upgrade to SP1 RC1 without problems at all. But not install with the RC1 bits version. The bit version is also not stable enough If somebody could explain to me what may cause this error - i might be able to get a little further I even upgraded the firmware to the latest rev.
Sunday, December 30, PM. I'm surprised I haven't had a response yet on how to fix this. I would have thought the title of "dead pc" would have caught some attention from microsoft.
Especially as the RC1 has modified the bootmgr on the wrong drive. I'm sure there are heaps of people out there with OSs on different drives. It's been too long now without a solution and I will have to use my last resort to just blow away the current installation and re-install vista on the sata drive. What's the point testing betas or RCs if we don't get a response to fix their bugs Gav. Monday, December 31, PM.
Tuesday, January 1, AM. Thanks for your suggestion. I couldn't wait any longer and have already re-installed Vista. I hope your suggestion helps others and as it is the first and only constructive answer I've received I'll just mark it as the correct answer.
I might try it on my old vista on IDE drive Has anyone done any testing to see if gigabit networking has been fixed in sp1?? Thursday, January 3, PM. My machine is still dead as of this point and I'd love to get it going again. Since Safe Mode is not an option what can I do to get my machine going again without losing data?
Wednesday, January 9, AM. Thursday, January 10, AM. Well, what happened with me was, SP 1 wouldn't install. It did it everytime I tried to install it. I'd deleted the files from Software Distro like others have posted here suggested,and tried again, and nothing would happen. So I gave up. Then when a bunch of new updates showed up on the 8th, I installed them. Low and behold the SP started to install.
When the computer restarted that's when I lost my OS with the missing ntoskrnl. I ran the Vista repair and of course it can't find anything wrong, but won't boot up. I did email on of the techs on here and he tells me there's nothing that would fix that untill the next build.
Which does me no good. What I need to know is, is there a way to do a command prompt uninstall of the last updates from the command prompt window off the OS DVD.
0コメント