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…

If you liked this, you might also be interested in:

Responses

181 Responses to “Manifest Parse Error…”

Pages:« 19 10 11 12 13 14 15 16 [17] 18 19 » Show All

  1. Response #161
    Eef (IP) on October 21st, 2003 at 2:31 pm

    THANK YOU ALL!!!!! To keep my story short, It definitely helped me. I faced so many problems.
    The BÙGGÊR in this story is the CONTROLS.MAN file, which you need to patch according to the (many) instructions above.

    Regards
    Eef

  2. Response #162
    GMTOM (IP) on October 27th, 2003 at 1:56 am

    I came across this problem last week formatted my hard drive several times and couldn’t get a clean install without this manifest parse error. I took my hdd drive out and checked what files where on it, found the recycled folder with a fair bit in it, deleted each item individually then FDISK and put the drive back in original machine, used my cd/rw dive instead of my DVD rom formatted and hey presto a complete installation without errors. I don’t know too much on the technical side but it worked for me. Hope it’s of help to you.

  3. Response #163
    JacksoN (IP) on October 28th, 2003 at 2:13 pm

    Well, the story starts a few weeks back. I lent my good copied version of XP to a friend, but then he kinda lost it :\ So, I was stuck without an XP disc (which I really wanted to have). Now, we all know how M$’s products have a very unpredictable stability, so I really needed to have a copy of XP handy so if anything did happen, BINGO it would be fixed.

    So anyway, I downloaded an ISO of XP PRO, and I had heard about this error before (so i checked the ISO and the controls file was ok). Burnt it and guess what…the directory that controls.man was in wouldn’t even load. So I tried it again..and again - this time on 2x speed…both times failing (same thing happening).

    So I extracted the contents of the ISO (using Undisker) and then proceeded to burn the files using Nero 5 on 4x speed. I then did data verification..Nero said everything was fine. I was a bit sketchy with this result so I checked out controls.man with Notepad..BINGO everything there! I haven’t had to reinstall Windows as of yet, but I’m assuming the disc is in working order (tested it by installing some Windows components).

    I hope this story helps anyone out there having trouble :)

  4. Response #164
    tomcat (IP) on November 6th, 2003 at 12:17 pm

    I only have copied winxp corporate edition cd.
    would someone pls send me all those manifest files or contents of files?
    \I386\ASMS\1000\MSFT\WINDOWS\GDIPLUS\GDIPLUS.MAN
    \I386\ASMS\5100\MSFT\WINDOWS\SYSTEM\DEFAULT\DEFAULT.MAN
    \I386\ASMS\6000\MSFT\VCRTL\VCRTL.MAN
    \I386\ASMS\6000\MSFT\WINDOWS\COMMON\CONTROLS\CONTROLS.MAN
    \I386\ASMS\7000\MSFT\WINDOWS\MSWINCRT\MSWINCRT.MAN

    thank you in advance

  5. Response #165
    12heineken (IP) on November 6th, 2003 at 4:13 pm

    Here’s my story. I have a legitimate copy of XP Home ed. in the form of a restore CD for my Emachines rig. It’s in Ghost format and computer-model-sensitive. I wanted to install XP in my older rig to test it, and came upon an info-site that instructed me to just copy the I386 folder outta my XP-equipped rig instead of worrying how to extract it from the disks and remove unwanted files. So I copied the I386 folder to a cheap Imation blank using the XP burning software and the CDWriter in my Emachines rig. I formatted my old 450’s HDD and popped in the I386 CD. It asked me if I wanted to enable SmartDisk or something like that. It sait it would greatly improve the performance of that stage of setup. I said Nah and just ignored it. It took 24+ hours to copy to the HD! several files wouldn’t copy, like the cyclad/cyclom inf’s - typical for a copy CD. Then I had the option to Change the File system to NTFS, so I opted for it, and XP copied to the HD for a 2nd time, but only took a few minutes this time. Fast-forward to the install-I get an error about XP not being able to complete setup because of a mismatch. There was no mention of “parsing” or anthing else, just something about the manifest catalog. I clicked the log button to discover that it was a problem in “line 4″ of the CONTROLS.MAN file. Fast-forward to my Google-search leading me here-I’m reading about all of these conflicting accounts, most of which support or debunk the CONTROLS.MAN issue. I checked the file on my cd. It was fine. What do I do now? I keep readin. I read about copying the file to a floppy and waiting for setup to ask me to manually search for the file if I take out the CD and reboot, then I tell it to look in the floppy. Hmm-ok-lets try that. I yoink out the CD, reboot and wait for it to look for the file, then not find the file, then ask me to track it down. BANG! the sonofabitch finishes setup without a hitch! IT DIDN’T ASK ME FOR THE FILE. It was like the CD was getting in the way of the identical file already on the HDD. WTF? Anyway, that’s my XP-copy story, try yankin the cd and rebooting if you haven’t done so already. I have to report that it seems less stable than my fast fast rig with OE XP-maybe due to a slower machine and less ram…whoknows. It works 90% fine. I’m Happy

  6. Response #166
    carlitos (IP) on November 18th, 2003 at 8:24 pm

    I have a Gateway Solo 1200 laptop without a recovery disk, the hard drive have been formatted, i also have a copied XP cd and i also get a manifest parse error, I tried to downgrade to win2k pro, it works but my display is not right, my network card doesnt work, and i dont have sound, does anyone know how i can get my drivers, without going to gateway since they are charging me $190 for a recovery disk.

  7. Response #167
    Char (IP) on November 19th, 2003 at 9:38 pm

    You are a GOD !! Thank you very much for the advise on the Manifest Parse Error - the advise to copy/replace the controls.man files worked perfectly. I made a new copy of Windows XP Pro following the step-by-step instructions here: http://www.geocities.com/zrantheus/ (really easy!)

    I have one note to make, however, for those of you out there getting ready to follow Richard’s directions…follow them to a “Q” and make sure the files get put where he tells you (don’t make the mistake I did and attempt to copy the Windows XP files to a different hard drive other than the c:\temp …it won’t work!!)Keep up the great advise Richard!! Thanks again!

    P.S. - I used the Roxio Easy CD Creator program for MY copy needs & it worked like a charm (but you still need to follow the step-by-step directions…)

  8. Response #168
    Jim (IP) on November 30th, 2003 at 11:42 am

    I am having the problem of ” The file “asms” on Windows XP Pro CD-ROM is need. Type the path where the file is located and the click O

    I have done everything that I was supposed to but I cannot get it to work. Someone said in an earlier post about a floppy disk with the tree. How do you do that and please be specific. I have been working on this forever.

    If some files are needed please eamil them to me jimflagg@sbcglobal.net

  9. Response #169
    Jim (IP) on December 2nd, 2003 at 7:03 am

    I got it to work. I just burned it to the CD at a slower speed and did what Rob said at the top. Thanks for your help.

  10. Response #170
    joe (IP) on December 4th, 2003 at 11:54 am

    Thank you this worked great.
    I followed the steps on this page and it worked like a champ.
    http://www.geocities.com/zrantheus/

Pages: « 19 10 11 12 13 14 15 16 [17] 18 19 » Show All

Contribute to the Conversation: