Microsoft has no solution at this time... They have escalated the issue to the "Design" team and suggested I file a bug on the Connect web site.
I pretty much expected this once we learned that the issue could be replicated with WDS and the default Windows 10 boot.wim. I guess they would have to generate new wim files in a later release of Windows 10 and ADK 10? I don't see that happening anytime soon so I guess we're stuck with this... Dewayne From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, October 1, 2015 9:38 AM To: [email protected] Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts If you are using PowerShell scripts during the WinPE portion of the TS, this is certainly one option. Depending upon what you are doing in the script other options include falling back to VBScript or HTAs or using native code. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrew Craig Sent: Thursday, October 1, 2015 7:32 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts "I updated our SCCM environment to 2012 R2 SP1 CU1 and applied KB3084586. This means using the Windows 10 ADK. " I'm open to correction but I don't think you have to. I mean you don't have to use Windows 10 ADK. Stick to 8.1 ADK until they iron out the bugs in 10. You can still deploy Windows 10 using WinPE 5.1 (+1) or even imported WinPE 10 boot images. Andy From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: 30 September 2015 18:43 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts I was able to reproduce it in a production environment a couple weeks ago. We switched from the x86 boot image to the x64 boot image when we started imaging Surface Pro 3 systems, and immediately we had TS failures because of a PowerShell script that suddenly was failing. Fortunately, the issue had already been raised on the list so we narrowed it down quickly, but I'm definitely hoping they release an updated ADK soon. Had to resort to vbscript for the functions we needed...blech! :) -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Hyatt, Dewayne Sent: Wednesday, September 30, 2015 8:48 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts I have an open support case with Microsoft for this issue now. I've had the case open for several weeks and it doesn't look like there has been much progress. In my own troubleshooting I was able to reproduce the error with vanilla WDS and the boot.wim from the Windows 10 media. There's a thread on Nialls site about it here: http://www.windows-noob.com/forums/topic/12833-sccm-2012-r2-sp1-task-sequence-powershell-adk-10-error-800703e9/ Dewayne From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Vann, Gerry Sent: Tuesday, September 29, 2015 6:36 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts Yep. Thank you all for the quick response. Looks like I will be watching for an update to the Windows 10 ADK. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Nick sullivan Sent: Tuesday, September 29, 2015 4:58 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts I was afraid of that. Thanks, ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts Date: Tue, 29 Sep 2015 20:28:58 +0000 Neither. This is a WinPE 10 bug. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Nick sullivan Sent: Tuesday, September 29, 2015 3:05 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts Jeff, Is this bug only for post-CU1 or even pre-CU1 on R2 SP1? Thanks ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts Date: Tue, 29 Sep 2015 19:57:45 +0000 It is a bug. Aaron Czechowski says they know about it and have only isolated it x64 systems so far. In my testing anything with UEFI and a mobile CPU has had the error. I haven't seen anything on connect about it. Thanks, Jeff Jerousek 217-793-3800 x1822 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Vann, Gerry Sent: Tuesday, September 29, 2015 2:36 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Windows 10 ADK PXE Boot PowerShell Scripts Hey all, I updated our SCCM environment to 2012 R2 SP1 CU1 and applied KB3084586. This means using the Windows 10 ADK. Ever since the update we have not been able to run PowerShell scripts when we PXE Surface Pro 3's and Lenovo's X1 Carbon 20BS. All other models are Dells and they work fine. The work around is to boot from USB, but our desktop team much prefer PXE. The error I get on the screen is: powershell.exec - Application Error The exception illegal instruction An attempt was made to execute an illegal instruction (0xc000001d) occurred in the application at location 0x00007FF845CBA761 And the smsts.log file says: SCCM Recursion too deep; the stack overflowed. (Error: 800703E9; Source: Windows) I found at least one other person having this issue and it sounds like a bug. http://www.windows-noob.com/forums/topic/12833-sccm-2012-r2-sp1-task-sequence-powershell-adk-10-error-800703e9/ Has anyone else experienced this or knows for sure it is a bug? Thanks, Gerry
