Windows could not finish configuring the system...
Hi There,
I have a problem when deploying a Windows image, hopefully someone can help...
I have created and captured a Windows 7 image using the SCCM capture media. It captured all ok and I created the task sequence etc. which is all fine.
I can PXE boot a another computer, select the image and it deploys ok, but when it restarts and does its Windows setup its gets to the 'Setup is starting services' and then comes up with this error -
'Windows could not finish configuring the system. To attempt to resume configuration, restart the computer.'
After a restart it does the same thing.
Any ideas?
Big Thanks!
Max
June 11th, 2012 11:53am
what does the smsts.log file tell you ?
June 11th, 2012 12:15pm
Sorry Niall - I'm new to all this - Where would I find the log?
Thanks,
June 11th, 2012 12:20pm
enable command prompt support in your boot image (see step 4 of
this post), then when imaging, press F8 to bring up a command prompt and browse to c:\windows\ccm\logs and you should see a smsts.log file in there (or in a sub-directory called smstslog)
post the errors from that file here.
June 11th, 2012 12:41pm
Link to the smsts.log file here -
Here
Thanks!
June 11th, 2012 1:19pm
And if you wont find an answer in smsts.log, investigate Application and System logs with Event viewer, because to me it sounds that some OSs service cannot be started. This could be because of a any dervice driver as well.
But study smsts.log first like Niall told :)
June 11th, 2012 1:20pm
are you sure you've added a step to apply network drivers for the hardware in question via an Apply Driver Package step ?
seems like there is no network connectivity here after completing sysprep....
Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="16:14:49.687-60" date="06-08-2012" component="TSManager" context="" type="1" thread="1996" file="libsmsmessaging.cpp:8689">
<![LOG[unknown host (gethostbyname failed)]LOG]!><time="16:14:49.687-60" date="06-08-2012" component="TSManager" context="" type="3" thread="1996" file="libsmsmessaging.cpp:692">
<![LOG[hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8738)]LOG]!><time="16:14:49.687-60" date="06-08-2012" component="TSManager" context="" type="0" thread="1996" file="libsmsmessaging.cpp:8738">
<![LOG[sending with winhttp failed; 80072ee7
June 11th, 2012 2:56pm
Ahh - No I didn't have that in the task sequence.
I have added 'Auto Apply Drivers' - is this correct? Where in the task sequence does it need to go? After 'Apply Operating System' and before 'Apply Windows Settings'?
Thanks!
June 11th, 2012 3:00pm
after the apply network settings you can have several
Apply Driver Package steps (before the Setup Windows and ConfigMgr step) which are targetted to different hardware based on wmi queries.
June 11th, 2012 3:54pm
Did Max solve this? My opinion is, that you can manage with Auto Apply Drivers just fine, you need just to publish all drivers necassary and remember to keep package updated on DP.
June 11th, 2012 11:14pm
Hi - Nope still having the same problem. I have added the Apply Drivers and all the drivers are there and in a package and the DP has been updated. Any other ideas?
Thanks,
June 12th, 2012 12:32pm
I'm sure I had this problem when one of the drivers I was attempting to inject was bad. IIRC, when I had this problem I booted the failed machine into Windows PE, fired up a command prompt and accessed the setupact.log or setuperr.log from the windows\panther\unattend
folder and I could see the problem.
Also, you could try applying a test driver package that ONLY has the network driver within it - and if setup completes then you know you have a driver issue.
June 12th, 2012 4:53pm
Thanks MadLuka - I have found the setuperr.log which had this in it - [windeploy.exe] Failure occured during online installation. Online installation cannot complete at this time.; hr = 0x8007139f
Looking this up it pointed me to this - http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/a113e858-8f9f-414a-8391-53bffb208036 which then pointed me to this - http://forum.kaspersky.com/index.php?showtopic=147099
So it looks like a problem with Kaspersky! I'm going to remove it and then try the capture again.
I will let you know!!
June 13th, 2012 10:05am
I just had this exact same issue except we are using AVG 2013. Couldn't find a way around it either. From now on, I'm going to remove AVG 2013 before running the capture process and just add the AVG application installation as a step in the
task sequence.
February 7th, 2014 11:50am