I've seen people talking about it on windows-noob, here's an interesting quote, i can't see any way to limit the cpu via the options in the surface pro 3 however,
*"so far that's been the case... However, by limiting the available Resources (CPU), as described above, it works in most cases - that behaviour is binary... 2 CPU == 100 % failure, 1 CPU == 80 % Success.... "* http://www.windows-noob.com/forums/topic/12833-sccm-2012-r2-sp1-task-sequence-powershell-adk-10-error-800703e9/page-2 On Thu, Sep 17, 2015 at 7:24 PM, Michael Niehaus < [email protected]> wrote: > We’ve been investigating, but so far there’s no concrete information on > the cause (other than it’s only on x64). > > > > Thanks, > > -Michael > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jerousek, Jeff > *Sent:* Thursday, September 17, 2015 10:08 AM > *To:* [email protected] > *Subject:* [mssms] Powershell on WinPE10 (UEFI) > > > > Has anyone narrowed down or fixed what’s causing errors with PowerShell on > certain devices in PE 10? > > > > I’ve only seen the errors on UEFI devices. > > > > So far Surface Pro 3s and Lenovo T440s are failing to even run PowerShell > from the command line sometimes. > > > > I’ve gotten memory exception errors and a mscorelib error. > > > > Turning Legacy mode on for the T440s fixed the problem. Haven’t found a > fix for the SP3. > > > > Hyper-V Gen 2, Dell 9010, 9020s all work fine. > > > > Thanks, > > Jeff Jerousek > > > > > >
