sysprep giving an odd error ?

[stickzilla]

I've never seen this one, so its really messin with me.

I'm building an image for a tablet pc (to only be used with the same tablet model). Everything is fine until I get to the point where I am sysprepping.

I run sysprep, choose my options (run minisetup, reseal) and hit Ok.

After a few seconds it pops up with an error that it was "An error occurrred while trying to update your registry unable to continue" and then "reseal failed !"

Absolutely nothing shows up in the Event Viewer, and after googling this problem a bit, I could only find solutions catering to some kind of MassStorageDevices error.

I've toggled turning the loading of mass storage devices off and on...as well as ran a command line of \sysprep.exe -bmsd to allow the machine to generate the inf information for ALL available mass storage devices.

This popped my sysprep.inf file up to 38k....so I tried running sysprep again, and after 30 min of chugging along, the same error popped up causing it to fail.

Any ideas ?

Here is my sysprep.inf in case anybody cares. And yes, our W drive exists....trust me thats not my call, this is based on somebody else's previous setup here.

;SetupMgrTag

[unattended]

OemSkipEula=Yes

TargetPath=\WINDOWS

ExtendOEMPartition=1

ResetSourcePath=W:\INSTALL\WINXP

InstallFilesPath = c:\sysprep\i386

OemPreinstall = Yes

OemPnPDriversPath="windows\inf"

DriverSigningPolicy=Ignore

[GuiUnattended]

AdminPassword=

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=20

OemSkipWelcome=1

OEMDuplicatorstring="blah"

[userData]

ProductID=

FullName="my stuff"

OrgName="my org"

[setupMgr]

DistFolder=c:\sysprep\i386

DistShare=windist

[RegionalSettings]

LanguageGroup=1

[Display]

BitsPerPel=32

Xresolution=1024

YResolution=768

Vrefresh=70

[identification]

JoinDomain=mydomain

; JoinWorkgroup=Workgroup

[Networking]

InstallDefaultComponents=No

[NetAdapters]

Adapter01=params.Adapter01

[params.Adapter01]

INFID=*

[NetClients]

MS_MSClient=params.MS_MSClient

[NetServices]

MS_SERVER=params.MS_SERVER

[NetProtocols]

MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]

DNS=Yes

UseDomainNameDevolution=No

DNSServerSearchOrder="mydomain"

EnableLMHosts=No

AdapterSections=params.MS_TCPIP.Adapter01

[params.MS_TCPIP.Adapter01]

SpecificTo=Adapter01

DHCP=Yes

NetBIOSOptions=1

[GuiRunOnce]

Command0="c:\\INSTALL\\mes.cmd"

Edited March 3, 2006 by stickzilla

[Jurac]

Getting the same error .... No one wants to tackle it I guess ....

[richard.seibert1]

I had the same problem. What I found out is that my drivers in my sysprep were not located on the machine. Make sure you have the drivers in the folder located where you specify in the .inf file

[JakeLD]

First, this is not a valid path

OemPnPDriversPath="windows\inf"

It should be

OemPnPDriversPath=%WinDir%\inf

You will get this error when a path is invalid specially in the mass storage section.

[Mordac85]

If the only location you have for drivers is %WinDir%\inf, you do not have to specify it in OemPnPDriversPath since that is the default.

If you do have custom drivers defined check to make sure you didn't alter the path structure defined in the driver inf. I normally delete all the helper app crap and platform version I don't need then just have the drivers in the root with the inf. But I have to review the inf/oem files to make sure it didn't reference the files in their previous subdirectory.

[Flip1001]

I could never get a tablet pc to work with sysprep either. I found out why in my circumstance it did not work, however. I was trying to sysprep a computer that had already been sysprepped in the first place. The laptop has built in recovery software that syspreps the system when you tell it to reformat your comp and start from scratch. You have to work on a computer that was installed by a regular installation.