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.

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.

We need a PowerShell version of tpmvscmgr.exe to manage TPM virtual smart cards.

The tpmvscmgr.exe tool 1) does not accept PIN, PUK and AdminKey numbers as arguments, these must be entered interactively in powershell.exe only, not ISE or with a pop-up, 2) cannot list currently existing virtual smart card ID strings, and 3) is somewhat crude in how it manages card lockout policies and unlocks.

This is needed not just for Windows clients, but also because Server 2016 Hyper-V supports virtual smart cards for guest VMs, such as for VDI scenarios.

We need to be able to pass in PIN, PUK and AdminKey numbers as arguments (not be prompted in an interactive shell) so that, among other things, we can have simple GUI wrappers written in PowerShell for this. These arguments could be PS secure strings.

If a cmdlet replacement is impossible for some reason, then please add the above functionality to tpmvscmgr.exe (so that we don't have to script sending keystrokes).

We also need the ability to list existing vCards, rename vCards, clear selected certificate+privkey pairs, clear all key pairs, unlock vCards which have suffered too many failed auth attempts, manage the lockout policies, etc.

A resource module for DSC would be nice, but not mandatory. Updating the graphical TPM Management snap-in for mmc.exe would be nice too, but not mandatory.

Here is a C# project with some of the code needed for the cmdlet:

https://code.msdn.microsoft.com/windowsapps/Smart-card-sample-c7d342e0

Please add the cmdlet(s) to the built-in TrustedPlatformModule posh module and not just to the PSGallery, though that would be OK as long as it is sponsored and supported by Microsoft as future TPM versions and future Windows OS'es are released.

Thank You!
Jason

Object Oriented Programming seems to be supported now in PowerShell, but custom classes defined in modules don't seem to behave the way they should.

There only seem to be two consistent ways to make these work when importing a module that has classes defined:
1. Import the module, then run "using module ..." to make the classes available in the session. Alternatively, you can import the module with the using statement, but this isn't ideal (no versioning).
2. Add the class definition file(s) to the ScriptsToProcess attribute of the module. This isn't ideal either as it runs the scripts in the global session which is bad practice.

Please provide a method that allows classes to be packaged with a module to support OOP scenarios. Thanks!

Votes from Connect: 22

Original Date Submitted: 2/8/2013 8:32:38 AM

Description:
********Contact Information********
Handle: antize
Site Name: PowerShell
Feedback ID: 778798
***************************************

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
Discussion about this at stackoverflow - http://stackoverflow.com/questions/563600/can-i-get-to-work-in-powershell

Jeffery Snover said to request it here so here I am :D

Here is a description of what they do -- http://www.gnu.org/software/bash/manual/bashref.html#Lists

An AND list has the form
command1 && command2

command2 is executed if, and only if, command1 returns an exit status of zero.

An OR list has the form
command1 || command2

command2 is executed if, and only if, command1 returns a non-zero exit status.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 778798 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=778798).

Repro Steps:
Expected Results:

Internal BugId: 4111

DEVCON.EXE can be used to install, uninstall, enable, disable, configure or query devices (as seen in Device Manager) from the command line. Here is the description:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff544707(v=vs.85).aspx

To get DEVCON.EXE, you have to download the entire Windows Drivers Kit (WDK), which is 803MB in size, and, as I understand it, DEVCON cannot be legally redistributed or shared separately.

It would be good to have a PowerShell cmdlet to replace DEVCON that is either installed by default or available in the PSGallery.

Or just allow DEVCON.EXE to be downloaded separately from the WDK somehow, like through NuGet, PSGallery or anywhere.

Or just allow DEVCON.EXE to be redistributed by third parties.

For example, as far as I know, DEVCON.EXE is the only supported or "clean" way to script the installation of the MS Loopback Adapter.

Thank You!

Votes from Connect: 13

Original Date Submitted: 11/1/2012 3:56:26 AM

Description:
********Contact Information********
Handle: J Stangroome
Site Name: PowerShell
Feedback ID: 769359
***************************************

Frequency: Always Happens
Regression: I don't know if this issue existed previously

Problem Description:
In the PSv3 documentation, $PSScriptRoot is now an automatic variable that is populated for both modules and ps1 scripts. It works from PowerShell.exe but not from the ISE

Product Studio item created by Connect Synchronizer due to creation of feedback ID 769359 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=769359).

Repro Steps:
1. Create a new script (eg c:\test.ps1) with the contents: gv PSScriptRoot
2. From PowerShell.exe, execute the script and see PSScriptRoot has a value.
3. From the ISE Console pane, execute the script and see PSScriptRoot had a value.
4. Open the script file in the ISE Script Pane and press F5 to run the script and see PSScriptRoot is blank.

Expected Results:
The $PSScriptRoot automatic variable should have a value when run via F5 in the ISE.

Internal BugId: 3931

Votes from Connect: 3

Original Date Submitted: 10/30/2014 5:41:25 PM

Description:
********Contact Information********
Handle: ulrichb
Site Name: PowerShell
Feedback ID: 1015225
***************************************

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
New-ScheduledTaskTrigger offers just a subset of the trigger options. Things like "On an (event log) event", or "On workstation (un)lock" are missing.

We just found ugly workarounds to add these (e.g. event log) triggers by using "schtasks.exe /create /xml" or using the COM "TaskScheduler" class.

New-ScheduledTaskTrigger should allow specifying all options the Task Scheduler UI offers. As there already exists an XML representation of these triggers (e.g. <EventTrigger>, <SessionStateChangeTrigger>, ...) it would also be possible to offer a "-Custom" parameter which takes such an XML fragment to specify a trigger.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1015225 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1015225).

Repro Steps:
Expected Results:

Internal BugId: 13076