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…
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.
Copied the data and created a new controls.man file and reburnt the cd with all the contents including the new man file but the man file will not run in dos. Any suggestions?
I actually went out and bought WinXP Home Edition today, only to get the same EXACT error ksuchoc is getting. Is there a solution to this?
Having not pirated XP, I took the original CD back to Best Buy today and received a new copy. XP installed off the new CD without a hitch…it seems that the original CD was faulty, right off the shelf. Now I see why people truly hate M$.
Being a computer builder and having installed XP Pro on many machines (new and used) from the same disk, it was, to say the least, extreemely frustrating to get the ‘manifest’ error. I used the 6 floppy disk boot for XP Pro and finished up with the CD. Worked well installation went without a hitch.
The version of CONTROLS.MAN in the .ISO file seems to be intact so the problem occurs when the ISO is burnt. A previous post mentions that these *.MAN files have longer paths than others on the CD. Anyone have any other ideas as to what could be the cause?
From the comments above it seems there is no common factor - different burning software, different hardware setups, pirated and legal versions all seem to be prone to the problem.
Could it really be some sort of copy protection by M$? I don’t see how it can be but then i’m not an expert in .isos and CD burning…. this is bugging me.. I want to know what is happening!
Ok it is my turn. I received the GDIPLUS.MAN error on line 4. This is after I (1) copied my XP to my harddrive; (2) revised all my .MAN files; (3) burned a CD at 2x with Easy Creator Version 4; and (4) banged my head against a wall until I was unconscious. What do I do???