Error after sysprep, during reboot

[Tripredacus]

Oh I've found a dandy error in which there is NO answer from The Google! Well there is 1 result but a case of "posting in the wrong place" so no answer that way. I've sent along an email to MS about it, but I'll post it here in case anyone has any idea or it helps them as well.

As per usual, I cannot post all details, suffice it to say, here are the errors:

1. During boot after sysprep, during the "Setup is starting services" phase, I get:

Windows could not finish configuring the system

2. So I go reboot into WinPE and read the log in Panther. It tells me this:

SYSPRP SPPNP: Error 0x3 setting SDDL on driver file C:\Program Files\Analog Devices\Core\smwdmif.dll!

SYSPRP SPPNP: Error 0x3 enumerating locked down files!

Basically, I deployed Win7 on a PC to Audit Mode. I installed a program (Intel Matrix Storage Manager/IATA89ENU.EXE) and run sysprep /oobe /reboot. I create a user, password, name the PC all that fun stuff. Then other changes are made to the PC. I use an answer file for OOBE settings, use this: sysprep /oobe /generalize /unattend:sysprep.xml. This XML has been tested and works fine. I then capture the image and redeploy on a matching system (or reboot the Master PC) and then get the above errors.

As I understand it, this DLL is part of the Intel SoundMAX software package for the Intel integrated audio. However, I hope I am not stuck with a busted up image and I can service it offline to correct the problem.

Anyone have any ideas?

[maxXPsoft]

might try Bing search, returned a lot on that smwdmif.dll. basically use different version

[Tripredacus]

I have tested out this config with another 7 image that uses the same driver as the custom one. It does not occur in this way. So either it is caused by a problem during deployment or the client changed something to cause this. I even tested using the answer file and had no errors.

I was led on a lead that it is a problem with the BCD but we write the BCD during deployment and have no problems with other images.

[cluberti]

0x3 in the log in this location likely is "ERROR_PATH_NOT_FOUND", meaning the file got deleted during sysprep, but for some odd reason sysprep is going back and trying to touch the file or it's registry. Does the SoundMax package install any drivers or services that are running on the system after the installation? It would indicate that the sysprep (for whatever reason) wasn't able to cleanly remove the driver, or information about it, during reseal. Not sure why it's specific to a particular image, but once this happens that image is pretty much toast - you'll have to rebuild. Once you've sealed it and the problem is in place, you aren't going to get out of that loop.

[Tripredacus]

I'll keep that info in mind, but as noted above, I can't recreate the issue using a duplicate system. Its only with the one system, but I am wondering if sysprep is doing additional steps when the image is being put onto a "different" hardware.

[cluberti]

I'll keep that info in mind, but as noted above, I can't recreate the issue using a duplicate system. Its only with the one system, but I am wondering if sysprep is doing additional steps when the image is being put onto a "different" hardware.

If you are running /generalize, then yes it is - there are functions that run on a generalized image when the hardware has changed if /generalize was specified when the machine was sysprep'ed.

[maxXPsoft]

might try using the <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> during Generalize to make it keep the Plug and Play devices

[Tripredacus]

might try using the <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> during Generalize to make it keep the Plug and Play devices

Well unfortunately it is not that easy. I just booted up the PC the image was captured from and it errored out as well. So the generalize on same hardware did it also. However, my tests on other systems have proven that the problem is not with the sound driver and/or generalize. For record keeping purposes, here is the newest driver:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18658&ProdId=2933〈=eng

Which is already the one that is installed during deployment, as this is injected into the WIM. Here are a list of changes to the Master Image before Sysprep /generalize was run. I am wondering if any of these settings could have done something to the driver? It might be impossible to tell!

Stuff I did

1. Set network to Public to enable Firewall

2. Turn off remote assistance

3. Turn on RDP but for any client (the middle option)

4. Set a static IP address

What the client did via RDP

5. Installed 4, 3 I can't list and 1 is Acrobat Reader 9.3 minus Google Toolbar.

6. Installed a printer driver (note, no printers are attached)

7. Set a wallpaper and created and saved a theme*

8. Created a shortcut on Public Desktop to a file that was copied over

9. Changed Folder Options to show file ext for known file types.

10. Changed to Details view for all folders.

11. Changed Start Menu properties concerning what items show up.

What I did after they disconnected

12. unplugged cable from NIC

13. Set IP and DNS to obtain automatically

14. Disabled RDP

15. ran sysprep and then captured the image

So here are my questions.

Is it possible that any of the following uses could cause a problem: RDP or installing a printer driver?

It IS possible that one of the other programs are causing the problem, however I am not sure if the client installed through Programs and Features. They are also aware that sysprep cannot set a theme (setting is depecrated) but they saved it to be chosen later.

Oh I forgot to say, basically the original image is busted so I'm already having to start over.

Update1

I have found the culprit. It is caused ONLY when a Crystal Reports viewer is installed. I cannot determine if this is an official product or developed in house. I did notice it's installer package tried to backdate ATL.DLL and MSVCP60.DLL but Windows 7 did not let the installer replace those files. I verified they were the correct version afterwards. Now as to why this program is doing this, I have no idea.

Edited March 31, 2010 by Tripredacus
Update1