Manifest Parse Error…
You receive the following message: “Manifest Parse error: Invalid at top level of document” when installing Windows XP for the first time and the installation fails because it cannot correctly parse the CONTROLS.MAN file. At no point does Microsoft’s installation program allow you to select an alternate source location for the file. It doesn’t even allow you full command prompt access. And the Recovery Program is useless, as it doesn’t even allow you to copy directories or copy using wildcards!
That’s what happened to me, too, after I decided to give Microsoft one more chance to have one of its operating systems on my main computer. I must be a glutton for punishment, because rather than scrapping it completely, I decided to figure out how to get around the problem. Old habits, like most computers running Microsoft operating systems, die hard.
I’ve heard everything from “it’s a copy protection scheme” to “it locks you out after three installations”. I’ve even heard of hundreds of people who have experienced the error from fresh-out-of-the-shrink-wrap, boxed versions of Windows XP. I couldn’t even get my freshly opened XP CD direct from Dell to work properly. Also, many folks prefer to install from CD copies and keep the original disks in close-to-pristine condition, yet rumors abound that as many as 60-70% of the copies experience this same problem. It must be another one of those undocumented Microsoft features.
The /i386/asms/6000/msft/windows/common/controls/controls.man file on the CD is corrupt. Copy your entire CD to your harddrive, use my version of the CONTROLS.MAN file (don’t forget to change the file extension!), and burn another CD. In theory, you could copy the entire i386 directory to your harddrive, replace the damaged file, and then run \i386\winnt.exe to install, but if you really want a reliable and stable system, it is not wise to install the XP operating system over an existing, older OS. So burning a CD is the only viable option for a fresh, clean install.Whether the new OS works well enough to dissuade me from breaking down and purchasing an iMac remains to be seen…
Seems to be a CDROM issue too. I have one that didn’t work on one DVD drive, but did work when I replaced the DVD with an old CDROM drive I had. Go figure.
Interesting thought! My installation was on a Dell Dimension 8100 with a stock DVD. Maybe you’re on to something… - RDL
Actually, I had the exact same parse error, but with a different file:
i386\asms\6000\msft\vctrl\vctrl.man
I think I might give another CD-Drive a go. Bah! And I had to reinstall Windows-ME just to find out what’s gone wrong.
I had the same problem with the ISO CD Image that I downloaded from Microsoft’s MSDN Download’s Site. On that site, Microsoft claims the image is meant to be burned to CD. Upon mounting the image with Daemon Tools (CD-ROM drive emulator), I checked the file’s contents and they looked good. (So the download, at least, is viable.)
After performing a CD copy from the mounted virtual CD to CD-R (Plextor Hi-Speed Media) using Adaptec CD Copier (Platinum 5.1), I checked the contents of the copied file on the CD-R with Notepad and it appeared empty. I forgot to check the file size before I threw the disk away so I’m not sure if it was actually empry or just corrupt.
I re-performed the copy from the mounted virtual CD to CD-R (lower speed generic media) using CloneCD (4.0.1.10). I again checked the new copy’s file contents. This time the file looked good. The disk was usable.
One theory is that this is some sort of copy protection (the correct information is stored in the sub-channel of the CD image, or something) that Adaptec can’t or won’t override. CloneCD, better for making true bit by bit copies of any disk, seems to accomodate the problem.
I didn’t do any further testing to prove this theory. Just a thought for people trying to get around this problem.
I had this same problem. I tried everything mentioned above, and still no luck. I formatted my harddrive at least 6 times, started a new installation still nothing. I copied all of the setup files to my hard drive, and made a new controls.man file and then ran the setup. Even after all of that, still, I got the same error. After two days of dealing with this problem, I finally gave up (I’ve worked on it 20 hours in the past 48), and installed win 2k pro. If anyone can provide anymore info on this problem, and/or a working link to a cd image of a PERFECT working copy of the Windows XP cd, I (along with everyone else I am sure) will greatly appreciate it.
You guys are funny. It’s just copy protection. Copy XP to HDD, replace controls.man with a good copy from working XP CD and burn.
Maybe so, but I don’t usually buy two copies of the software I’m trying to install, perhaps naively expecting the single copy I buy to actually work as designed. Remember, my OEM original CD purchased separately from Dell experienced the problem originally. - RDL
“Reggi”, I have already done what you have said…and I had no luck. On a few of the copies, the controls.man file became corrupt?! I’m wondering wtf is with that.
Justin you need a working copy of controls.man. I can give it to you, or you can download it, or make your own. You might want to check all the *.man files before you burn to make sure they are not corrupt or empty.
If you’re gonna make a CD, you’ll probably want to make it bootable too… go here for help with that
http://members.chello.nl/a.vanheumen1/nero/
email me if you’re still having probs..
bryson_c@hotmail.com
The issue seems to be with the actual cd, I just had the problem occur and happened to have another XP pro cd handy. i took out the cd before setup started when it prompted me for the cd I put the new one in. and it worked like a charm.
I have been trying really hard to get XP to work over the past few days but I always no matter what i do get the Manifest Parse Error.
I have followed all the tips of this site ie
Replacing my DVD rom with a cd rom
Makeing a bootable disk
Replacing the controls.man file
And it still doesnt work and all its achieved is losing all my data
Anyone else got any suggestions?
SUCCESS STORY! I tried to install a copy of WinXP Pro, got the Manifest error… control.man errors, and catalog invalid rubbish… Copied entire disk to a folder on my desktop, replaced control.man with Richard’s text… burnt a new CD using Roxio Easy CD creator 5 (memorex700CDR)… Deleted XP folder from PC… removed all programs not compatible with XP… cleaned up HD… Put in XP Pro… and YEEEEHHHHAAAAA, I’m now running XP Pro… Upgraded instead of clean install, running smooth so far… Tx, Richard for your help!
Funny enough i tried to install Window’s XP using my DVD-Rom and i didn’t work even with replacing the Control.man folder.So i installed using my Burner rom…..And it works…So DVD players have a hard time reading the folder but Richards replacement controle.man file really works…THANKS
Heya guys.
I ran into this problem this weekend… I tried replacing the Controls.man and re-burning the CD using Nero but it still doesn’t work. The CD boots fine but it still fails when trying to read the controls.man … I double checked on another computer and the Controls.man file is in the right place and can be read by notepad. Anyway I did a little more searching and in addition to the link above describing how to burn the CD in Nero, another webpage said you need to check Finalize CD, and choose Disc-At-Once as the burning method (which the above link didn’t mention). Trying to re-burn the CD one more time… I sure hope it works!!
I’m encouraged by the other success stories here so I’m trying to stay positive… But god, failed Windows installs has *got* to be one of the most annoying things in the universe!! I hope I don’t have to send my CD back for a replacement because it could take another 5-7 business days to get it shipped 
(everyplace only wants to ship free replacements via Ground unless you pay extra $$, sigh)
I’ll try to write back again if those extra 2 Nero options work.
Still didn’t make a difference.. However I found an article on M$’s page. Going to try doing that now. Also, though the computer I’m trying to install this on doesn’t have a burner, I’m borrowing a cd burner from a friend and I’ll see if it has any better luck finding this file.
For some reason regedt32.exe refuses to run from that shift+f10 command line… tried using regedit on a WinMe box but it can’t do the “Load Hive” thing and it can’t read the System.sav file as a regular registry file so I’m out of luck. The vendor I bought the CD from is replacing it, though I’m going to have to wait for it to arrive.. sigh. Ah well. Hopefully that M$ kb article above can help someone in the future.
Oh yeah, one more *weird* thing. From the Shift+F10 command line I was able to xcopy the whole D:\i386 (cdrom) folder onto my C:\ drive. I rebooted and took the XP cd out. It asked me where the Asms folder was so I put in C:\i386. Still got the same parse error on line 0 in Controls.man
I double checked and the Controls.man file on my C:\ drive is an exact copy of what is posted on this site (with no extra spaces/lines at the beginning or anything). So much for XML being flexible! Anyway a new CD should do the trick, I just hate having to go back to WinMe for a week or so.
Works wonderfully! Just upgraded from Millennium Edition (which is REALLY bad; even Win98 ran better…) using your Controls.man . I don’t understand how it’s possible that my original controls.man was empty, but it works perfectly now. Thanks!
I followed instruction to download the new CONTROLS.MAN from a tripod server, burn a new CD, now instead of getting error in LINE O, I gets error in LINE 4. Any Ladies and Gentlemen out there know why this is and how to go about to overcome it? Please help. Please help!
Worked for me. Thanks
Hi everybody! This web page is the first result from Google when searching for the term “windows xp Manifest Parse error”.
I am having this problem too. Admittedly, I am using pirated software — I have no problem saying that. I downloaded a pirated ISO and a keygen for Windows XP. I intend to use it for test purposes only as I use all Mac and Linux desktops and I need to test Samba Winbind compatibility.
I have no knowledge of this actually occurring on non-pirated Windows XP disks, but it is possible. I discovered the problem after booting the system for the first time after a CD install. It gave me the manifest parse error. I then searched for answers online and found this website.
I checked my written disk itself and the CONTROLS.MAN file in question was indeed corrupt on the CD. Next I turned to the original ISO image and raw read the CONTROLS.MAN file. The ISO image file was not corrupted. Therefore, something occurred during the authoring of the CD itself. The CD is bad but not the image. So, using the same media, same CD authoring program, I made minor changes, writing out the image at 1x speed instead of the 40x speed that my CDRW drive is capable of.
The result was that the problem did not occur and I had a fully functional Windows XP installation disk. It may be a clever copy protection method based off of the image pattern, but I do not [know] of it. It is impossible for a CDROM or DVD drive to write to a CD, so forget about that right now.
If you are unlucky enough to have a CD copy but no original ISO image, you can use a program that runs under windows called WinISO to modify the file in the image itself, thus the easiest route of correcting this problem. Make a new image from your bad disk, modify the image, and then write it again until you have a working copy. Things that might make a difference are media quality, CD authoring program, and CD writing speed.
If you think working with Windows is a pain, I really ask you to try out Red Hat Linux, or if you have the cash to buy a new box, make your next one a Mac and get OSX — it kicks ášš, and it’s BSD based. Apple computers are quiet and still powerful, and the operating system is smooth and works. Listen to those Apple Switch commercials. If you are stuck on i386, Red Hat is very easy to install, you are in control of the operating system, and Red Hat offers REAL support for their users. If you are a more experienced user I highly recommend FreeBSD, OpenBSD, or Debian Linux. It is too bad that BeOS kicked it — it had serious potential too, but the common computer user is really a dumb person and too lazy to see what else is out there or learn new things.
I should know, I am qualified to say so.
Cool website Richard.
Jesse
MCSE, RHCE, CCNP, CCDP
Thanks! I just wish I had an answer as to why this sometimes happens with shrink-wrapped CDs. Limiting the write speed to 1x is a good idea. Nowadays I never write above 6x despite the higher rating of my drive. Using 8x and up always seems to corrupt the data, regardless of the installed drive or software. - RDL
I just used Richard’s control.man content to resolve my problem experiencing this Manifest Parse Error. Thanks a bunch RDL!
just a note:
images burned with nero will be fûçkëd (tho nero says succesfull)
burn with cdrwin
//pc is out
The following is the short version of the article from labmice.net. This article had been removed by pressure from Microsoft. http://www.labmice.net/windowsxp/articles/changeID.htm
If the product key used in your workstation installations [is a] leaked or invalid [key], you may need to change the key (re-enter a valid key) in order to install Windows XP service pack 1, and to make sure your environment is legal. You could completely re-install Windows XP Professional or you can try the method below. (Please backup your system before attempting this.) This workaround is only for the corporate editions of Windows XP Professional using a compromised or illegitimate key. Windows XP Home Edition and retail versions of XP Professional should not be affected by Service Pack 1. Although this procedure may work with other versions of XP, we have only tested it on the corporate edition (volume license version) of Windows XP Professional.
Backup your Registry/System State.
1. Backup your system state by clicking Start > Run > and typing ntbackup > Click the Advanced Mode button in the Backup Utility Wizard. >Click the Backup tab, then in Click to select the check box for any drive, folder, or file that you want to back up, select the System State.
2. As an alternative, you can backup just the Registry by clicking Start > Run > and type in Regedit From within the Regedit screen, right click My Computer, choose Export, name the file whatever you choose, and click Save.
To change the product ID.
1. Click Start > Run > and type in Regedit
2. Browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\wpaevents
3. Double-click OOBETimer
4. Remove the ‘ca’ part from the value. (Changing or deleting any of the binary values will accomplish the same effect)
5. Click OK and close regedit
6. Click Start > Run and type in: “%systemroot%\system32\oobe\msoobe.exe /a”
7. Choose the 2nd option (phone activation)
8. Click Change Product Key (at the bottom)
9. Enter your valid Corporate Product Key
10. Press Update and close the window
11. Restart your computer
Verify the change.
1. After the workstation restarts, click Start > Run
2. Type in: “%systemroot%\system32\oobe\msoobe.exe /a”
3. Make sure the dialog box says ‘your copy of windows is already activated’
If you performed the above steps incorrectly, or used an invalid key, your system may not be able to boot. Use the F8 key to boot to the last known good configuration and retry with a valid key.
Thanks for the info. Sorry, but I removed the product key from your copy of the article because I really don’t need Microsoft on my ášš. I’ve had enough people stalking me lately! - RDL
After making the change of controls.man file, I was still unable to install Windows XP.
I just used Richard’s controls.man content to resolve the installation problem with XP’s “manifest parse error”. I tried to follow instructions from Richard to run i386\winnt.exe, but i could not find the winnt file in my dumped harddisk, instead of this it shows winnt32.exe file.
I followed the steps descibed by “Happy User” to change my Product ID. I only get the activation window without any options. It is a blue-colored window. Any idea why I do not get the options to change the CD key? I guess I can try installing SP1 without changing the Product ID???
It is a bad CONTROLS.MAN file that will stop XP from installing. I had the same problem, but with different error messages (when installing from a CD it only said “error: a required installation file cannot be found in i386\asms”, and when trying to install from the harddisk it said “error: the manifest file does not begin with the required tag or format information: *:\i386\asms”. Then my computer started forcing a boot into win xp, but win xp wouldn’t load! This would have disabled the system if I didn’t have a backup C: drive handy. I checked CONTROLS.MAN on my CD and HD (image from CD) and the CD said it was there with 2 kb, but when opened with Notepad it was empty. The HD image was missing CONTROLS.MAN entirely. I opened up a new Notepad window and copy/paste(ed) the script from above into it, then saved it as CONTROLS.MAN to the /i386/asms/6000/msft/windows/common/controls directory. I then successfully installed XP to my D: drive (previous C: drive made unbootable earlier). It works perfectly! Do not install using the key that starts with “FCKGW”. Find a newer corp key or use xpkey.exe (a search on Google, or any p2p can’t miss it)!!! Sorry if this is redundant to some, but I wanted the above errors to come up when others search. I looked forever, before finally finding this site. Thanks to everyone here for solving this small problem. XP should be free to anyone who got suckered into buying ME as the “ultimate OS”.
Actually you can get around having to do a full reinstall by letting the system restart after it encounters the error and removing the Windows CD. It will continue setup right where you left off and ask for the “asms” file and you simply click OK and it will let you enter in the path to the file. At this point you insert a floppy disk which you’ve made to have the complete file tree (all folders the same) as on the CD down to the CONTROLS.MAN file. Make sure that your CONTROLS.MAN file is correct (4kb or so) and then in the path change “E:/I386″ to “A:/I386″ and hit enter. This should do the trick. It will read the Manifest file from the floppy and when it’s done it asks you to reinsert the Windows CD and installation continues as normal. Email me if you have any other questions as I have done this install numerous times. Adios and Good Luck!
Thanks!
1. downloaded MSDN XP Pro image
2. burned to a CD-RW 8x
3. got the stupid manifest error
4. Google sent me here
5. used winiso to look at the image
6. all the files were correct on the downloaded image
7. burned a CD-R at 2x disk at once with Nero
8. checked that CD
Yea, finally got past the stupid error! Thank you, Microsoft, for making everything we do just a little bit harder!
If you go look on the CD, open up the CONTROLS.MAN file, you’ll see that’s it’s broken. It IS empty. Trying to change CDROM is just plain stupid.
I got a similar yet different error message when installing WinXP! My corrupted file was i386\asms\1000\msft\windows\gdiplus\gdiplus.man - line 0. Did anyone else find this file empty?
Jeez… Fûçk Bill Gates and use XP corp. plenty of keygens out there…. C’mon people! Civil disobedience is the only way to bring Billy Bob Gates down.
While I do not condone or support the illegal usage of pirated software, I do support the reduction of power currently held by the Evil Empire! - RDL
Dear, Richard — I have one thing to say about your help in proliferating the abuse of Microsoft software… THANK YOU!!!! That dámn error was driving me crazy after just spending $2K on a new PC and then not being able to even use it… Can’t even think about it now but, once again, thank you. You’re a gentleman and a scholar.
You’re welcome! My purpose of informing the interested public is certainly not to proliferate the abuse of Microsoft software, but merely to point out the ridiculousness of putting up with mediocre products from the Evil Empire. As I’ve stated several times, I ran into the problem with a fully licensed OEM version that I obtained directly from Dell with my PC purchase and desired to help others with the same problem. I am nonetheless very pleased that my tribulations and subsequent workaround has helped so many. - RDL
Well, I’ve had the same problems also, and I’ve wasted about 20 blanks trying to fix the problem!
There are some things I’d like to point out, firstly the *.MAN files are somehow corrupted by the Windows system! This happens either when its copied to an image file from CD or harddrive. It’s not that the text is changed in anyway… its how its written to the disk causing a “crc error” or “bad cd cluster”. I also had the same problem with MSWINCRT.MAN on installation “in the asms\7000 folder” (maybe cuz I have an Athlon x86 chipset?)
The only way around this was copying the ASMS folder from the WinXP CD, to the harddrive and renaming CONTROLS.MAN to CONTROLS.MA_ and so on (there are 5 *.MAN files in the ASMS folder)
E:\I386\ASMS\1000\MSFT\WINDOWS\GDIPLUS\GDIPLUS.MAN
E:\I386\ASMS\5100\MSFT\WINDOWS\SYSTEM\DEFAULT\DEFAULT.MAN
E:\I386\ASMS\6000\MSFT\VCRTL\VCRTL.MAN
E:\I386\ASMS\6000\MSFT\WINDOWS\COMMON\CONTROLS\CONTROLS.MAN
E:\I386\ASMS\7000\MSFT\WINDOWS\MSWINCRT\MSWINCRT.MAN
Next, add the *.MA_ files into the WinXP iso image using WINISO, and then delete the old “CONTROLS.MAN” and rename CONTROLS.MA_ to CONTROLS.MAN etc., inside the iso…
hope this helps
lenny
You guys rock! I just used the copy of controls.man file at top and it worked fine. I copied XP onto my hardrive and replaced the file, reburned it and it worked fine… Thanks for the help!
I have Win XP Corp edition and the same thing happened to me. Your solution at the top was right on, and now I am up and running perfectly! Also, I am making it a point to spread the word, thanks!
Am having the same problem as the rest. When I tried to install XP Pro, during setup I got a bunch of files not loaded correctly. Told to hit ESC to continue but XP may not load correctly.
Eventually I got through it but then the Manifest
Parse Error. My question, being a total novice, is
how is the Controls.man file replaced? When I tried to copy the CD to my harddrive using Adaptec, immediately it instructs to put a fresh CD in and it starts to burn. There isn’t any time or way to copy anything. And what are the exact
steps to replacing the Controls.man file? These may be stupid questions but I’ve only used a PC for a few years and am self-taught. If anyone out
there can discuss the process throughly, I’d
really appreciate it. Thanks.
Thank you so much your info about changing the files in controls. Helped me a lot and made šhìttÿ Windows finally work. Too bad Microsoft didn’t have the brains to figure it out.
– thxs again dave
ANOTHER SUCCESS STORY!!
Richard, you are a genius! Also, thanks to all for the postings, combined, I was able to figure out a resolution for this on my system. BTW, contrary to popular belief, this is NOT a copyright protection scheme by MS, it’s a bad design. Surprise! I know this because I downloaded XP Pro AND Home from MSDN and got the same exact error (I was burning them at 40x; bad idea looking in hindsight.) I went through two paths to fix this and they both worked. They are nothing new from what’s mentioned above, but I just wanted to share
1. TEMPORARY SOLUTION: Copy the i386 folder to a FAT32-formatted hard drive. Used winimage to extract CONTROLS.MAN and overwrote the bad file on the HDD. Ran c:\i386\winnt and installed as normal.
2. PERMANENT, FASTER SOLUTION: I burned the XP ISO using Nero 5 at 1x (2x did NOT work!!) also chose finalize, burn proof, and disk at once and that did the job! Now, I have a working, bootable XP Pro CD!
Thanks for all of the input. This is a GREAT site! Nice work, Richard!
Your fix solved my ‘Manifest Parse Error…..’ problem too. After my first failure I formatted the Hard Disk, copied the contents of my (copied) XP Pro CD onto it. I then patched in a new and correct Control.Man file. When my second XP install fell over in the same place I simply removed the CD, rebooted and when prompted I pointed the installation file at the /I386 directory on my hard disk. I was later asked to replace the XP CD but the installation continued and worked fine. Many thanks Richard.
I, myself, had this same problem, and I have three CD-capable Readers on this machine. A Cyberdrive CDRW 40/16/48, an Artec/Ultima DvD, and an old SCSI Yamaha 4600TICP. Got the same error on every one. Will try your fix now, and see if she works.
I had the same error as everyone else… I used a different Windows XP CD to install the OS and that worked fine. I think perhaps the fixed the file on different types of CDs, or perhaps different versions of the file work better on different computers. First I was using Windows XP Pro (OEM) then I switched to a different version of XP Pro… Basically, try a different CD with a different version.
Hey, Hey, Hey! I think it worked! I copied controls.man from WinXP home version. Thanks!
Well, for those of you that want a little different approach… here is how I did it. I used WinISO and made an ISO of my Windows XP Pro CD. Then using WinISO replaced the contents of the “Controls” directory. (Consists of three files - controls.man, controls.cat, and one other one)
Using Roxio EZCD Creator 5.1 Platinum I burned the new ISO back to a fresh new CDROM. Worked just like magic…
Saved my system! My friend tried it, but couldn’t change controls.man, until i told him it was read-only… some people don’t notice the obvious things. Now if I could just figure out why my system locks and goes BBBBZZZZZZZZZZ through my speakers…
Here’s my question. I just ran into this very problem myself. I used my XP disk to install XP onto one of my computers and it worked fine. In fact, being new to XP, I ended up reinstalling XP numerous times using this disk thanks to my curiosity with the XP registry. Anyways, I have scrapped the old computer and started using a new one. But when I tried to install XP using the same CD on the new computer, I received the Parse error. Of course, the control.man file was empty when I checked it, but then it’s always been empty hasn’t it… I mean, it’s not as if it was magically erased between the last successful install and this unsuccessful one. So what’s the deal? Do you think it is hardware related? I mean, are certain systems sensitive to this error whereas others are not? I can’t think of any other explanation since CD data simply cannot be altered after it is created… I mean on regular CDs obviously, not CDRW. Any ideas?
Like Dan, above, I am a novice and need specific details on how to resolve this manifest parse error when installing XP. I am not sure how to copy to HD nor replace the controls.MAN file using notepad. Can someone please make things as simple as possible. An idiot’s guide required. Thanks!
Gordon, I made up a quick webpage outlining the details for this fix. Hope it helps. There are several images on this page so be patient.
http://www.geocities.com/zrantheus
Had the same error and problems as everyone else but finally got it to work. Here’s what I did: Copied the contents of my XP CD to a folder on another computer’s hard drive, edited the CONTROLS.MAN file to include what you have posted here on your website, burned all the files with newly edited CONTROLS.MAN file to new blank CD at 2x speed (any faster and the buffer overruns), since I didn’t make the CD bootable I had to download the XP boot floppies from http://www.winxpfix.com, but when I tried it, it worked like a charm. One note though, I may have been the only goofball that did this but the information that you have posted as the contents of the CONTROLS.MAN file shouldn’t include the bracketed stuff. I initially thought that the file resembled a win.ini file with each section separated by bracketed headings. So I copied the brackets as well as the info and it didn’t work. Once I took out the bracketed info it worked great. Thanks for posting this info, it was very helpful.
I finally thought I’d managed to sort it out by following the instructions above, only to encounter a further problem. After copying the installation files my PC reboots and I get missing or corrupt hal.dll windows can’t find the file \system32\hal.dll. I am running 98 and trying to install XP Pro as a dual boot on D (a separate disk). When I look for the hal.dll file I can see it on D but not on the C drive where 98 is installed. Is this right? I’ve heard that it may be a boot.ini problem but being non-technical I am a bit lost as to what to do without clear advice. Any ideas?
This is apparently a problem many people are having whereas I found multiple references to it online. If the following article from Microsoft doesn’t help, try doing a search for “missing or corrupt hal.dll file” on a search engine. That’s how I produced the following link. Good luck!
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q320252
One more note, Gordon… Don’t give up. Relax, work the problem. Microsoft applications have millions of beta testers worldwide (that being the consumers) and someone has experienced your problem out there. Look for the reference, read, take notes and experiment. You say you have more than one harddrive? I myself have two harddrives. Both are 40 gigs. The first drive is partitioned in half for two operating systems. The second drive is for all of my personal data. This way, no matter WHAT I do to Windows, or what problems I encounter, I am only a re-installation away from grace, since everything important is easily re-accessable on the second hard drive. The reason I’m posting this is I just helped someone get their copy of XP to install. It wasn’t a big deal really, but they panicked. Now that it’s running, the modem won’t work and they’re going to dump XP. Gave up too easily and are missing out on a nice build of Windows… well, as nice as it can be anyways. heh! Keep at it, and continue to post here with updates and questions. I’ll keep a watch for your post and help you where I can as I’m sure the other users here will do as well. Good luck Gordon, you’ll get it straight in the end.
I’m afraid I didn’t think that sentence out…now that you mention it, the interpretation is rather dubious.
BTW, how’s the XP Install going Gordon?
ZD
I was just curious to know if anyone else was wondering if it may depend on the speed in which you write the disk? someone above had said that they tried burning again at a slower speed and it worked.
I have the same problem but the error says that my GDIPLUS.MAN file is corrupt as opposed to the controls.man file. I checked and indeed the gdiplus file (but not the controls.man) is corrupted on the CD i burned. I do not have access to the original image and those iso building programs are a pain in the ášš (You cant make an image with winiso over 100mb in the trial version, and I cant find a working key anywhere) I’ve tried just burning a regular cd with only the .MAN files arranged in the same directory structure as the XP CD. I checked the files and they werent corrupted after the burning process with nero. However, when I put the CD in and tried to continue the winxp install it gave the exact same error as before, even though the MAN files weren’t corrupted. My friend has a working WinXP Home edition cd but I dont know if it is the same as the Pro edition in the way of these .MAN files.
Here’s a suggestion. Don’t burn the CD directly from the Image file, even if you’ve altered the necessary files. Either use winiso or winimage to unpack the files to the harddrive, or burn a CD from the ISO and copy the burned files to the harddrive. Now that you have a working directory of the XP install files, alter the corrupted files on the harddrive XP directory. I’m not sure how all of the burning software works as far as exact procedure, but I’m sure they all offer this option. Insert a blank CD, manually select ALL of the files on the XP install directory located on the harddrive to be burned directly to the new disk…ie: In Easy CD Creator, the option is make a data CD. Now burn the CD at any speed. This is the process I used and it worked fine the first time around. I’m not certain, but the error may be materializing during that extra step when the burning software converts the ISO file for burning.
It’s just a suggestion.
ZD
Oh yes, I forgot to mention this. Pay attention to what the volume name of the Windows XP install CD should be and make sure you manually name the new CD before you burn it.
ZD
Woohoo! I got it working after downloading the image off the internet then burning with Nero. Thanks everyone!
I have an error where it says something about driver.cab unable to copy. Thing is, it opens fine in WinZip, and I can extract any file I want. Why is this happening?
Just a big thanks to Richard and all with the help. Openened up controls.man on my laptop - content. Opened up controls.man on the PC I was trying to install XP on with DVD ROM - no content. Burned a CD with the directory structure and the controls.man only - booted into existing XP setup , with new CD , swapped to old CD when prompted and Roberts your fathers brother - XP installed no problems.
hi when installing xp prof on my laptop i get an error message that says my vcrtl.man has an error in line 4 or 16. Can anyone help??
Hi! Thanks Richard for your really informative guide. Have recently moved to Germany and wanted to install windows xp professional in german on my Dell Inspiron 8200, which comes bundled with the crappy Windows XP Home.
I have read all the comments on the website. And am ready to try it out. My question however is, would the contents of CONTROLS.MAN work for Windows XP Professional (German Edition) as well? Unfortunately I no longer have the original Windows XP Pro (which I so naively copied onto a blank CD and gave back to my benefactor) so I cant compare the contents as well…
Would appreciate any help in this regard!
Thanks
Tim
Burning image from MSDN Academic Alliance to CD with Prassi PrimoCD Plus 2.1 on an Acer 16/10/40 didn’t work. But with Roxio Easy CD Creator 5 on a TEAC CD-W216E it worked! Read and installed on Acer 16/10/40. I finally can study for my final exam later today and maybe get a little rest!
God bless! –Loren
hey richard nice site! came across this because, of course had the same error, “error: the manifest file does not begin with the required tag or format information: *:\i386\asms”. this was from an iso burn from nero at 12x using a dvd rom to install. then used a cdrw for the next tries.
i tried changing the CONTROLS.MAN with yours above. burned it at 1x with nero checked it and still no luck. so i used winiso to check the iso image and everything looks complete including the CONTROLS.MAN so i tried burning from iso again at 1x with nero then checked the CONTROLS.MAN and sure enough it was blank, checked with notepad.
so my question is, after reading all the replies above, does it matter what operating system you are using initially on making the the CD? if not, then i really think its just my burning media NERO. after being unsuccessful i had to install win2k pro.
my assumption about nero comes from creating a win2000 pro CD from the time-limited version to the time-unlimited version where you have to alter the SETUPREG.HIV file with REGEDIT32. i have the original installation cd but time-limited. did all the necessary applications to alter the SETUPREG.HIV file then burned to cd with nero at 12x and 1x and installed unsucessfully. now i was burning this cd in win2k pro. now im confused because there are successful installs listed above when burning with nero. oh yea also chose to disc at once.. finalize cd.. still unsuccessful. im not giving up though. it might also be from dling it. so im dling 2 more iso’s from kazaa. if anyone can help me please do. THANKS
oh yea and the intial unsuccessful cds of xp were made in windows 98se. then the windows2k pro cds were made on installed time-limited version. created win2k pro cd and had missing installation files next time around ill try to list files unread. i know after the first reboot the TCPIP.SYS file couldnt be read and i think before the boot i dont recall but it would probably after the first boot too.. the browseui.sys i think couldnt be read too.. dont have time right now will list more later. thanks again
sorry i just read the above message i typed up this morning and it made only little sense to me hehe.. so here i revised it.
hey richard nice site! came across this because, of course had the same error, “error: the manifest file does not begin with the required tag or format information: *:\i386\asms”. this is the message i got after skipping a file. also the cd was from an iso i downloaded from kazaa and burned in windows 98se. then using nero at 12x, finalize cd, and using a dvd rom to install.
i tried changing the CONTROLS.MAN with yours above. burned it at 1x with nero checked it and the CONTROLS.MAN was there but still no luck with the install. so i used winiso to check the iso image and everything looks complete including the CONTROLS.MAN so i tried burning from iso again at 1x with nero assuming this would be a better burn according to previous posts above, then checked the CONTROLS.MAN and sure enough it was blank when checked with notepad.
so my question is, after reading all the replies above, does it matter what operating system you are using initially on making the the CD? if not, then i really think its just my burning media NERO. after being unsuccessful i had to install win2k pro time-limited version.
my assumption about nero comes from creating a win2000 pro time-limited version to the time-unlimited version where you have to alter the SETUPREG.HIV file with REGEDIT32. according to another website (http://www.winchan.net/win2000/) they say you have to be running nt or 2k already prior to altering the SETUPREG.HIV file. i have the original installation cd for 2k pro but time-limited. i did all the necessary applications to alter the SETUPREG.HIV file then burned to cd with nero at 12x and also 1x. installed unsucessfully. now i was burning this cd in win2k pro. now im confused because there are successful installs listed above when burning with nero. oh yea also chose to disc at once.. finalize cd.. still unsuccessful. so i started with one of the cds i made from the time-limited version got an error switched cds to an iso image made from a downloaded version of win2k pro then got one error which was the TCPIP.SYS file couldnt be found. but ended up with a succesful install of win2k pro but i had to get a new copy of TCPIP.SYS file and copy it into the drivers folder.
now back to winxp pro corp it might also be from dling it. so im dling 2 more iso’s from kazaa. ill try burning it with win2k pro with nero again.. then ill try using another burning software. if anyone can help me please do. THANKS
Thanks for the help on this forum, especially ZD who provided the much needed motivation and the knowledge I needed to proceed. I had reall almost given up, but I tried the link to Microsoft and their advice worked. The only prob was, I expected it not to work, and so had setup the install as an upgrade. This means I now have XP but no 98 - never mind, at least it works, most of the time.
Sometimes when i click on links the window I’m in shuts down for no apparent reason. Any ideas?
Once again, thanks.
Great news Gordon and you’re welcome. Glad to hear you are up and running. As for loosing Win98, it’s really unnecessary now. WinXP is the OpSystem us gamers who loved NT/2000 had been waiting for. It incorporates the necessary components of the Win95/98/ME OpSystem needed for game play. So, basically WinXP is a hybrid of both lines of software. I personally have yet to find any of my mainstream applications from Win98 that will not run in WinXP…drivers aside. However, XP drivers were a mere click away for my hardware.
As for your new problem, I have heard stories…unconfirmed by your’s truly, that an upgrade from any qualified Windows OpSystem to XP is a bad way to go. But then I’ve always felt this way whereas I’ve had problems doing it myself when Win98 came out. This could be a result of a piece of hardware, and/or it’s drivers corrupting XP. So here’s my suggestion:
1. Power down the computer and remove all add-in hardware. ie: Soundcard, modems, network cards, etc… Leave only the video card, and obviously don’t mess with the harddrives, CDROMS, etc.
2. Reinstall WinXP with a fresh FULL copy.
3. Now, basically we’re getting the system to the most basic state of operations. Get out a good pen and some paper. Make a note of what you’ve done so far.
4. Test for the problem. Try to recreate it any way you can remember from when it first occurred. And while you’re at it, test the entire system. Run a scandisk, explore the OpSystem, watch and feel how it responds. In this state it should react quickly and free of trouble…assuming you don’t have an actual problem with the computer itself.
5. No problems? Make a note and power down the PC.
6. Now, install one piece of hardware at a time, testing each time to see if the problem reoccurs. Keep notes each time, they help later I promise.
Odds are, your problem is from a nasty upgrade and can be remedied by a FULL reinstall of WinXP. But if it’s being caused by hardware or drivers, you will find it only through a methodical process of elimination. If and when you do discover the culprit, get online and start researching, and research some more. You’ll most likely find someone with a similiar problem and what they did to fix it…just like this page here. If not, you may have to consider an alternative piece of hardware.
Well, I’ll cut this short before Richard sends me a mail bomb for eating up his server space. Keep at it and ask if you need an answer. Personally, I loved moving up to WinXP. It’s like a puzzle, figuring out the new system, learning it’s little quirks, solving hardware issues, etc. Solve the puzzle Gordon, and take solice in the fact that unlike women, there will come a point when you will understand what the hëll is going on.
ZD
Another solution to the parse errors, I got them all . CONTROLS.MAN, GDIPLUS.MAN and VCRTL.MAN , Burned a lot of cd to try to fix it
when I got a bootable its man menu would not let me execute the install menu option. Using the soluton at barts http://www.nu2.nu/bootcd/#wxp
Go to microsoft get Windows XP Professional with Service Pack 1 Utility: Setup Disks for Floppy Boot Install
6 floppies,
Install up till you get the error.
Boot off the floppies.
It works.
Thanks, it worked! I created …\CONTROL.MAN on my HD, removed the CD, rebooted, it asked me for my cd i386 dir, I typed in my HD dir, no error, then switched back to CD for the rest. A floppy could be used too.
My FCKGW.. key failed (it worked running setup in windows) and my XFKFG.. key worked (it failed running setup in windows).
Richard, have you seen this? Any thoughts on how to help this problem? I have a pirated version of XP how do I go about preventing this from geting to me if I can’t update to protect against it? Also, is there a site to get updates for my XP pro system that I’m using without buying it?
December 19, 2002
XP Flaw Puts MP3, Windows Media Files at Risk
By Dennis Fisher
Thanks to a newly found flaw in Windows XP, two of the most popular audio file formats can be used by crackers to take control of remote PCs. Users only need to hover their mouse pointers over the icons for malicious MP3 or Windows Media files to execute the attacker’s code, Microsoft Corp. said in a bulletin published Wednesday.
The vulnerability lies in the Windows Shell, which is the portion of the operating system responsible for defining the user’s desktop as well as organizing files and folders and enabling the OS to start applications. An unchecked buffer in a function used by the shell to extract custom attribute data from audio files enables an attacker to create a malicious MP3 or Windows Media file and use it to run code on a remote user’s machine.
MP3 files are traded and shared by the millions on sites and peer-to-peer networks all over the Internet. Users commonly download and play files posted by people they’ve never met, and there is essentially no practical way of verifying the content of these files to ensure that they’re not corrupted. The Windows Media format is somewhat less popular than the MP3 format, but is still quite prevalent online.
To exploit the vulnerability, an attacker can do one of three things: host the malicious file on a Web site or on a network share or send it to a user in an HTML mail message. If a user hovered the mouse pointer over the file or the folder containing the file–on a Web page or on the local disk–the code would execute. A user would need to open or preview a mail message containing the code to execute it in the e-mail attack scenario.
Thank you, Richard for posting the fix! Thanks to you, my computer now is working! It’s people like you that make the internet such a wonderful place!
After reading all of the above postings, I decided to just try reburning the ISO image at Nero’s slowest setting (2x on my version). That did the trick. I join the many others in thanking you for this information. I wish Microsoft had the guts to publish this kind of stuff.
HELP!! I keep getting the syntax error on line 4 problem of the controls.man file when upgrading winxp from 98se, despite following the code and relevant instructions above. The same thing happened during a fresh install too ;(
Any suggestions??
Okay…I don’t know bout many other ppl…but I fixed the controls.man file…it’s changed and set…but now I get another error
“A Component’s file does not match the verification info present in the component manifest.”
Any one any idea what it means?
I’m installing from my hard drive cuz I’m sick of wasting cd’s trying…
OK ok… I just got a burnt copy of Xp… That’s right burnt. And I got the same message as everyone else something about not be able to copy some folder. I’m trying to change the controls.man, hopefully it works. I’m really lost when it comes to burning images with Ahead Nero, can anyone help?
Someone mentioned that Disc-At-Once and being sure to Finalise the CDburn fixes the problem - They are spot on… Unfortunately i had to drive back into work to try this, but it was well worth the drive in…
Thanks guys!!
I’m pretty certain those two steps ARE required Brad.
I uploaded a copy of the CONTROLS.MAN file to my “Manifest Parse Error” site for those having trouble creating their own.
http://www.geocities.com/zrantheus/
Good luck.
ZD
Richard,
thanks for the wealth of information you’ve collated and thanks to the community of contributors. List me as another victim of the abovementioned ‘manifest’ error. I had other options for restoring WinXP Pro on my PC (ie vendor disks to recover back to factory settings which included WinXP) but I tried a friend’s WinXP Setup CD to compare hardware support for an existing CD burner …an internal HP CDWriter Plus 8200 which has a top burn speed of 4X and came supplied with Adaptec Easy CD Creator 3.5c. It’s a trooper that’s served well for 18 months and highlighted the “manifest” error. I empathise with Tom Miller … I too have initiated at least 10 iterations of “format-hard-drive, install WinXP” but scrapping the burner was at the bottom of the ‘culprit’ list ie. there are 6,500 files that are burned on the WinXP Setup CD ….
a) why are there less than a handful of files bearing grief ??!!
b) you can burn a dámn lot of CDs using any number of CD burning freeware or shareware for the price of a new CD burner
c) there’s no guarantee the new CD burner will fix the problem
My problems appear attributable to the CD burning software. During the recent repeated rebuilds of my PC, I engaged the services of a colleague (well, actually…the colleague was useless but their Win XP CD was instrumental). Starting with a clean hard drive, my colleague’s CD installed WinXP Pro from ‘go to whoa’ without any grief yet my copy of that CD bogged down with he ‘manifest’ error. Went to Bill Gates’ support web links and their suggestion is ‘return to vendor or buy a new CD’…. the cursade was on …. Bill Gates’ “manifest” error was stinking up the corridors of my mind. I had used Adapter Easy CD Creator option “CD Copier” in the hope it would make a mirror copy that would be equally WinXP Setup bootable on a clean hard drive. Well, it appears that ‘CD Copier’ is a loose term….they probably should have called it “CD Approximator”. I’ve had ‘buffer underrun’ errors during CD burnin but never discrimate file erosion. I’ve made 3 copies using burn speed of 1X, 2X and 4X all resulting in the different versions of corrupted file CONTROLS.MAN … all occurrences of the file showed 2K on disk, 2 of the 3 were empty (well …. might have had non-display characters but I couldn’t be bothered …. we’d be quibbling on different degrees of error),the third occurrence contained text reflecting the make/model of the CD Burner… go figure. I then copied WinXP setup folders/files from my colleague’s CD to my harddrive and then used Adapter CD Creator to create a CD layout and burn the files and there were no curruptions in the files, albeit the disks were not suitable for WinXp setup bootable on clean hard drive. I then repeated the burn of all the files with the exception of CONTROL.MAN leaving the disc open, then added the file on a second burn and it was still in perfect condition. (as you can clearly see, the medical association warns that Bill Gates is a health hazard !!!) At this point, i now have 8-9 CDs pinned on the cork board ….. 10 more and I’ll have enough for a mock-up 18-wheeler MACK truck with bogie.
Today I downloaded 30-day trial CD burning software ‘Alcohol120 v1.4.0 Build 114′ (self extracting 4Mb EXE available from http://www.alcohol-software.com),
installed it in 30 seconds, fired it up, hit the ‘Copy Wizard’, chose maximum speed for the CR-RW (yep ….used all the available 4X it could muster)
and out popped a sweet copy. The trooper HP CDWriter Plus 8200 is still going strong and it’s Adaptec that’s on the ‘Re-consider’ list. Another colleague has made a copy of the CD using a CD-RW purchased last weekend and that CD appears useable. The fact that most people are getting clean copies using current CD burning software suggests it’s not the hardware that’s at fault. Another observation i’ve just noticed is that the *.MAN files in question have perhaps the longest path names on the CD… coincidence ???!!! …AM 21/01/2003 ESDT Australia
Worked for me! Jus’ copied the whole contents of the XP CD to HD and copy and pasted Richies text above into Notepad, replaing the whatever file it was. Got no errors and installing my second copy as we (I) speak.
I read with great interest the experience of the many downtrodden users regarding the Manifest Parse Error. I’m not sure if my problem is related. My wife purchased a DELL Inspiron 2650 laptop from DELL online in Sep 2002. My system came with XP PRO and SP1, IE 6.0, Office 2002, and other bundled software pre-installed. On many occasions my system just hanged, sometimes with as little as two or three appplications loaded. Outside of the Office 2002 suite I use Quickbooks. A local PC technician told my wife that it was normal since XP has a number of quirks still to be ironed out. I recently installed the System Mechanic utility to scan my registry since I became fed up with the persistent system hangs. The results revealed several invalid (orphaned) entries in the following registry locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\WDM
“sample value name is C:\WINDOWS\system32\advapi32.dll[MofResourceName]“.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\WDM\DREDGE
“sample value name is C:\WINDOWS\System32\DRIVERS\ACPI.sys[ACPIMOFResource]”
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Active Setup Temp Folders
“value name is Folder”
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\ x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.10.0_x-ww_f7fb5805
“sample value name is Codebase” and “value data is C:\WINDOWS\ServicePackFiles\i386/controls.man”
N.B. all the *.man files are listed as invalid (orphaned)
HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Install
“sample value name is MouseInf”
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
“sample value names are C:\WINDOWS\System32\MSXML3A.DLL” and “C:\DOCUME~1\HEATHE~1\LOCALS~1\Temp\_ISTMP1.DIR\_ISTMP0.DIR\mediabuild20.dll”
I contacted DELL on 13-FEB-2003 and they sent me an XP hardware diagnostic utility - CD110210.exe - via email to run. It showed me that all my hardware devices except the Roxio Easy CD-ROM drive were okay. The CD-ROM drive failed the confidence test - READ, SEEK, WRITE, and AUDIO and was deemed incompatible. DELL Support indicated that if my hardware devices were deemed okay then I will need to reinstall my operating system, which I dread. DELL only supplied me with a reinstallation CD rather than an original operating system CD. They said that is all I will need for the job.
Since running the diagnostic test the system does not hang as often. I have to get back to DELL Support with the results. However, I am concerned about the number (55) and type of invalid registry entries that System Mechanic listed.
Would you please shed some light here? Thanks a $1,000,000 in advance. I regret being so lengthy, but I wanted to provide you with essential info to get a meaningful and effective response.
Cheers
MartinP
Another solution:
I had the same problem with setup giving me multiple .man file errors. My solution was to use Fireburner 2.1.7 to burn the ISO that I downloaded from MSDN.
It seems that the install process or the image itself is VERY sensitive to which program you use to burn the CD.
Rick
The problem is you are attempting to install an unauthorized copy of Windows XP. It is NOT a security feature. The easiest solution is to get another copy preferably from another more reliable source. The parse error originated when the original person was attempting to copy the windows xp on to another disc tried to copy from the windows xp cd-rom over to his hard drive and then to his cd burner. That’s the part when the security measure kicks in. What needs to be done is to use Roxio and do a disc to disc burn.
This site is a lifesaver! Can’t thank you enough for all the help it provided. I copied the I386 folder to my HD and modified the CONTROL.MAN file but rather than copying it back to a CD-R just told it to look there rather than the CD when it prompted. Worked like a charm! I built a new comp and was rather annoyed with having to use Win98 (FIRST ADDITION!). It was a major step up. However, will my OS be stable? I only did the upgrade and was wondering if it would be better or improve my proformance to do a full fresh copy of XP?
same problem tried your fix didn’t work just need a working copy of controls.man can you provide?
please and thanks.
Norman
Response to the slightly different comments about “Error: SXS.DLL: Syntax error in manifest or policy file “e:\I386\asms\6000\MSFT\WINDOWS\COMMON\CONTROLS\CONTROLS.MAN” on LINE 4.” or “A Component’s file does not match the verification info present in the component manifest”
I was initially having the problem with controls.man at line 0. After replacing the file with a non-corrupt version I started getting the error at line 4. Strangely on my XP CD I had 2 folders containing Controls.man, one in the usual e:\I386\asms\6000 folder, and one in a folder e:\I386\asms\60100. It was the one in 60100 that seemed to be causing the problem. Most of the comments on this site seemed to be talking only about the folder 6000. I thought it would be worth just deleting this 60100 folder to get a CD with the same file structure as most of the people commenting on this page. And it seemd to work!
So if you have the problem at line 4, it may be worth trying this. Look for a folder called 60100 in \I386\asms\ on your CD. Copy everything but this folder onto a new CD. Install from you new CD. You may get an error during install saying something is missing, but XP seemed to install anyway.
It seems strange that it installed OK without this folder on the CD, but so far I seem to have a working copy of XP.
['m] getting this error trying to install XP on [a] Toshiba Laptop with DVD. So pìššëd because I’ve used this disk several times. [The] .man files [are] there and intact - made a copy of CD with EZCD Copier ===NO GOOD=== made a copy with Clone CD Max read and 8x write and everything worked great. Apparently the DVD has problems with the CD as mentioned above. WEIRD! Maybe they should add thet [sic] to the XP compatiblity list! *LOL*
I had the same problem with a dell optiplex G1 that i am upgrading. then i used another copy cd and it worked. i still dont get it.
I have gotten the parse error also but I got it in a differnt file. My error is below.
Fatal Error
An error has been encountered that prevents setup from continuing.
One of the componenets that windows needs to continue setup could not be installed.
A component’s file does not match the verification information present in the component manifest.
***
Error:
SXS.DLL: Syntax error in manifest or policy file “E:\I386\asms\6000\MSFT\VCRTL\VCRTL.MAN” Line 11.
***
Error:
Installation Failed E:\I386\asms. Error Message: A component’s file does not match the verification information present in the component manifest.
***
Fatal Error:
One of the componenets that windows needs to continue setup could not be installed.
A component’s file does not match the verification information present in the component manifest.
What can i do about this? When i get this error XP setup restarts my computer and attempts to start setup again but it gets the same error, how do i fix this? It keeps going into an infinate loop. I have tried several times but keep getting the same error.
How do i fix this, please help me out.