Windows 10: Inside Windows Sandbox, how can I run PowerShell or Cmd as a non-administrator?

submitted by /u/krk_computers
[link] [comments]

:)

 

Windows Sandbox can't run PowerShell?!?

When running in Windows Sandbox I can't run any PowerShell scripts at all. I get an error that states that, "Version v4.0.30319 of the .NET Framework is not installed and it is required to run version 3 of Windows PowerShell." and I have .net version 4.8.03752
installed on the host machine (and then presumably on the sandbox machine). So far I've found it impossible to reinstall any version of .net 4.0 in the sandbox, I get "Same or higher version of .NET Framework 4 has already been installed on this computer."

I assume PowerShell is supported in the sandbox? That would be a pretty annoying limitation to not be able to run PowerShell...

Thanks,

 

CMD and PowerShell

Hi Andre,

Done. The result: in control panel there's now an administrator account (local). Signing in to that account, and using win key+X I can run PowerShell (as admin) without a problem.

I signed out of that account and signed in to my own original administrator account: win key + X cannot run PowerShell as administrator, same notification that there's no connected application. I can get to PowerShell ISE, though, and by typing CMD in Start
I can run the command prompt as administrator.

The only difference between the 2 accounts is that in the local administrator account I can with Win key+X run PowerShell (as admini) whereas in my own account I cannot.

[In both account in taskbar settings "replace command prompt with PowerShell:" is on.]

 

Why does Powershell Install-Module fail inside Windows Sandbox

Outside sandbox windows powershell is happy to Install-Module ; inside Sandbox the ability to do this is missing? The versions appear to be identical. I'm trying to automate a build process inside Sandbox using a Powershell script that installs and builds
a number of things and I need to install 7Zip4Powershell.

Running outside of sandbox:

Code:

PS C:\Users\eddy> echo $PSVersionTable

Name                           Value

----                           -----

PSVersion                      5.1.18362.752

PSEdition                      Desktop

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}

BuildVersion                   10.0.18362.752

CLRVersion                     4.0.30319.42000

WSManStackVersion              3.0

PSRemotingProtocolVersion      2.3

SerializationVersion           1.1.0.1

PS C:\Users\eddy> Install-Module

cmdlet Install-Module at command pipeline position 1

Supply values for the following parameters:

Name[0]:
[b]Whereas inside sandbox:[/b]PS C:\Users\WDAGUtilityAccount> echo $PSVersionTable

Name                           Value

----                           -----

PSVersion                      5.1.18362.752

PSEdition                      Desktop

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}

BuildVersion                   10.0.18362.752

CLRVersion                     4.0.30319.42000

WSManStackVersion              3.0

PSRemotingProtocolVersion      2.3

SerializationVersion           1.1.0.1

PS C:\Users\WDAGUtilityAccount> Install-Module

Install-Module : The term 'Install-Module' is not recognized as the name of a cmdlet, function, script file, or

operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try

again.

At line:1 char:1

+ Install-Module

+ ~~~~~~~~~~~~~~

    + CategoryInfo          : ObjectNotFound: (Install-Module:String) [], CommandNotFoundException

    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\WDAGUtilityAccount>