We are running Powershell 3.0 scripts in the task sequences against T450s and 
T440s no problem at all.  Not sure if that's helpful but I thought I'd mention 
it. 
                 On Thu, Aug 6, 2015 at 7:41 AM, Hyatt, Dewayne 
<[email protected]> wrote:








So last night I completely removed my ADK install, just to be thorough. I 
recreated all of my boot images and it did not make a difference.
 
I found this thread that is related, but it is for ADK preview:
 
https://social.technet.microsoft.com/Forums/en-US/c51e4f0b-f067-4739-bfcd-e9069de5b58f/windows-adk-10074-issue-with-winpe-and-powershell?forum=WinPreview2014Setup
 
It’s the exact same issue reported by a few different people but no resolution. 
At this point I think I will open a ticket with Microsoft.
 
Dewayne
 


From: [email protected] [mailto:[email protected]]
On Behalf Of Hyatt, Dewayne

Sent: Wednesday, August 5, 2015 2:16 PM

To: [email protected]

Subject: [mssms] RE: ADK 10 boot images + PowerShell is crazy


 
Thanks Michael,
 
This particular VM has 2048MB and is not set for dynamic memory. Actually the 
first system to exhibit this behavior was a Surface Pro 3 with 8GB
L
 
Thanks,
 
Dewayne
 


From: 
[email protected] [mailto:[email protected]]
On Behalf Of Michael Niehaus

Sent: Wednesday, August 5, 2015 1:58 PM

To: [email protected]

Subject: [mssms] RE: ADK 10 boot images + PowerShell is crazy


 
I’ve seen errors like that (very random) on memory-constrained VMs, e.g. those 
using dynamic memory with a 512MB minimum.  If you are using a VM, try 
specifying a 1024MB minimum.
 
Thanks,
-Michael
 


From: 
[email protected] [mailto:[email protected]]
On Behalf Of Hyatt, Dewayne

Sent: Wednesday, August 5, 2015 1:53 PM

To: '[email protected]' <[email protected]>

Subject: [mssms] ADK 10 boot images + PowerShell is crazy


 
I’ve found that running PowerShell in my new Windows 10 boot images has been 
very erratic. I noticed that our frontend form was giving numerous errors. I 
then found that just trying to run “start powershell” from a command prompt was 
also
 very hit or miss. Sometimes it will run, other times I received a “Process is 
terminated due to StackOverflowException” error and even got a “800703e9 
recursion too deep stack overflowed”.
 
Example:
 

 
Has anyone seen this?
 
Thanks,
 
Dewayne
 
 
 










                                          


Reply via email to