Powershell Core appears to be broken in latest WinXPE Release

Testing with version 7.1.0 and windows 10 2009 release.

Native powershell commands are fine, but anything that calls an external executable (such as reg or diskpart or something) fails with OperationStopped: the request is not supported. Tested using Powershell 7.0.3 with identical settings and didn't have the same issue. Doesn't affect Powershell Core in a regular windows install.

Powershell 7.1.0:


Powershell 7.0.3:

Hi Venerence,
I reproduce the same, also with PowerShell-7.2.0-preview.1-win-x64
It seems related to this issue: Avoid an exception if file system does not support reparse points
with this comment by SteveL-MSFT, 8 days ago

Looks like you can't execute native commands in WinPE w/o this fix

Hi Venerence,
I reproduce the same, also with PowerShell-7.2.0-preview.1-win-x64
It seems related to this issue: Avoid an exception if file system does not support reparse points
with this comment by SteveL-MSFT, 8 days ago

Looks like you can't execute native commands in WinPE w/o this fix

Thanks for narrowing down the problem, guess we'll just have to wait for the next preview release and hopefully it'll resolve itself.

I have added PowerShell 7.0.3 to Wimbuilder as a standalone plugin/app. (Not a preview version)
PSVersion      7.0.3
PSEditon         Core
GitCommitId      7.0.3
OS         Microsoft Windows 10.0.19041
Platform         Win32NT
PSCompatibleVersions   {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion   2.3
SerializationVersion   1.1.0.1
WSManStackVersion   3.0

It is built from MSMG PEPacks for Microsoft Windows  (10.0.19041.84,x64,en-US)
It is not suffering from executing native commands.
Working= reg, regedit, diskpart, notepad, mspaint, cmd, etc.

If you like, I can share or even help you troubleshoot with this issue,
beings I have a working PS7 install.

Regards
RoyM

or you could just change the "program version" to 7.0.3 instead of 7.1.0
as I think it was reported that >

Tested using Powershell 7.0.3 with identical settings and didn't have the same issue.

Yeah your right Jimehc, didn't catch that on first read.
Regards
RoyM

Thanks for narrowing down the problem, guess we'll just have to wait for the next preview release and hopefully it'll resolve itself.

Tested with Powershell v7.2.0-preview.2, the problem seems indeed solved
To test easily, write "7.2.0-preview.2" in Program Version