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.