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…
Thankyou, Thankyou, Thankyou!
Used your text from the start for controls.man
Created a cd with just the i386 directory, poped it in just after winXP restarted setup(after the obligatory parse error and reboot) and the install went along like it was DESIGNED for a two disc set.
Now to add the other 1/2 gig of memory to make my new os a happy camper
can anyone send me CONTROLS.MAN file but not of folder 6000 but of foler 60100. I would appretiate if anyone could send me the file in my email as soon as possible my email is sachindra@mountdigit.com
Thanks,
I’m having the gdiplus.man problem, but the thing is, I only ran setup so i could repair some files, and now I can’t finish booting my computer without setup trying to run again.
Is there not any way to just keep setup from continuing and get back into my machine?
A very helpfull thread. Didnt help me to solve the CONTROLS.MAN problem here but it showed me what it wasn’t. The computer is a Dell C600. Everything above was tried but to no avail. I knew my burn(ed) XP ISO’s were OK but still the parse error. Eventually I got XP to install by deleting the suspend to disk partition. A flawless install followed.
ALL YOU NEED IS A DIFFERENT COPY OF XP! THATS IT! TRUST ME!
FYI… after reading this post and feeling too lazy to copy and burn another CD, I simply put the controls.man file on a floppy disk in the appropriate \i386 directory structure. Then all I had to do was remove the install CD, let the installation restart and point it to the floppy drive. Once it got past that point, it prompted me for the CD again and I put the install disk back in the drive and… wala!
Absolutely Genius … It’s now at least a year after this thread was started and I am thrilled that I was able to use the “Floppy” method to get my software going ….
Thanks Richard !!
~oh yeah.. floppy solution all the way~
MY BAD>> IT WAS LENI WHO CAME UP WITH IT!! sry!
This is just my experience…
I just came across the SXS.DLL manifest error for the first time. This might not be the same solution for everyone, but for me it was a hardware problem. After I swapped out memory and a CD drive I had no problems with XP. This is the same CD stored in a jewel case that I’ve used numerous times before. Likewise I had similar blue screen and install problems on the same system attempting a W2K install. Therefore, for all those frustrated while trying to get a clean XP install, try changing memory modules. IT’s worth a shot.
Matt