Page 2 of 2

Re: Rawr: SB-E & x79 Build

Posted: Wed Oct 03, 2012 10:44 am
by apertur3
Forge wrote:
That's a lovely machine. Looks almost identical to my much-loved dc5800 SFFs.

I work from observations and my gut, as opposed to Ryu's extensive documentation, so please feel free to disregard my comments...

Generally when I see messages like that, it means that the preinstall OS and the bootloader are no longer configured correctly to each other. In particular, on machines configured that way, with an OEM-altered OS, it's hard to recreate their changes.

I might be able to set up one of my dc5800s and run the OS restore disks against it, get a factory boot partition for you, but it likely wouldn't match well enough to work either.

Back to you, Ryu!


I appreciate it - I'm up for trying just about anything at this point. I was afraid of the possibility that it might be because of special OEM customizations.
Though these are work machines, I will be building a new Ivy Bridge system for home when the parts come in a couple of weeks as an upgrade from my Core 2 Quad - and I'd love to employ this method to avoid having to reinstall everything, at least at first.

Re: Rawr: SB-E & x79 Build

Posted: Wed Oct 03, 2012 3:21 pm
by Ryu Connor
It is most likely a 3rd party background service that is causing the machine to hang.

See if this link helps you find an error log that more clearly defines the issue and then return to us. :)

Link

and

Link

Re: Rawr: SB-E & x79 Build

Posted: Fri Oct 05, 2012 5:16 pm
by apertur3
Ryu Connor wrote:
It is most likely a 3rd party background service that is causing the machine to hang.

See if this link helps you find an error log that more clearly defines the issue and then return to us. :)

Link

and

Link


Thank you, Ryu. Can you tell me how I can access the "$windows.~bt\Sources\Panther" directory, since apparently logs are written to that location before setup can access the drive? Correct me if I am wrong, but it would seem that if setup could not access the drive, or if it had to write logs, they would be to a temp location a.k.a., a RAM drive. Would this be a good place to start looking, and if so, how would one gain access to it?

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 10:34 am
by Ryu Connor
In your instance setup has accessed the drive.

A copy of Windows PE should be able to reach the location (\Windows\Panther) or even using a Windows DVD, choosing to repair the install and selecting the Command Prompt.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 11:04 am
by apertur3
Ryu Connor wrote:
In your instance setup has accessed the drive.

A copy of Windows PE should be able to reach the location (\Windows\Panther) or even using a Windows DVD, choosing to repair the install and selecting the Command Prompt.


OK. I used "start notepad setupact.log" to check the most common log file in the \Windows\Panther directory, and found this:



