The Problem
I decided to give Microsoft one more chance to have one of its (non)operating systems on my primary home computer. After reformatting my drive and beginning installing Windows XP from a freshly opened WinXP CD that I received direct from Dell, the following message appeared: “Manifest Parse error: Invalid at top level of document”. The installation failed and stopped because it could not correctly parse the CONTROLS.MAN file.
There are many theories as to what causes the error. Many folks prefer to keep their original disks in close-to-pristine condition and install from CD copies, yet rumors abound that as many as 60-70% of copies experience this error during installation. On the other hand, hundreds of people have gotten the error while installing from fresh-out-of-the-shrink-wrap, boxed versions of Windows XP. I’ve heard everything from “it’s a copy protection scheme” to “it locks you out after three installations”. None of the theories seem to be accurate.
I must be a glutton for punishment, because rather than scrapping the OS completely, I decided to push all the theories aside and figure out how to get around the problem. Old habits — like most computers running Microsoft operating systems — die hard.
The Solution
The /i386/asms/6000/msft/windows/common/controls/controls.man file on the CD is corrupt. Microsoft’s installation program doesn’t 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!
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. Burning a CD is the best 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.
hey everyone…I just wanna say that I have had these problems too about parsing errors and invalid files and whatnot, but I just re-downloaded the iso from microsoft and burned it and it worked fine…so maybe the errors just lie in the download and not in the actual image.
For those who have replaced the CONTROLS.MAN file but still get the parse manifest file error (this time in line 4 rather than line 0): the other files in the i386asms…CONTROLS folder (the .CAT file and the .DLL file) may be corrupt too. I’ve done a compare with working files, it showed that .MAN and .CAT were completely screwed and the .DLL was OK in the first half (that’s why it showed DLL version correctly), but the rest of the file was broken as well.
After replacing all 3 files with their working versions (I took them from xp home cd) the setup went ok.
Hope this helps.
Thanks to everyone. I will share my experience as well.
A guy in my company downloaded JP_WinXP_PRO_x86_build2600_ISO.IMG and burned it to a CD (probably high speed). Using the CD, I got the manifest error when trying to install Japanese Windows XP on a second partition of the hard drive. The particular file that had problem was GDIPlus.MAN. However, I can open and see GDIPlus.MAN just fine (it’s not blank). I also compared it to the copy on our MSDN Windows XP (English) CD using ExamDiff — they are identical.
The guy used the same ISO image and burned a CD again, only this time with x1 speed. It worked.
Everyone, I have found the easiest way to resolve this stupid error. I have been getting this same message for quite some time and finally found a fix. All you have to do is start the installation and after Windows XP copies the files to your HD and reboots, wait until you get the setup screen that says installing windows. Take out your Windows XP CD. Wait until it asks you for it, then reinsert the CD. Give it a few seconds, maybe 15 seconds, take the CD out again. Each time you take the CD out you will get message that you need windows XP cd to copy a certain file. Do it once or twice more and the installation should continue without a problem.
I tried a few of the solutions posted here before coming up with my own combination that works well and easily:
Andrew wrote above on Sept 12, 2002:
The disk you make has to contain all three files in that CONTROLS folder — the .cat, .man, and .dll files. That way, Setup looks for the .man file, finds the working one you put on the A-drive, and can still find the .dll file that the .man file refers to.
Easier than burning a new cd… and it works!
I tried the floppy disk workaround suggested by Andy above… Setup read the floppy disk for 30 seconds or so and I thought I was home free, but then I got the error message:
“An error has been encountered…
One of the components that Windows needs…
Data error (cyclic redundancy check),
If you are installing from a CD, there might be a problem with the disc; try cleaning the disc or using another disc.
If you are installing from the network, it is possible that not all of the files were copied correctly to your drive. Run the disk checking utility on your installation drive from the Recovery Console and start setup again.”
Is something wrong with how I created my floppy? I copied in the correct “controls.man” content and duplicated the .dll and .cat files on the floppy. I created all of the folders in the i386 directory but not on the entire CD. Do I need to recreate EVERY single folder on the CD (there are tons) or just the i386 tree? Or could something else be causing the problem?
Richard, thanks for creating this awesome resource.
Follow-up to my comment above:
It works now! I went ahead and replicated the ENTIRE directory tree from the CD onto a floppy and then included just the three files in the Controls folder (with the fixed Controls.man). To replicate all the folders on the floppy, I just copied the CD to my hard drive and then erased every file in every folder (took ~30 mins) and then copied the resulting empty directory tree onto a floppy. Then everything went off without a hitch as described by Andy on May 6, ’03. I now have XP Pro up and runninng.
Thanks again to everyone for enabling me to circumvent the evil empire.
***
Error:
SXS.DLL: Syntax error in manifest or policy file “E:I386asms6000MSFTVCRTLVCRTL.MAN” Line 11.
***
Error:
Installation Failed E:I386asms. 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.
if it helps i had this error from an original copy of xp, i made an iso and keep it for back up purpose on my computer. well i made a burn of it at 8x. tried it and the above fix and got all kinds of other errors of corrupted files. i just got the original xp disk made an iso of it again and reburned it and it worked fine. chances are if this happens its due to a corrupt iso file (or other cd image file). making a copy from the original should work just fine.
The fix to all is in the WinXp files folder of
http://briefcase.yahoo.com/login99ph
When Windows XP installs, it makes a directory named $win_nt$.~ls to your main drive. It copies almost all the CD files to it. Manifest files like VCRTL.MAN or CONTROLS.MAN check the files. Component files do not match component verification when they do not became identical to the original CD’s. To fix this. They should first all be of the same time and end with 12:00PM. I have a file copy program i made. Available to you if you email me. And if you ned the fix to VCRTL.MAN component manifest error. Download the fies in my briefcase link above and then copy them to the $win_nt$.~lsi386asms6000msftvcrtl folder. Or if you got more problems email me, or post. Ill read it once i get more money. Im out of dough, and im a hacker/programmer. See ya!
Dont forget to make abootdisk first. If you dont know DOS, just email me.
Thanks for the great wealth of information Richard!
I’m getting the GDIPLUS line 4 error. All the .man files on my CD are fine. If fact, I used the same CD to do a successful install on my other virtually identical PC. I’ve tried copying the .man files to hard drive, floppy drive, pulling out the CD and nothing keeps me from getting this error. I’ve reformatted my hard drive 5 times. I’ve re-installed Win98 and tried to upgrade from there twice and it always comes down to this error!
Any help would be appreciated.
I was getting the “vcrtl.man error in line 21”. So I just edited vcrtl.man in edit and overwrote line 21 with a bunch of spaces. XP installed fine after that.
I got a NEW one! While trying to install WinXP Corp I get absolutly NO errors, however during the copying of installation files the install stops at 37%. I try it again, it stops at 2%. Again, it stops at 55%. What the hëll it going on??? I am suspicous of my CD drive, but it has worked great up till now. Is it something else? Is it possible to install from HD or a network drive??? Can I make a temp install dir and install XP from HD???
continued from last msg…
OK I watched more closely this time. This time setup files stopped copying at 27% (driver.cab). This is after I deleted partitions and did a full format using the NTFS file system. I could hear that the CD-ROM remained spinning inside the drive, green read light stops flashing.
Just stopped AGAIN at 27%, but this time I did NOT delete partitions and reformat. I chose to overwrite existing C:windows dir. You should also know that I am putting this on an older sys. It might be below min. req.??? It use to run ME just fine; except for the usually ME/Windows bûllshìt, which is to be expected with all M$ products.
Anyways…
“it” is a:
400mhz AMD K6-II
256MB SDRAM
FIC VA-503+ (rev.1.2a) motherboard
ATI Rage Pro Turbo (2X AGP)
Maxtor 16gig HD
Yamaha 20x10x40x CD-RW
I stuffed this all into an old Gateway 2000 case
I am trying it again right now.
This time it stopped copying setup files at 12% (mshtml.dll). I deleted all partitions and reformatted using NTFS file system before this attempt. What the hëll is going on???
The reason I ask about a HD install is because I use to be able to do that w/ ME and older windows. I copied all the cab files, etc.. onto the HD and installed that way.
Any help on this would be great cause I have no F*@#kin’ clue!!!
Thank you Thank you Thank you for all your help guys, here’s what I tried and what worked for me:
* Tried a burned CD of XP Professional
* got the Manifest Parse error with CONTROLS.MAN on Line 0
* Copied a GOOD version of the file to a floppy disk, all directory names intact
* Got same error, BUT on Line 4 instead of Line 0
*******
Here’s the kicker
*******
THEN I had to copy, IN ADDITION to the CONTROLS.MAN file, the COMCTL32.DLL and CONTROLS.CAT files
Then it worked!
Hope this helps some of you others out there!
How do i fix the I386asms6000MSFTVCRTLVCRTL.MAN problem. I have read the whole page here and still cant work it out
PLEASE HELP ME!!!
Ok, I tried doing what you said. I tried to burn the disk to hard drive, create new file off of yours, and then everytime I went to burn it to cd, it said there was an error, and wouldnt burn it. grrrr Is there anyone who can help me? Im getting so frustrated!
Hello. First I tried copying a [pirated] XP Home cd. It failed. Second, I copied to my hard drive, except for one file “sxs.dl”. I can’t, for the life of me, figure out why this file won’t copy over. Any recommendations? By the way, I’m trying to copy the trial version of the CD. I do plan on purchasing the full version, but I want to make sure I like it first.
what the hëll i had same problem i downloaded a win xp iso a year ago burned the cd and installed it and everything worked fine recently i couldnt find the cd so i burned a new one using the same hardware and software as the first cd i burned and now i get the stupid parse error.. wasted about 5 cds and thought about it so i did some bong hits and realized hmmmm i know where the cd is so i found the first one installed xp and it works fine… firgure that out.. oh well f@ck bill gates. by the way even when i got the parse error xp worked better than anything mac or apple has ever put out who the hëll would want a mac piece of shìt (well except for the government)
I had a problem with the VCTRL.MAN file
I was getting the manifest error on line 16
I looked at the file to make sure it wasn’t corrupt, and it wasn’t. I tried the method mentioned before about copying the files to a floppy and that worked.
simply copy the file structure from I386/ASMS/6000/ and so on…. inlcude all the VCTRL files inluding the dll’s and whatnot as well as all the CONTROL.MAN files
boot without the cd-rom and when asked to locate the files type A:I386
this worked for me and hopefully it will work for anyone else with the VCTRL problem.
Tip for VMWare users – if you get this message while trying to install XP Pro as a guest, close down your VM and check “Enable raw access” to the Cd/DVD.
Ta just wot i wanted cos my contols.man file was corrupt and the original cd was at work
I was getting the wonderful controls.man CRC error on my just out of the shrink wrap XP PRO OEM CD. At first I though all my nice new hardware was suspect, but thankfully all that is great. Anyway I replace the very old 8X CD-ROM with an borrowed brand new Samsung DVD reader and bang, it works like a champ. I guess better readers can overcome MS’s cheap CD presses!
Just like all of you…
I got exactly the same message as peter (look for [Posted by: peter from 132.238.187.69 on March 2, 2003 11:58 AM]).
To all who have this problem, remember this: WinXP Setup seems very sensitive to CD media and/or readers!
My little story. I mounted myself a new PC with recent components:
-MB Asus P4P800 Deluxe
-P4C 2.4Ghz (Intel cooler, too noisy)
-2x256Mb TwinMos PC3200
-ATI 9500 pro
-Maxtor 80Gb (6Y080L0)
-DVD-Rom Samsung (SD-616Q, *very* noisy, unacceptable for me; if someone has a suggestion for a RPC1 and silent DVD drive, thanks)
-Antec black case with 380W
-wireless Logitech combo key/mouse
On my first attempt to install WinXP, Setup wasn’t even able to see the Maxtor hard disk. It seems it was the fault of the Asus MB BIOS (was 1004) which I upgraded to 1006 (needed to borrow a floppy drive for this: I didn’t buy one for this new PC!)
Then the Setup could start… and stop after the first reboot (you know, at 39 minutes remaining). I tryed 3 times, changing BIOS settings between them. Then I looked on internet and I found this page. Obviously I began to doubt about the CD copy, but it appeared to contain all needed files under the ASMS/6000/MSFT folder with the correct content. So I tryed the CD on another computer (an old Dell with P2/450): same problem. Finally I burned a new CD-R and the problem gone. In brief, success story!
Thanks Richard for this page.