I was afraid of that. Thanks, From: [email protected] To: [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]] On Behalf Of Nick sullivan Sent: Tuesday, September 29, 2015 3:05 PM To: [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] To: [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]] On Behalf Of Vann, Gerry Sent: Tuesday, September 29, 2015 2:36 PM To: [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