2012-10-02 12:08:12, Info [0x0f0080] SYSPRP LaunchDll:Found 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'; executing it
2012-10-02 12:08:12, Info capisp.dll::CheckIFCryptoSysPrepSpecialized: returning 0
2012-10-02 12:08:12, Info capisp.dll::CryptoSysPrep_Specialize: assigned CAPI machine guid "b84907e0-9609-49e3-84d4-9c2becf8a1e6"
2012-10-02 12:08:12, Info capisp.dll::DisableAdministratorIfApplicable disabled the admin account.
2012-10-02 12:08:12, Info capisp.dll::CryptoSysPrep_Specialize: returning 5
2012-10-02 12:08:12, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]
2012-10-02 12:08:12, Info IBS Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
2012-10-02 12:08:12, Info IBS Callback_Specialize: Specialize return: [5]
2012-10-02 12:08:12, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x5
2012-10-02 12:08:12, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not configure Windows to run on this computer's hardware.]
2012-10-02 12:32:14, Info [0x070042] DIAG CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
2012-10-02 12:32:14, Info DIAG CallBack_DiagnosticDataSend: Setup was started from Phase 4. Disabling Diagnostics [DiagnosticDataSend] in this scenario
2012-10-02 12:32:14, Info [0x090095] PANTHR WdsExitImmediate called! Execution will stop, and the queue won't be saved.
2012-10-02 12:32:14, Info IBS Callback_Specialize: Exit.
2012-10-02 12:32:14, Info [0x09008c] PANTHR SeqExecute -- stopping, since WdsExitImmediate() was called
2012-10-02 12:32:14, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-10-02 12:32:14, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-10-02 12:32:14, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-10-02 12:32:14, Info PANTHR DeleteCriticalSection for pExecQueue->csLock;
2012-10-02 12:32:14, Info [0x0605a6] IBS Requested UI to hide the language and locale selection pages.
2012-10-02 12:32:14, Info [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
2012-10-02 12:32:14, Info [0x0601d7] IBS InstallWindows:Error Type = 3211266
2012-10-02 12:32:14, Info [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.
2012-10-02 15:39:25, Info [0x0601c1] IBS InstallWindows:Install Path = C:\Windows\system32\oobe
2012-10-02 15:39:25, Info [0x0601c2] IBS InstallWindows:Setup Phase = 4
2012-10-02 15:39:25, Info [setup.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE] --> [IMAGE_STATE_UNDEPLOYABLE]
2012-10-02 15:39:25, Info [0x0601ee] IBS PrepareSetupForFirstBootPhase:Working directory is [C:\Windows\Panther]; we are continuing an installation
2012-10-02 15:39:25, Info IBS PrepareSetupForFirstBootPhase:Passed drive-letter assignment sanity check.
2012-10-02 15:39:25, Info [0x0601cb] IBS InstallWindows:Continuing Setup after completing WinPE phase. Working directory = C:\Windows\Panther
2012-10-02 15:39:25, Info [0x0601ce] IBS Setup has started phase 4 at 2012-10-02 15:39:25
2012-10-02 15:39:25, Info [0x0601cf] IBS Install source is C:\Windows\system32\oobe
2012-10-02 15:39:25, Info [0x0601d0] IBS Build version is 6.1.7600.16385 (win7_rtm.090713-1255)
2012-10-02 15:39:25, Info [0x064041] IBSLIB CreateSetupBlackboard:Opening existing blackboard path is [C:\Windows\Panther\SetupInfo] Setup phase is [4]
2012-10-02 15:39:25, Info [0x090008] PANTHR CBlackboard::Open: C:\Windows\Panther\SetupInfo succeeded.
2012-10-02 15:39:25, Info [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [C:\Windows\Panther\SetupInfo]
2012-10-02 15:39:25, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [].
2012-10-02 15:39:25, Info IBS InstallWindows:Setup architecture is [x64]
2012-10-02 15:39:25, Info [0x0601d4] IBS InstallWindows:Restarting Queue. Setup Phase = 4
2012-10-02 15:39:25, Info PANTHR InitializedCriticalSection for pExecQueue->csLock;
2012-10-02 15:39:25, Info [0x09001c] PANTHR Couldn't find queue 'MainQueueOnline' in contents file
2012-10-02 15:39:25, Info [0x09002a] PANTHR Could not locate saved 'MainQueueOnline' in working directory
2012-10-02 15:39:25, Info PANTHR DeleteCriticalSection for pExecQueue->csLock;
2012-10-02 15:39:25, Info [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
2012-10-02 15:39:25, Error [0x0601d6] IBS InstallWindows:WdsExecuteWorkQueue failed!!![gle=0x00000006]
2012-10-02 15:39:30, Info [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.



researching it now...

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 11:36 am
by Ryu Connor
Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]


Link

Jonathan Hall wrote:
I may have had several factors causing the problem, but the key for me was disabling Kaspersky's Self Defense prior to sysprepping. Try waiting until after the sysprep to install your AV.


When looking up failed deployment problems, it frequently returns to AV software being the cause of woe. Looks like this may be the responsible issue here as well.

I'm concerned this will be a longshot to fix once the image has been captured. You might could try mounting the .wim file and renaming the AV service files causing them to fail, but this is a situation where you may have to start over. :(

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 11:44 am
by apertur3
Ryu Connor wrote:
Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]


Link

Jonathan Hall wrote:
I may have had several factors causing the problem, but the key for me was disabling Kaspersky's Self Defense prior to sysprepping. Try waiting until after the sysprep to install your AV.


When looking up failed deployment problems, it frequently returns to AV software being the cause of woe. Looks like this may be the responsible issue here as well.

I'm concerned this will be a longshot to fix once the image has been captured. You might could try mounting the .wim file and renaming the AV service files causing them to fail, but this is a situation where you may have to start over. :(


yes, I was just reading that one as well :) thanks!

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 1:46 pm
by apertur3
Good news:

Image

A couple of the posts in this thread helped me, namely the ones about setting the GeneralizationState key in HKLM\SYSTEM\Setup\Status\SysprepStatus to 7 (it was on 4), and navigating to the OOBE folder and running msoobe.exe. I can't help but wonder though if I "skipped over" any crucial steps in the installation process that will come back to haunt me later, though... Any thoughts? I thought that sysprep/generalize was supposed to strip out all drivers from the image. Yet, when I open Device Manager, there is not a single unidentified device - even audio was working on first boot! I remain suspicious.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 2:49 pm
by Ryu Connor
Based on where you were in the setup the installation of hardware was complete.

The image purged all installed instances of the hardware, but that doesn't mean it purges the drivers themselves. The drivers remain in the driver store and can be used to re-install the hardware during the hardware detection phase.

If you don't want that you'd need to use pnputil or DISM to purge the drivers from the driver store.

I suspect any issues you might have will be with the service setup of the machine. There is damage, but whether or not it will impact you is harder to say. It might all be fixable once you find it.

If this is meant for a home environment, I wouldn't sweat it. If this is meant for a production environment I'd suggest starting over, determining what service broke the setup, removing it, and then capturing the new fresh image.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 3:07 pm
by apertur3
Ryu Connor wrote:
Based on where you were in the setup the installation of hardware was complete.

The image purged all installed instances of the hardware, but that doesn't mean it purges the drivers themselves. The drivers remain in the driver store and can be used to re-install the hardware during the hardware detection phase.

If you don't want that you'd need to use pnputil or DISM to purge the drivers from the driver store.

I suspect any issues you might have will be with the service setup of the machine. There is damage, but whether or not it will impact you is harder to say. It might all be fixable once you find it.

If this is meant for a home environment, I wouldn't sweat it. If this is meant for a production environment I'd suggest starting over, determining what service broke the setup, removing it, and then capturing the new fresh image.


Back to the drawing board, then, I guess. I would like this to go off without a hitch, as I am sure I will have many similar systems to deploy in the future. The error log is cryptic at best, though - it doesn't seem to reference a specific service. It's going to be horrible if I have to go through the services one by one, capturing an image every time.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 3:16 pm
by apertur3
Here's another hunch as to what the problem may be: Has this image exceeded the rearm limit, because it was originally an OEM image?

Image

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 3:36 pm
by Ryu Connor
Uggh.

Yeah, you can't /generalize that.

I suspect HP did that by reusing that image multiple times.

It is possible to have sysprep SkipRearm. You can find a handy guide here.

SkipRearm was meant for situations where the hardware was the same. The retained activation status isn't going to be kept across different hardware.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 3:56 pm
by apertur3
Ryu Connor wrote:
Uggh.

Yeah, you can't /generalize that.

I suspect HP did that by reusing that image multiple times.

It is possible to have sysprep SkipRearm. You can find a handy guide here.

SkipRearm was meant for situations where the hardware was the same. The retained activation status isn't going to be kept across different hardware.


I actually consider this to be good news, despite the obvious problem here and its implications. I was beginning to think that there was something seriously wrong. This makes me optimistic about my C2Q -> IVB upgrade at home in the next couple of weeks.

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 10:24 pm
by BIF
Sorry to toss an anchor in here, but I want to thank you both/all for posting this history.

I still have quite some time before I pull the trigger and begin to order hardware, and I have not yet thought about whether or not I might need to use this procedure, but it is nonetheless a very good timeline for somebody like myself. I finally kept my promise to myself and sat down yesterday to read this thread in detail. I don't know what I enjoyed more, the thread or the tacos I ate while reading it.

And they were very good tacos, I assure you! :P

Re: Rawr: SB-E & x79 Build

Posted: Mon Oct 08, 2012 10:37 pm
by apertur3
BIF wrote:
Sorry to toss an anchor in here, but I want to thank you both/all for posting this history.

I still have quite some time before I pull the trigger and begin to order hardware, and I have not yet thought about whether or not I might need to use this procedure, but it is nonetheless a very good timeline for somebody like myself. I finally kept my promise to myself and sat down yesterday to read this thread in detail. I don't know what I enjoyed more, the thread or the tacos I ate while reading it.

And they were very good tacos, I assure you! :P


Glad that you were helped! Though I think all of the credit goes to Ryu, and his incredible attention to detail, as well as his willingness to help.

Re: Rawr: SB-E & x79 Build

Posted: Fri Oct 12, 2012 10:05 pm
by apertur3
another question: when you used PNPutil, you had obviously already applied the image - were you booted into WinPE when you were installing new drivers into the driver store?

Re: Rawr: SB-E & x79 Build

Posted: Sun Oct 14, 2012 1:08 am
by apertur3
Well, I did it. New system is up and running smoothly. WHAT A DIFFERENCE from my old hardware. WOW!
Image

Re: Rawr: SB-E & x79 Build

Posted: Sun Oct 14, 2012 2:20 am
by Ryu Connor
apertur3 wrote:
another question: when you used PNPutil, you had obviously already applied the image - were you booted into WinPE when you were installing new drivers into the driver store?


No. PNPUtil cannot be used for an OS in an offline state. To add drivers to the driver store of an offline OS (including directly into a .WIM image), you must use DISM.

apertur3 wrote:
Well, I did it. New system is up and running smoothly. WHAT A DIFFERENCE from my old hardware. WOW!
Image


Congrats!