Fatal error on boot (using ghost)

[Guest]

Hello.

Using Corporate Ghost 8.0 to create an image of a Dell Dimension 2400 with
XP sp2, sysprep 5.1.2600.2180.

The Ghost client was installed on the workstation, image create task run and
an image was created at the console station. All appeared fine until the
client rebooted - during restart a dialog box declaring "Fatal error: Windows
is unable to restart because the registry could not be updated. To address
this problem, please contact your computer manufacturer. Windows must now
Shut Down."

I rebuilt XP, recovering the original installation, and found the the
sysprep folder a file called cleandrm.log. It contained the following:

**** Begin CleanDRM *************************************************
**
** LogFile : C:\SYSPREP\cleandrm.log
** TimeStamp : 11/3/2004, 12:09:08 PM
**
[Clean registry]
Deleting Machine ID registry value...
Deleting Secure Store registry values...
(default) : deleted
Deleting Data Path registry value...
DataPath : deleted
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
No indiv files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned 0x00000000.
Register drmv2clt.dll: DllRegisterServer returned 0x00000000.
**
**** End CleanDRM ***************************************************


**** Beginning CleanDRM procedure
**
[Clean registry]
Failed to delete machine id.
Failed to delete Signatures.
Deleted Data Path.
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
no indiv key files found
no indiv dll files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned -2147467259.
This tool must be run with admin privleges.
Register drmv2clt.dll: DllRegisterServer returned 0.
**
**** Ending CleanDRM procedure.

After rebuilding the machine, I restored the image to the client machine
using the GhostCast server. After the image was loaded and the system
rebooted, I again received the dialog box "Fatal Error..." as noted above.

I have since rerun this with administrative user permissions at both client
and console stations but it made no difference.

Any clues?

George

 

[Guest]

Hi there,

I had a similar problem with some sysprep images i made but on a SP1 build,
and using Ghost corporate edition 8.0 some machines did it and some didn't it
seemed to be a hit an miss 1/100 machines came up with that error so we
pretty much just replaced the machine as this was a mass XP rollout across
some 7,000 machines.

I think the route of the problem is a BAD build in some cases, if you kept a
pre-sysprep version i would check it over and then re-package it and try
again. also make sure the registry files are not stamped as read only maybe?


not sure if thats much help.

Alex

Hello.

Using Corporate Ghost 8.0 to create an image of a Dell Dimension 2400 with
XP sp2, sysprep 5.1.2600.2180.

The Ghost client was installed on the workstation, image create task run and
an image was created at the console station. All appeared fine until the
client rebooted - during restart a dialog box declaring "Fatal error: Windows
is unable to restart because the registry could not be updated. To address
this problem, please contact your computer manufacturer. Windows must now
Shut Down."

I rebuilt XP, recovering the original installation, and found the the
sysprep folder a file called cleandrm.log. It contained the following:

**** Begin CleanDRM *************************************************
**
** LogFile : C:\SYSPREP\cleandrm.log
** TimeStamp : 11/3/2004, 12:09:08 PM
**
[Clean registry]
Deleting Machine ID registry value...
Deleting Secure Store registry values...
(default) : deleted
Deleting Data Path registry value...
DataPath : deleted
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
No indiv files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned 0x00000000.
Register drmv2clt.dll: DllRegisterServer returned 0x00000000.
**
**** End CleanDRM ***************************************************


**** Beginning CleanDRM procedure
**
[Clean registry]
Failed to delete machine id.
Failed to delete Signatures.
Deleted Data Path.
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
no indiv key files found
no indiv dll files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned -2147467259.
This tool must be run with admin privleges.
Register drmv2clt.dll: DllRegisterServer returned 0.
**
**** Ending CleanDRM procedure.

After rebuilding the machine, I restored the image to the client machine
using the GhostCast server. After the image was loaded and the system
rebooted, I again received the dialog box "Fatal Error..." as noted above.

I have since rerun this with administrative user permissions at both client
and console stations but it made no difference.

Any clues?

George

 

[Guest]

Well, I got curious reading about slipstreamed CDs. I had no idea what it
meant. Turns out that it's the answer, at least to my issue. The bottom
line - when one wants to clone an XP sp2 box, one needs to build that box
from an installation CD with SP2. That's where slipstreaming comes in - one
uses it to create an sp2 installation cd from the service pack and prior cds.

I now have a good, usable image in ghost.

Regards.

George

Hi there,

I had a similar problem with some sysprep images i made but on a SP1 build,
and using Ghost corporate edition 8.0 some machines did it and some didn't it
seemed to be a hit an miss 1/100 machines came up with that error so we
pretty much just replaced the machine as this was a mass XP rollout across
some 7,000 machines.

I think the route of the problem is a BAD build in some cases, if you kept a
pre-sysprep version i would check it over and then re-package it and try
again. also make sure the registry files are not stamped as read only maybe?


not sure if thats much help.

Alex

Hello.

Using Corporate Ghost 8.0 to create an image of a Dell Dimension 2400 with
XP sp2, sysprep 5.1.2600.2180.

The Ghost client was installed on the workstation, image create task run and
an image was created at the console station. All appeared fine until the
client rebooted - during restart a dialog box declaring "Fatal error: Windows
is unable to restart because the registry could not be updated. To address
this problem, please contact your computer manufacturer. Windows must now
Shut Down."

I rebuilt XP, recovering the original installation, and found the the
sysprep folder a file called cleandrm.log. It contained the following:

**** Begin CleanDRM *************************************************
**
** LogFile : C:\SYSPREP\cleandrm.log
** TimeStamp : 11/3/2004, 12:09:08 PM
**
[Clean registry]
Deleting Machine ID registry value...
Deleting Secure Store registry values...
(default) : deleted
Deleting Data Path registry value...
DataPath : deleted
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
No indiv files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned 0x00000000.
Register drmv2clt.dll: DllRegisterServer returned 0x00000000.
**
**** End CleanDRM ***************************************************


**** Beginning CleanDRM procedure
**
[Clean registry]
Failed to delete machine id.
Failed to delete Signatures.
Deleted Data Path.
[Clean DRM folder]
Cleaning C:\Documents and Settings\All Users\DRM...
drmv2.lic : deleted
drmv2.sst : deleted
[Clean indiv files]
no indiv key files found
no indiv dll files found
[Register DRM libraries]
Register drmclien.dll: DllRegisterServer returned -2147467259.
This tool must be run with admin privleges.
Register drmv2clt.dll: DllRegisterServer returned 0.
**
**** Ending CleanDRM procedure.

After rebuilding the machine, I restored the image to the client machine
using the GhostCast server. After the image was loaded and the system
rebooted, I again received the dialog box "Fatal Error..." as noted above.

I have since rerun this with administrative user permissions at both client
and console stations but it made no difference.

Any clues?

George