We've been lucky, from what I'm gathering from web searches! Until December last year, Exchange Online Powershell cmdlet help was available using Get-Help in the shell. However, after the Christmas break, the only response we get is:

Get-Help : Exception calling "Invoke" with "0" argument(s): "Cannot find path '' because it does
not exist."
At line:1 char:1
+ Get-Help Get-Mailbox
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-Help], MethodInvocationException
+ FullyQualifiedErrorId : CmdletInvocationException

It's the same issue irrespective of the cmdlet.

Consequently, I'm forced to contend with painful searches of the documentation website for information of the relevant cmdlets.

Raised this question on the Github Exchange documentation site (https://github.com/MicrosoftDocs/office-docs-powershell/issues/2440) and Chris Davis, who noticed the issue since June, suggested I raise a support case. So not sure this is the right place to do so.

Powershell 5.1 on both Windows 7/10

When calling PowerShell from CMD and specifying a script file that contains an extra "extension" (extra dot) in the base name, the script is not run but the file is mysteriously deleted:

Example (run in CMD):

powershell -file c:\temp\script.txt.ps1

The same issue when called like this:

powershell -command "& c:\temp\script.txt.ps1"

This has been reproduced by me and others on different machines with different paths.

The same issue exists when called from inside PowerShell like this:

. "powershell.exe" -file c:\temp\script.txt.ps1
Start-Process "powershell" -Arg "-file, "c:\temp\script.txt.ps1"

Note that these will work just fine:

powershell -command "& 'c:\temp\script.txt.ps1'"
powershell -command ";& c:\temp\script.txt.ps1"
powershell -file "c:\temp\script.ps1.ps1"

Could this be an optimization bug?

Found out when my CPU is high (99%-100) (i do set executionpolicy to remotesign/unrestricted also)
When i run the PS script, it will ask for executionpolicy.
but when i low CPU, it will just run the script.

suspect value (executionpolicy remotesign) unable to pass thru to script.ps1 on time. so it prompt out everytime when CPU is high.
do we have some setting to tune this. delay it, so that executionpolicy have more time to pass the value to script.ps1.

---------------------------------
Script:
$sourcefolder="D:\A743"
$datenow = get-date
$processdate = (get-date).Adddays(-3)

get-childitem $sourcefolder -file | where-object { $_.lastwritetime -le $processdate } | remove-item -force
---------------------------------------
WIN2012R2 PowerShell v5.1
--------------------------------------
this is the message cause the automation fail.

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks described
in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

Thanks you. due to the original post cant update. here i post again for all the information. Thanks

LOW CPU = all run normal. no prompt anything abt execution policy.
high CPU = will ask exceution policy. if automation (without GUI) will fail.

Sorry if this is the wrong place, I created an issue https://github.com/chef/chef/issues/7765 but I am not sure its an issue with Chef.
I have also created an issue https://github.com/PowerShell/PowerShell/issues/8148 .
I am not very familiar with Powershell sorry, so I am unable to replicate without Chef (If I knew how it would be handy to try and replicate with pure WinRM).

Steps to reproduce
------------------
In Chef
```powershell
cd C:/Test
Add-AppxPackage Example_1.0.0.0_x64.appx -DependencyPath "Dependencies\\x64\\A.appx","Dependencies\\x64\\B.appx","Dependencies\\x64\\C.appx"
```
This is trying to install an appx for a standard user. I believe Chef uses WinRM to run the commands.

Expected behavior
-----------------
```
App installs. Testing the command when physically logging in as the standard user and running powershell, it does work (appx installs).
```
```powershell
get-appxpackage -allusers -name *example*
(result is empty)
```

Actual behavior
---------------
```
Win32 internal error "Access is denied" 0x5 occurred while reading the console output buffer. Contact Microsoft Customer Support Services.
```

Environment data
----------------
```powershell
Name Value
---- -----
PSVersion 5.1.17134.228
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17134.228
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
```

Additional Notes
----------------
I have tried everything I can think of, the only thing that works is starting another powershell script as the user (see the ticket on Chef). Please see https://github.com/chef/chef/issues/7765 for more details.

So I have Windows 10, in Windows optionalFeatures.exe Powershell is marked as version 2.0 in windows system32 is it version 1.0 and Windows Powershell HOST command says Version 5.1

Despite the above information, my Powershell does not know how to do any commands such as 'install-module' or 'PSVerstonTable'
I have a suspicion that my Powershell is somehow corrupted or the incorrect version that was manually installed previously.

I have turned Windows PowerShell 2.0 OFF in Windows Features but Powershell remains and I can open and access it.

I have looked for guides and help on how to do a clean install, or repair. I need help.

when I call:
Restart-Computer -ComputerName $lotsOfComputers -Force

where: $lotsOfComputers is 20-150 other computers on the LAN in our AD environment

This is the sequence of events: First, the command completes quickly, the expected computers reboot, and no errors are displayed. I can then type in the console exactly 1 new line of input and hit enter, after which the PowerShell console hangs for a long period of time (several minutes), possibly in correlation to the size of the array of computers. Once it begins hanging it does not register any new keyboard input onscreen during the hang (but it does stay queued up), and after random periods of time, several of the typed keys will show up in the console, then the hang continues, then a few more keys, then eventually they all show up, the hang has finished, and the console is usable again.

Currently occurs on Windows 10 v1709 with the built-in Windows PowerShell version (PSVersion = 5.1.16299.785 as I type this) Does not seem to be machine-specific, it's happened on any Windows 10 machine I've tried this on Windows Powershell 5.1 went RTM.

If you utilize Smart Cards with certificates that are not directly linked to users (no suitable user DN in Subject and no UPNs in SANs), you are able to link a single certificate to multiple accounts dynamically with the caveat that users need to provide explicit user name hints during logon in order to log on.

User name hints need to be enabled via GPO or registry settings ("X509HintsNeeded"), after which all standard credential dialogs in Windows support them, except PowerShell's Get-Credential. This effectively prevents using PowerShell remoting with such Smart Cards / certificates if different credentials are required.

In today's landscape where Microsoft recommends explicitly tiering your infrastructure and user accounts and using secure methods of administration such as PowerShell Remoting, the omission of this feature is a big letdown. It also reinforces bad habits because Remote Desktop fully supports this scenario while PowerShell does not.

This feature should be implemented.