(MDT 2012) - Black screen after install, restart allows continue
-
Monday, May 28, 2012 4:33 AM
Hopefully this is a quick one! I've been slowly moving from thin images to thick images for the deployment speed and I've come across a strange problem.
I have used MDT 2012 to capture and deploy a 7 Pro 64bit image and straight after the OS installation the TS will reboot and I'll just get a black screen with a mouse. No matter how long I leave it it will just sit there.
If I restart the PC manually the OS loads fine and the TS continues as if nothing happened.
The MDT logs don't show any errors or anything, the Windows event logs don't show anything (other than a single error showing that the PC was shutdown unexpectedly). I've rebuilt the image twice and deployed to our test model and a virtual machine with the same result. I originally thought it might be driver related but the VM has a completely different driver set etc.
There is only a couple of applications installed onto the thick image (and we have created these images before for our laptops using the same application list with no issues).
Any ideas?
Thanks!
All Replies
-
Monday, May 28, 2012 4:38 AM
Sorry just to be clear, the process is:
- Install OS in VM (though also tried installing on hardware with same result)
- Install updates and apps, modify settings
- Capture image using MDT 2012 standard capture TS
- Boot into PE
- Select TS
- Install drivers and OS stage
- restart
- Black screen indefinitely
- Restart manually
- OS loads
- Continue TS
- Completed.
- Edited by mhouston100 Monday, May 28, 2012 5:09 AM
- Edited by mhouston100 Monday, May 28, 2012 6:00 AM
-
Monday, May 28, 2012 3:19 PM
Hi,
to completely discard that is a driver issue,i would try first to upgrade to the latest BIOS versión in one of the host you are using to test your deployment. If that does not solve the problem, i would create a test profile in the MDT console only with the network and HDD drivers. If this works...probably the problem was in one of the drivers you are installing...so you have to keep adding drivers one by one until you get the error again.
-
Monday, May 28, 2012 9:50 PMI'll definitely be testing that today, especially with the BIOS (this test model is one of the first that we got of this series). I wasn't very thorough with the drivers I'll admit, I just copied them from another MDT share... probably karma getting me for trying to take shortcuts!
-
Wednesday, June 06, 2012 1:16 AM
I have now exhausted my testing capabilities it seems and I'm still hitting the same stumbling block. It isn't critical as a manual hard power off is working to contin ue the build but it sure is annoying! So what I have tried so far:
- Removing all drivers (even network) from the driver injection results in the same issue. A restart fixes it and then the TS fails due to no network connection as expected.
- Removed all storage drivers from the capture and turned off the storage device feature of sysprep same result.
- Installed direct from media and captured with MDT, same result
- Added media to MDT, deployed, then captured and same problem with resulting image. Interestingly though, the initial deployment from MDT of the blank media proceeds fine, only when I re-capture that I get this blank screen.
- Deployed image to Same hardware, different hardware and VM and same blank screen problem.
As I said above, the image itself works perfectly once a manual restart is done, but if no one intervenes it will sit on the black screen indefinitely.
Checking the even logs just shows the manual power off with no errors prior to that, the last even prior to me pressing the power button is 'The Windows Modules Installer service has entered the stopped state' but it's just an info event, prior to that the same service starts, changes to 'on demand' and then stops.
Can anyone think of something I haven't tried? Or some other logs that I can check?
Thanks in advance!
-
Wednesday, June 06, 2012 8:49 AM
So, the OS and drivers get installed and then the machine reboots. This is when you see the Blank Screen? Correct?
If you reboot manually, it continues with the automation.Couple of things - Can you check your task sequence - if you have a reboot after OS install and any other steps.
Next - If you get to the black screen, can you press CTRL+SHIFT+ESC which will open Task Manager - Do you see litetouch.wsf or vbs running??
Next - Open CMD from Task Manager - Then goto x:\Deploy\Scripts\ and then type litetouch.wsf to resume - see what happens.
This is not a driver issue - If I were you, I would recreate a new Task Sequence and test.
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"
-
Wednesday, June 06, 2012 9:50 PM
Thanks for taking the time Vik, to answer your questions:
- That is correct, I have left it overnight again and is still on the black screen this morning (with cursor), when I restart it restarts Windows as normal and continues the TS (also, the TS completes with no errors in the logs)
- Task sequence is the standard MDT 2012 'Standard Client Task Sequence', I haven't modified it other than to put an IF statement on the USMT restore step (which works on all other TS I have in there at the moment)
- Black screen and cursor but no Task Manager - Through Ctrl-Shift-Esc or Ctrl-Alt-Delete
- Same above
- Also a new TS is created every time I do a capture (at this point) until I have a stable image!
Very strange, I'm beginning to think it is either a Windows update or an application that is causing it (though my other TS and media use the same apps and updates) - the applications are very basic, corporate archive program, pdf printer, acrobat reader, flash etc but it may be one of these that causes it.
Like I said, when I deploy just the media with drivers from MDT it appears to go through fine. I'll be testing it further today if I have time, maybe even to the point of one app at a time until I find the culprit. Unfortunately we are in the middle of a massive backup overhaul so I'm trying to juggle this when I can!
Again, thanks for your help!
EDIT :: Probably doesnt mean anything but after the manual restart I do get the 'Microsoft Windows did not shut down correctly' and I chose 'Start Windows Normally' from the menu. As above though, there are no errors or warnings in the event logs.- Edited by mhouston100 Wednesday, June 06, 2012 10:55 PM More info
- Edited by mhouston100 Wednesday, June 06, 2012 10:56 PM
-
Thursday, June 07, 2012 1:23 AM
SIGH - Well, I thought I had it. I did a complete deployment, then removed from domain and ran the capture again, thinking maybe the problem only shows on the first setup, but same issue when restarting.
So to confirm a few details:
- 1. OS install completes
- Restart happens
- Get Windows animated loading screen
- 'Setup is configuring your computer' - (can't remember exact wording!)
- 'Testing Video performance' - Screen flickers as though adjusting resolution
- Black screen with cursor.
Tearing my hair out! Right now, I am going to do a fresh install from media, install only updates, then capture and see if I have any success.
- Edited by mhouston100 Thursday, June 07, 2012 1:24 AM
-
Thursday, June 07, 2012 9:42 AM
When you run your next deployment, can you disable the Apply Drivers actions in the TS as a temporary measure?
If it was a drivers issue then I would expect there to be something in the Windows Setup logs (C:\Windows\Panther\setupact.log and setuperr.log as well as possibly C:\Windows\setupact.log and setuperr.log). Disabling the driver injection on your sysprepped image should rule out drivers completely, but because of where it's failing I cant believe its anything but drivers.
I've seen similar things in the past with Windows XP - mostly monitor driver related if I remember correctly.
-
Friday, June 08, 2012 12:07 AM
G'day Andrew,
Disabled both 'Inject driver' actions in the TS, installation still proceeds the same and stops on the black screen.
On the black screen I restarted back into a PE and checked the logs, setuperr.log is blank, I don't see anything dramatic in the setupact.log, it ends with :
2012-06-07 13:36:15, Info [0x060132] IBS Callback_ProductKey_CleanBB: Successfully deleted ProductKey value from blackboard.
2012-06-07 13:36:15, Info UI CallbackShowFinishOnline: Enter
2012-06-07 13:36:15, Info UI CallbackShowFinishOnline: Exit
2012-06-07 13:36:15, Info [0x09008e] PANTHR SeqExecute -- stopping, since termination group reached
2012-06-07 13:36:15, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-06-07 13:36:15, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-06-07 13:36:15, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2012-06-07 13:36:15, Info [0x0900c7] PANTHR SEQ EVENT_SERIALIZE_BEFORE_EXIT Received. Will only save modules with persistent subscriptions!
2012-06-07 13:36:15, Info [0x0900b7] PANTHR SerializeToFile: C:\Windows\Panther\MainQueueOnline1.que
2012-06-07 13:36:15, Info [0x0900b8] PANTHR Saving Main Event Queue
2012-06-07 13:36:15, Info [0x0900b9] PANTHR Saving Permanent Event Queue
2012-06-07 13:36:15, Info [0x0900c5] PANTHR Queue Serialization Succeeded
2012-06-07 13:36:15, Info PANTHR DeleteCriticalSection for pExecQueue->csLock;
2012-06-07 13:36:15, Info UI CallbackWin32UITerminate: Deleted WizardUI
2012-06-07 13:36:15, Info [0x0605a6] IBS Requested UI to hide the language and locale selection pages.
2012-06-07 13:36:15, Info [0x06010d] IBS Module_Term_Productkey: Valid product key in blackboard, show property set to hide.
2012-06-07 13:36:15, Info [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
2012-06-07 13:36:15, Info [0x0601dc] IBS Setup has completed phase 4 at 2012-06-07 13:36:15
2012-06-07 13:36:15, Info IBS Successfully logged Setup information onto event viewer system channel
2012-06-07 13:36:15, Info IBS Successfully logged OS information onto event viewer system channel
2012-06-07 13:36:15, Info [0x0601e1] IBS InstallWindows:First boot phase of setup done!!!!
2012-06-07 13:36:15, Info [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.Seems legit. I ran through any log I could find in that folder but didn't really see anything that stood out...
-
Wednesday, June 13, 2012 3:24 AM
If anyone is still watching this thread, I still have no idea why this is happening. I've done a fresh deployment to a VM using a brand new task sequence and the fresh installation media from MDT (I've disabled the domain integration and drivers), deployment works fine. Without making ANY changes I do a capture which also goes fine, then deploy that captured image using a standard task sequence and same black screen straight away. This is with no drivers at all being included.
Bizarre. So at the moment I am just living with it as I don't have any more time to create / recreate images for testing.
-
Wednesday, June 13, 2012 6:59 AM
Hi,
It's really hard to debug this one remotely and the logs weren't the help I was hoping for.
1 more suggestion, next time you initiate your deployment, unplug all pheripherals right after you've gone though the MDT wizard. USB & PS2 if you have them.
-
Wednesday, June 13, 2012 10:21 PM
ha ha it's a bastard on site too!
I'll try that, I had read a couple of threads with people having issues with USB. I'll give it a shot today.
Thanks!
-
Wednesday, June 13, 2012 11:26 PM
Are you talking about a Windows 7 Pro RTM disk, or a Windows 7 with SP1 integrated as source installation files? Just thinking out loud.
Could you also please discribe the hardware in question?
What's the hardware vendor of the graphics card, unless it's a cpu integrated gpu.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCC.
How to configure Windows RE/OEM Recovery Partition with MDT- Edited by Stephan Schwarz Wednesday, June 13, 2012 11:57 PM fixed typo
-
Wednesday, June 13, 2012 11:36 PM
Just a plain Win 7 Pro 64bit SP1 install disk. Hardware is Core i5 Sandy Bridge, everything integrated (i.e no discrete graphics etc). Only 'external' device is a card reader, which I'm going to unplug for testing today along with the USB devices.
-
Wednesday, June 20, 2012 1:22 AMWe have ended up going with a different media so I guess the point is moot. Still frustrating though!
-
Wednesday, June 20, 2012 1:00 PMHaving same problem here deploying an image with MDT 2012. Ours is a Win 7 32 bit captured image. Will hang indefinitely on the black screen after the OS install. We have to restart and then we get the same 'Microsoft Windows did not shut down correctly' chose 'Start Windows Normally' from the menu and it loads and resumes the deployment as if nothing happened.
-
Wednesday, June 20, 2012 10:03 PM
I never did find an answer. I'm still leaning towards a driver issue, even though I disabled the inject driver phases something may still be getting in - does anyone know if the drivers that are in the PE are used for he installation if they match, even if the injection is disabled?
Unfortunately I scrapped those images so I cant do any further testing!
-
Wednesday, June 20, 2012 10:30 PM
I never did find an answer. I'm still leaning towards a driver issue, even though I disabled the inject driver phases something may still be getting in - does anyone know if the drivers that are in the PE are used for he installation if they match, even if the injection is disabled?
Unfortunately I scrapped those images so I cant do any further testing!
If driver injection is not used, then the drivers that WinPE uses will not be used either.If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCC.
How to configure Windows RE/OEM Recovery Partition with MDT -
Saturday, November 10, 2012 4:53 PM
Hi,
Running into the same issue here when deploying a Custom WIM captured with MDT2010 with MDT 2012 and WAIK.
Deployment Method: PXE boot or Standalone USB media - Same issue.
Same image with same drivers is working fine when deploying from MDT2010.
With MDT2012 after the WinPE phase where OS is installed, on the first reboot we see the usual setup is installing devices and so on.
After that black screen with mouse. RDP'ed to the machine from MDT2012 DaRT Monitoring and Device Manager is clean so is MSInfo32 (Problem Devices).
Display settings in MSinfo32 seems correct 1024x768 @ 60 Hz, yet QRes /L ( list supported mode) reports no supported mode. ( I did test the same util on a successfully deployed image and I get a large list, so something is fishy at that level).
Attempts to set the resolution with QRes are failing with "Error: The graphics mode is not supported!"
Will try to update the Unattend.xml with WSIM to set resolution again. In the meantime any suggestions are welcome.
Thanks
Manuel
Manuel Toussaint
- Edited by toussman Saturday, November 10, 2012 4:54 PM
-
Wednesday, November 14, 2012 9:41 AM
Manuel,
Can you run task manager when you get the black screen? If so, check to see if you have a copy of xcopy running (it comes and goes).
I've seen this issue before but for our images.
Roy
-
Wednesday, November 14, 2012 8:37 PMEven though the issue no longer occurs for me, when I did have it, there was no task manager, nothing except the mouse pointer itself on the black screen.
-
Wednesday, November 14, 2012 10:01 PM
Thanks issue fixed for us, one of my colleague found the fix ( also called Roy L.) BTW.... ;)
Selecting the option “Create extra 'Active' partition” on the "Format and Partition Disk" step did the trick.
@mhouston100 To access task manager, someone actually needs to be in front of the computer to press Ctrl - Alt - Del.
Manuel Toussaint
- Edited by toussman Wednesday, November 14, 2012 10:03 PM
-
Wednesday, December 19, 2012 2:37 PM
Hi,
If you are using VMware,
Shut down the virtual operating system(i.e. Server 2012).
then go to settings ->Under 'Hardware' Tab -->Display -->then Enable 3D Graphics.
And Start the system again.
It Worked for me!!!
Please don't forget to mark as Answer if this helped you!!!!
Sandeep Avala
sandeep
- Proposed As Answer by saiava Wednesday, December 19, 2012 2:37 PM
-
Thursday, April 11, 2013 2:05 PM
I had exactly the same problem as You described. I am using Windows 7 image prepared by Symantec Ghost and try to capture it into WIM file and then using MDT deploy. I read the whole discussion here and have some comments:
1. When You press Ctrl+Shift+Esc there is no task manager but You can type in cmd: taskmgr and it appear then
2. I try to troubleshoot this using RDP (to enable I typed in cmd: sysdm.cpl and computer properties window apper) and it help me because in RDP window I can see that installation completes and there is an error which say “C:\Windows\system32\config\systemprofile\desktop refers to a location that is unavailable.”
So I check if user profile is ok and it was not. In C:\users there was only Public folder
And the solution of this problem (for me) is use <CopyProfile>true</CopyProfile> in unattend.xml used in deployment. I believe that this problem occurs because administrator account was renamed into admin
Sample CopyProile section in unattend.xml
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName></ComputerName>
<CopyProfile>true</CopyProfile>
<ProductKey></ProductKey>
<RegisteredOrganization>Compay</RegisteredOrganization>
<RegisteredOwner>admin</RegisteredOwner>
<TimeZone></TimeZone>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>

