Another sysprep problem after SP2

  • Thread starter Thread starter Johan Arwidmark
  • Start date Start date
Did you run sysprep with the -nosidgen switch?

"An Error Has Been Encountered That Prevents Setup from Continuing"
Error Message When Sysprep Mini Wizard Runs
http://support.microsoft.com/default.aspx?scid=kb;en-us;818171

You can also try deleting the files in
C:\WINDOWS\system32\Microsoft\Protect\S-1-5-18\User
folder before running sysprep

regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net


here is a copy of my sysprep.inf

the administrator account in the image has a blank password


;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20

[UserData]
ProductKey="removed for privacy"
FullName=""
OrgName="TransIT"

[Display]
BitsPerPel=32
Xresolution=1280
YResolution=1024

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[Identification]
JoinWorkgroup=TRANSIT

[Networking]
InstallDefaultComponents=Yes

[sysprepcleanup]


yes i am
Click to expand...
Click to expand...
 
So i update the image i have with sp2, i run the mgr prog ,then i sysprep it
choosing only mini setup. when rebooting the image it says

Fatal Error

An error has been encountered that prevents setup from contining.
Windows is unable to start because the registry could not be updated. to
address the problem contact your manufacturer. windows must shut down now

press ok to view the setup log

LOG FILE CONTENTS:

fatal error
An error has been encountered that prevents setup from contining.
Windows is unable to start because the registry could not be updated. to
address the problem contact your manufacturer. windows must shut down now

i must point out that the system was working perfectly before the sysprep


Thank you in advance.
 
here is a copy of my sysprep.inf

the administrator account in the image has a blank password


;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20

[UserData]
ProductKey="removed for privacy"
FullName=""
OrgName="TransIT"

[Display]
BitsPerPel=32
Xresolution=1280
YResolution=1024

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[Identification]
JoinWorkgroup=TRANSIT

[Networking]
InstallDefaultComponents=Yes

[sysprepcleanup]
 
i think i read in the textfile that is in deploy.cab:


that you cannot run sysprep on a computer that was installed as xp sp1 or
lower and then had sp2 installed by running update.exe.

the file also goes on to say that you can you have slipslip stream an
version into the sysprep i386 directory by using the opk , to get he opk you
must be a system builder and or buy at least a 3pack oem version of xp

there is one more option but i do not have the text file open


thanks any more information anyone has will be greatly appreciated

i am still gonna try your suggestion just to see what happens (call me a
cat)

Hampton


Johan Arwidmark said:
Did you run sysprep with the -nosidgen switch?

"An Error Has Been Encountered That Prevents Setup from Continuing"
Error Message When Sysprep Mini Wizard Runs
http://support.microsoft.com/default.aspx?scid=kb;en-us;818171

You can also try deleting the files in
C:\WINDOWS\system32\Microsoft\Protect\S-1-5-18\User
folder before running sysprep

regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net


here is a copy of my sysprep.inf

the administrator account in the image has a blank password


;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20

[UserData]
ProductKey="removed for privacy"
FullName=""
OrgName="TransIT"

[Display]
BitsPerPel=32
Xresolution=1280
YResolution=1024

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[Identification]
JoinWorkgroup=TRANSIT

[Networking]
InstallDefaultComponents=Yes

[sysprepcleanup]


yes i am

"Johan Arwidmark" <[email protected]>
wrote in message Are you running the new, updated, sp2 version of sysprep?

regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net


On Wed, 11 Aug 2004 14:06:27 -0500, <who cares> wrote:

So i update the image i have with sp2, i run the mgr prog ,then i
sysprep
it
choosing only mini setup. when rebooting the image it says

Fatal Error

An error has been encountered that prevents setup from contining.
Windows is unable to start because the registry could not be updated.
to
address the problem contact your manufacturer. windows must shut down
now

press ok to view the setup log

LOG FILE CONTENTS:

fatal error
An error has been encountered that prevents setup from contining.
Windows is unable to start because the registry could not be updated.
to
address the problem contact your manufacturer. windows must shut down
now

i must point out that the system was working perfectly before the
sysprep


Thank you in advance.
Click to expand...
Click to expand...
Click to expand...
 
I think I fixed it

I went ahead and deleted those files in C:WINDOWS\system32\Microsoft\ProtectS-1-5-18\User before I ran Sysprep

It came up this time, and went all the way through the mini setup with no errors.

Afterwards, I logged on, both with the Admin account and a secondary user account I created for building my profile. Everything appears to be working just fine. I went into various system settings in Control Panel, and was able to adjust anything I needed.

I don't know what else to test, but this appears to have fixed the issue.

Has anyone else tried this and found any problems?
 
sysprep: An error has been encountered that prevents Setup from continuing

Had same problem. And can confirm that your solution works.

I deleted [font=&quot]all files in C:WINDOWS\system32\Microsoft\Protect\S-1-5-18 and its User subdirectory.

Then ran sysprep.

BTW, I am running sysprep on XP SP2 using 'Mini-Setup' and 'regnerate SIDs' options (after generating a sysprep.inf file using setupmgr.exe). The original XP installation was an HP OEM.

thanks for the tip.
[/font]
 
sysprep: An error has been encountered that prevents Setup from continuing

BTW, don't forget that [font=&quot;]the key files in C:WINDOWS\system32\Microsoft\Protect\S-1-5-18 and its User subdirectory are operating system files and you can't see/delete them unless you 'un-hide' them first.
[/font]
 
Same issue on Windows Server 2003 R2 Ent Sp2

I have ran accross the same issue. With windows 2003 R2 SP2 Server. Funny, same pre sysprep snap shot, all i did was change some of the massstorage drivers and snmp strings. But there were three SIDs in each of those folders...

here was what i found, in case anyone else stumbles accross this thread

http://support.microsoft.com/kb/818171
 
Back
Top