Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Installation won't complete - Fatal Error 1

Status
Not open for further replies.

cdogg

Technical User
Jul 30, 2001
7,785
US
Hey there, thanks in advance for reading the thread!
[thumbsup2]

Recently, I've encountered the following error message during the install of XP Pro (FAT32):

Fatal Error-
SXS.DLL: Syntax error in manifest or policy file C:\$win_nt$.~ls\I386\asms\6000\MSFT\VCRTL\VCRTL.MAN on LINE 11
A component's file does not match the verification information present in the component manifest



Setup constantly restarts, returning to the same error message. I've tried the following:

- read various M$ support articles
- ran a repair
- ran chkdsk /r
- formatted and tried again
- formatted, copied i386 directory to HD first, then ran Winnt.exe
- replacing VCRTL.MAN from CD to the Temp directory


Nothing has seemed to work, and I'm pretty sure this installation was successful on a different pc. Any ideas? Possibly, can someone list what's on line 11 of their VCRTL.MAN?

Thanks again,
~cdogg


~cdogg

"The secret to creativity is knowing how to hide your sources."
- A. Einstein
 
<?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;yes&quot;?>
<assembly xmlns=&quot;urn:schemas-microsoft-com:asm.v1&quot; manifestVersion=&quot;1.0&quot;>
<assemblyIdentity type=&quot;win32&quot; name=&quot;Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries&quot; version=&quot;6.0.0.0&quot; processorArchitecture=&quot;x86&quot; publicKeyToken=&quot;6595b64144ccf1df&quot;/>

<dependency optional=&quot;yes&quot;>
<dependentAssembly>
<assemblyIdentity type=&quot;win32&quot; name=&quot;Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries.Resources&quot; version=&quot;6.0.0.0&quot; processorArchitecture=&quot;x86&quot; publicKeyToken=&quot;6595b64144ccf1df&quot; language=&quot;*&quot;/>
</dependentAssembly>
</dependency>

<file name=&quot;mfc42u.dll&quot; hash=&quot;d9357dbe54a1f754cd8d662323acdeb100a0b0d1&quot; hashalg=&quot;SHA1&quot;>
<comClass description=&quot;Font Property Page&quot; clsid=&quot;{0BE35200-8F91-11CE-9DE3-00AA004BB851}&quot;/>
<comClass description=&quot;Color Property Page&quot; clsid=&quot;{0BE35201-8F91-11CE-9DE3-00AA004BB851}&quot;/>
<comClass description=&quot;Picture Property Page&quot; clsid=&quot;{0BE35202-8F91-11CE-9DE3-00AA004BB851}&quot;/>
</file>
<file name=&quot;mfc42.dll&quot; hash=&quot;138a2057b090678d865720ed22276b00ede39168&quot; hashalg=&quot;SHA1&quot;/>
<file name=&quot;atl.dll&quot; hash=&quot;60f116cba40bf191e78dd71177de8de79d79c50b&quot; hashalg=&quot;SHA1&quot;>
<comClass description=&quot;Registrar Class&quot; clsid=&quot;{44EC053A-400F-11D0-9DCD-00A0C90391D3}&quot; progid=&quot;ATL.Registrar&quot;/>
<typelib tlbid=&quot;{44EC0535-400F-11D0-9DCD-00A0C90391D3}&quot; version=&quot;1.0&quot; helpdir=&quot;&quot;/>
</file>
<file name=&quot;msvcp60.dll&quot; hash=&quot;0d48860c3fdc649067ae29ef95635443d9d7064d&quot; hashalg=&quot;SHA1&quot;/>





<comInterfaceExternalProxyStub name=&quot;IAxWinAmbientDispatch&quot; iid=&quot;{B6EA2051-048A-11D1-82B9-00C04FB9942E}&quot; proxyStubClsid32=&quot;{00020424-0000-0000-C000-000000000046}&quot; numMethods=&quot;35&quot; baseInterface=&quot;{00000000-0000-0000-C000-000000000046}&quot;/>

</assembly>

That's all my vcrtl.man - line 11, including space lines is <file name=&quot;mfc42u.dll&quot; hash=&quot;d9357dbe54a1f754cd8d662323acdeb100a0b0d1&quot; hashalg=&quot;SHA1&quot;>

cdogg - have you considered it could be caused by a hardware fault?
 
Are you installing it in a cd burner drive? I ran into similar recurring errors installing XP from a burner, switched to my dvd-rom drive and it installed fine.
 
wolluf,
Thanks. It turns out that our files are identical as I suspected. I guess there must be some kind of hardware conflict. I'll go through the hardware compatibility list when I get the chance.

lucasm,
Good suggestion, however copying the i386 folder to the hard drive and running winnt.exe from there produced the same errors. It must be something else.


I'm still open to suggestions if anyone has any...


~cdogg

&quot;The secret to creativity is knowing how to hide your sources.&quot;
- A. Einstein
 
linney,
All due respect...&quot;been there done that&quot;

I've read every line of that thread:
twice!
LOL


And I know how to google!!!!!!!!!!!!!!!!
do you always post as if the poster is inexperienced? No need in this case...


~cdogg

&quot;The secret to creativity is knowing how to hide your sources.&quot;
- A. Einstein
 
try the install from a different CD and see if it isn't a corrupt file on the CD that is transfering over to the harddrive.

low level format may not fix this particular problem....
it wouldn't hurt to try though......
 
Turn off video bios and/or memory caching in your bios if it is turned on.
 
i'm not some huge antipiracy guy or anything, but i ran into the same problem when i used a copy of a copy i downloaded, it seems that clonecd didnt do something right in the duplication proccess,
it was the exact same error, only with disks copied from the origional copy. rooted around and found the &quot;origional&quot; and even though there were some scratches, bam, it worked fine.

just a thought.
 
Well, I was getting the exact error message in my installation of xp pro. And it just so happens that I was using a copy of a copy, just like cnycompguy...
 
I had the exact problem until I read lucasm's post above about putting the XP CD in the CD-ROM instead of the burner. Worked fine after that.
 
Hmm, having exactly the same problems , although the Failure msg change between

Fehler Meldung :SXS.DLL D:\I386\asms\6000\MSFT\VCRTL\VCRTL.MAN ( in Zeile 16 )

and GDIplus.Man ( in line 4 ) still within the asms folder tho !!!

PC: Dual Xeon 3.06 ( 533 )
MB ASUS PC-DL Deluxe
Corsair TwinXL 512MB ( x2 )

Have tried a DVD and a DVD-rw drive now I am trying a CD (24x old ) to see if its a CD error, although I believe the problem to be with the Original MS Win CD . VGA is a standard Radeon 7000 AGP and theres no sound card or other PCI cards.

Has it got something to do with the Promise Raid sys ( Fast-Trak 378 ) or that I am using S-ATA Drives ??

any other tips ??
 
Hi,

after eading the other threads mentioned, I would like to add that itsa an Original OEM CD from Windows no copy, and that as far as I can tell all files are on the cd and not corrupted.

I have however seen that both Failure msgs have the same line ending : hashalg="SHA1"/>

what is this SHA1 ?? could it be the problem
 
its an encryption algorithm

it seems to be a hardware pb, having just googled for 10 minutes ...
people have got round it by:
-changing memory
-formatting HD with a tool to put all 0s
-changing CDRom drive


gdi plus..
you are not alone....

good luck

Aftertaf (david)
MCSA 2003
 
Hello,

Well i was haveing the same problem SXS.DLL during install
and the proble did turn out to be bad memory.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top