Process1_initialization_failed

[teddy0682]

Has anyone gotten a blue screen after the install with "PROCESS1_INITIALIZATION_FAILED" as the title. This occurs during the windows boot screen while heading into the second part of the install, where it configures the time zone and everything else. Can you help me get rid of this? Thanks.

BTW... this is Windows XP with service pack 2 slipstreamed and I have never seen this message before with our service pack 1 disc. I followed the guide and used nLite to slipstream sp 2.

[icnocop]

Has anyone figured out how to resolve this?

I am experiencing the same issue with Windows XP Pro, deployed using tftpd32 as RIS.

Thank you.

[icnocop]

tftpd32 as ris + windows share with xp pro files, trying to remotely deploy windows xp pro (without any service packs integrated) on vmware workstation 6.5, but i get a process1_initialization_failed bsod right after the xp setup goes into gui mode.

i notice that the remote machine connects to the windows share from the event viewer.

Event Type: Failure Audit

Event Source: Security

Event Category: Account Logon

Event ID: 680

Date: 5/11/2009

Time: 1:21:36 PM

User: NT AUTHORITY\SYSTEM

Computer: AMD64-PC

Description:

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

Logon account:

Source Workstation: \\192.168.1.100

Error Code: 0xC0000064

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Account Logon

Event ID: 680

Date: 5/11/2009

Time: 1:21:36 PM

User: AMD64-PC\Guest

Computer: AMD64-PC

Description:

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

Logon account: Guest

Source Workstation: \\192.168.1.100

Error Code: 0x0

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

192.168.1.100 is the ip address that the remote machine gets from tftpd32.

I have this setup as described in "guide_from_base_install_for_fully_unattended_windows_installs_using_tftpd32.doc".

netmon log

1:21:37 PM 5/11/2009 272890 741.314453 192.168.1.100 192.168.1.3 TCP TCP:Flags=......S., SrcPort=1025, DstPort=Microsoft-DS(445), PayloadLen=0, Seq=1701493885, Ack=0, Win=64240

1:21:37 PM 5/11/2009 272891 741.314453 192.168.1.3 192.168.1.100 TCP TCP:Flags=...A..S., SrcPort=Microsoft-DS(445), DstPort=1025, PayloadLen=0, Seq=933292918, Ack=1701493886, Win=16384

1:21:37 PM 5/11/2009 272892 741.319336 192.168.1.100 192.168.1.3 TCP TCP:Flags=...A...., SrcPort=1025, DstPort=Microsoft-DS(445), PayloadLen=0, Seq=1701493886, Ack=933292919, Win=64260

1:21:37 PM 5/11/2009 272893 741.336914 192.168.1.100 192.168.1.3 SMB SMB:C; Negotiate, Dialect = PC NETWORK PROGRAM 1.0, LANMAN1.0, Windows for Workgroups 3.1a, LM1.2X002, LANMAN2.1, NT LM 0.12

1:21:37 PM 5/11/2009 272894 741.336914 192.168.1.3 192.168.1.100 SMB SMB:R; Negotiate, Dialect is (#5)

1:21:37 PM 5/11/2009 272895 741.355469 192.168.1.100 192.168.1.3 SMB SMB:C; Session Setup Andx, Account = ބ衑權5; Tree Connect Andx, Path = \\192.168.1.3\RICHARD3, Service = ?????

1:21:37 PM 5/11/2009 272896 741.546875 192.168.1.3 192.168.1.100 SMB SMB:R; Session Setup Andx; Tree Connect Andx, Service = A:

1:21:39 PM 5/11/2009 272897 743.964844 192.168.1.3 192.168.1.100 SMB SMB:R; Session Setup Andx; Tree Connect Andx, Service = A:

AMD64-PC is 192.168.1.3

RICHARD3 is the network share

My directory structure is as follows:

D:\MyRIS\richard3\ (the network share)

\$OEM$\$1\Drivers\Nic

vmware-nic.cat

vmware-nic.inf

vmxnet.cat

vmxnet.inf

vmxnet.sys

\DOCS

\I386

\pxelinux.cfg

default

\SUPPORT

\VALUEADD

AUTORUN.INF

mboot.c32

menu.c32

NTLDR

pxelinux.0

README.HTM

SETUP.EXE

startrom.n12

startrom.n12ntdetect.com

startrom.n12winnt.sif

tftpd32.exe

tftpd32.ini

WIN51

WIN51IP

I've attached winnt.sif, that is equivalent to startrom.n12winnt.sif and \I386\winnt.sif.

I've also attached tftpd32.ini.

Thank you.

winnt.sif

tftpd32.ini