On a side note, I just loaded our .WIM into a VM. It looks hosed! I am getting desktop could not be loaded, IE gets errors when you open it, ALL out IE patches are missing. IE patch level shows RTM. All Windows Updates are missing it looks like.
Could the R2 upgrade somehow have modified our .WIM? Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, August 20, 2014 1:14 PM To: [email protected] Subject: RE: [mssms] ConfigMgr 2012 R2 upgrade - OSD - Hangs at black screen after windows setup Testing now, should know later today or early tomorrow. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Wednesday, August 20, 2014 1:07 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] ConfigMgr 2012 R2 upgrade - OSD - Hangs at black screen after windows setup try the offline updates test, copy your current WIM file, do offline updates on the copy, deploy the copy to one dp only, and duplicate your deploy ts to deploy this wim, do the previously failing machines now suddenly work ? On Wed, Aug 20, 2014 at 7:02 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: The affected models is growing. Twist, Yoga, T540p, M91p so far. Just found some more info in the sysprep logs, the interesting thing is this is from a working machine. Failed machines have the same errors. Everything online points to a generalization issue in unattend.xml or possibly a network profile issue. Not much else online. SetupErr.log 2014-08-20 11:20:19, Error SYSPRP SPPNP: Error 0x25 (CONFIGRET) occurred while determining the buffer size needed to hold the list of devices that are using service usbhub20. 2014-08-20 11:20:19, Error SYSPRP SPPNP: Error 0x424 occurred while opening a handle to the service usbhub20.[gle=0x00000424] 2014-08-20 11:20:25, Error SYSPRP SPPNP: Error 0x25 (CONFIGRET) occurred while determining the buffer size needed to hold the list of devices that are using service vmbus. 2014-08-20 11:20:25, Error SYSPRP SPPNP: Error 0x424 occurred while opening a handle to the service vmbus.[gle=0x00000424] Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Wednesday, August 20, 2014 12:57 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] ConfigMgr 2012 R2 upgrade - OSD - Hangs at black screen after windows setup yes we've seen it, bizarre too what hardware is it failing on ?> we've seen it on only specific hardware such as lenovo w530 i think the solution ? inject offline updates into the captured wim and deploy that wim instead. No idea why the updates solved it, but it did. We had the problem with both images captured in Configuration Manager and MDT. On Wed, Aug 20, 2014 at 6:50 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: We are fighting an intermittent issue with a small percentage of our builds in OSD. This is post our R2 CU1 upgrade. The machines install Windows, reboots, and hang at a black screen with just the mouse cursor. You can move the mouse, but cannot hit F8 or shift+F10 for the cmd prompt. We can take the same machine, rebuild it again, and it will go through without an issue. This happened intermittently on any number of our 20+ task sequences. Any ideas? The only thing we have found is LOTs of driver errors in setupapi.dev.log on the machines that failed. We will most likely be opening a case with Microsoft in the next day or two if we cannot get any headway. Thanks! Daniel Ratliff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
