Windows 7 SP1 Enterprise Black Screen and Language Packs
-
Thursday, April 26, 2012 8:51 AM
Need some help with a challenging issue with our Windows 7 SP1 Enterprise platform. We have 150+ machines which have a black screen which appears for 1-3 minutes at every boot. These machines are built from a master wim image which was built using hyper-v and deployed using SCCM 2007 and MDT 2010 Update 1. The master wim image included multiple language packs and keyboard languages.
We have since rebuilt the master image to not include the additional languages and provide it on demand via MDT which has resolved the issue. The problem is we have 150 machines which we cannot rebuilt therefore need a fix.
The have run xperf and process monitor with boot logging in an attempt to track the issue. Having now removed alll the language packs and keyboard layouts from one machine as a test we continue to have issue.
What I have detected is lpksetup.exe running at startup under svchost dcomlaunch is taking about 60 seconds to complete and almost all of that time it is waiting for a session from CBS. Then the process is repeated again via the task scheduler and this one takes 55 seconds and is waiting for a CBS session.
Reviewing the CBS logs has not identified any issues.
Is it possible to reinstall the lpksetup.exe component so it not longer runs? This would be ok for english only systems but not our other regional language requirements.
Has anyone seen similar with cbs or have any pointers on how to troubleshoot this?
All Replies
-
Thursday, April 26, 2012 9:03 AM
Here's the lpksetup log from the task scheduler run in case it helps. The time differences between lines 2 & 3 is what I would like to understand.
09:06:05:396 : INFO: _wsetlocale returns: English_United Kingdom.1252
09:06:05:396 : PERF: CbsClient::Initialize - ENTER
09:07:20:822 : INFO: created Cbs session 0x346d78
09:07:20:853 : DEBUG: Found TI process (C:\Windows\servicing\TrustedInstaller.exe)
09:07:20:853 : PERF: CbsClient::Initialize - LEAVE
09:07:20:947 : PERF: CbsClient::Initialize - ENTER
09:07:20:963 : PERF: CbsClient::Initialize - LEAVE
09:07:20:963 : PERF: Enumerating installed languages - ENTER
09:07:21:072 : DEBUG: CreateFromIdentity("Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385")
09:07:21:087 : DEBUG: CreateFromIdentity("Client")
09:07:21:087 : LanguagePack en-US created.
09:07:21:103 : type: MUI
09:07:21:103 : identity: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385
09:07:21:134 : WARN: Unable to open Language reg key
09:07:21:259 : DEBUG: CreateFromIdentity("Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514")
09:07:21:275 : DEBUG: CreateFromIdentity("Client")
09:07:21:290 : LanguagePack en-US created.
09:07:21:290 : type: MUI
09:07:21:306 : identity: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514
09:07:21:306 : WARN: Unable to open Language reg key
09:07:21:321 : PERF: Enumerating installed languages - LEAVE
09:07:21:321 : PERF: RestorePointEnd - ENTER
09:07:21:321 : PERF: RestorePointEnd - LEAVE
09:07:21:353 : DEBUG: Cleaning working path in a new process
09:07:22:289 : INFO: Session 0x346d78 finalized, reporting no required reboot
09:07:22:304 : INFO: destroying CbsSession 0x346d78
09:07:22:304 : INFO: attempt to re-finalize session 0x346d78 not acted on -
Friday, April 27, 2012 5:36 AMModerator
Hi,
Based on your description, this would be caused by the uncompleted configuration in SCCM, I suggest you check the SMSTS.log to see if there is some information about the deployment.
On the other hand, if this is caused by a problematic image, we can prevent this issue from root cause., rebuilt image. Or you could stop lpksetup.exe process in task scheduler for a try.
Alex Zhao
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Alex Zhao
TechNet Community Support
- Marked As Answer by Alex ZhaozxMicrosoft Contingent Staff, Moderator Monday, May 07, 2012 1:32 AM
-
Friday, April 27, 2012 9:49 AM
Hi Alex,
Rebuilding the image has resolved the issue for new builds but not for the existing systems built off the original image. I can disable the lpksetup.exe in the task scheduler but now do I stop the svchost dcomlaunch one? I believe I need to deinstall or unregister the lpksetup but I don't know how.
Mike
-
Wednesday, May 02, 2012 4:56 AMModerator
Hi,
What is the result when you disable that scheduled task?
Lpksetup.exe is available with all default Windows installations, if this is a corrupted system file, we can use SFC to repair it:
But maybe this is not caused by defective system file, if you still want to replace this file, try to replace the file with a known good copy of the file, you could also find the full steps in the article above.
Alex Zhao
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Alex Zhao
TechNet Community Support
-
Friday, May 04, 2012 5:19 AMModerator
Hi,
Do you have any updates?
Regards,
Alex Zhao
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Alex Zhao
TechNet Community Support
-
Friday, May 04, 2012 8:46 AM
Hi Alex,
Disabling the scheduled task helped to reduce the delay by about a minute. I had ran checksar on the machine which did not find any issues. The problem I have now is the machine had a major issue and I had to rebuild it so my troubleshooting has stopped.
Mike
-
Monday, May 07, 2012 1:32 AMModerator
Hi Mike,
It's OK, if you have any other problems or concerns, please feel free to let us know.
Alex
Alex Zhao
TechNet Community Support
.png)
