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.

Problem:

When creating an object from the x509Certificate class the shell adds 3 script properties:

DnsNameList
EnhancedKeyUsageList
SendAsTrustedIssuer

The SendAsTrustedIssuer property causes Powershell to hit a CLR exception and hard crash when accessed.

Repro Code:

* Note: do this in a fresh session as it will crash the session

$Test = New-Object System.Security.Cryptography.x509Certificates.x509Certificate2
$Test | select *

Alternately,

$Test = New-Object System.Security.Cryptography.x509Certificates.x509Certificate2
$Test.SendAsTrustedIssuer

Crash dump:

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Management.Automation.Security.NativeMethods.CertGetCertificateContextProperty(IntPtr pCertContext, CertPropertyId dwPropId, IntPtr pvData, Int32& pcbData)
at Microsoft.PowerShell.Commands.SendAsTrustedIssuerProperty.ReadSendAsTrustedIssuerProperty(X509Certificate2 cert)
at CallSite.Target(Closure , CallSite , Type , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(ScriptBlockClauseToInvoke clauseToInvoke, Boolean createLocalScope, Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
at System.Management.Automation.ScriptBlock.<>c__DisplayClass57_0.<InvokeWithPipe>b__0()
at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThreadCheck(Action action)
at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Boolean propagateAllExceptionsToTop, List`1 variablesToDefine, Dictionary`2 functionsToDefine, Object[] args)
at System.Management.Automation.ScriptBlock.DoInvokeReturnAsIs(Boolean useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Object[] args)
at System.Management.Automation.PSScriptProperty.InvokeGetter(Object scriptThis)
at Microsoft.PowerShell.Commands.Internal.Format.MshExpression.GetValue(PSObject target, Boolean eatExceptions)
at Microsoft.PowerShell.Commands.Internal.Format.MshExpression.GetValues(PSObject target, Boolean expand, Boolean eatExceptions)
at Microsoft.PowerShell.Commands.SelectObjectCommand.ProcessParameter(MshParameter p, PSObject inputObject, List`1 result)
at Microsoft.PowerShell.Commands.SelectObjectCommand.ProcessObject(PSObject inputObject)
at Microsoft.PowerShell.Commands.SelectObjectCommand.ProcessObjectAndHandleErrors(PSObject pso)
at Microsoft.PowerShell.Commands.SelectObjectCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
at System.Management.Automation.CommandProcessorBase.DoExecute()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
at System.Management.Automation.DlrScriptCommandProcessor.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
at System.Management.Automation.DlrScriptCommandProcessor.Complete()
at System.Management.Automation.CommandProcessorBase.DoComplete()
at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase commandRequestingUpstreamCommandsToStop)
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
at System.Management.Automation.Runspaces.PipelineThread.WorkerProc()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

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

i have a pull server with 2 non-encrypted mofs, and 1 encrypted mof. The LCM on the lab node is configured to pull the 3 different configs as partialconfigs. When I run Start-DSCConfiguration, the encrypted mof fails with the following:

PowerShell DSC resource MSFT_UserResource failed to execute Set-TargetResource functionality with error message: There could be a possible multiple matches exception while trying to use the System.DirectoryServices API's.Exception calling "Save" with "0" argument(s): "The
password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.
"
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : localhost

The error above is misleading, as it is probably interpreting that password block in the MOF as a string literal (not an encrypted variable)

If i configure the LCM on the node to only pull the encrypted MOF, it works. So there seems to be some problem with a combination of multiple partial configs which some are encrypted, and some are not. any help appreciated.

Get-RDSessionCollection of the RemoteDesktop module always throws an exception:
--

PS C:\windows\system32> Get-RDSessionCollection
New-Object : Exception calling ".ctor" with "1" argument(s): "Invalid parameter "
At C:\windows\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\SessionDesktopCollection.psm1:520 char:14
+ ... $scope = New-Object System.Management.ManagementScope("\\" + $Conn ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

CollectionName Size ResourceType CollectionType CollectionDescription
-------------- ---- ------------ -------------- ---------------------
mycollection 0 RemoteApp programs PooledUnmanaged My first collection

PS C:\windows\system32>

--

Changing C:\Windows\System32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\SessionDesktopCollection.psm1 line 520

$scope = New-Object System.Management.ManagementScope("\\" + $ConnectionBroker + "\" + $wmiNamespace, $connectionOptions)

into

$msuri = "\\" + $ConnectionBroker + "\" + $wmiNamespace
$scope = New-Object System.Management.ManagementScope($msuri, $connectionOptions)

fixes the problem.

This issue breaks our offering in the Azure Marketplace.

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.

The documentation states to import a .xml to a mounted Windows image, you can use the powershell command:
PS C:\ Import-StartLayout -LayoutPath "Layout.xml" -MountPath "E:\MountedImage"

This will generate an error. You cannot end -MountPath with a '' character, if you do, PowerShell throws the error:
Import-StartLayout : The path B:\WIMs\Test\ did not resolve to a file.

If you format the command:
PS C:\ Import-StartLayout -LayoutPath "Layout.xml" -MountPath "E:\MountedImage"
You will receive the following error:
Import-StartLayout : Could not find a part of the path
'E:\MountedImageUsers\Default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml'.
Note the missing '\' character between "MountedImage" and "Users"
This appears to be an error in the Import-StartLayout commandlet.

For a workaround, I used Junction64.exe to create the expected 'E:\MountedImageUsers' junction targeted to 'E:\MountedImage\Users'

At this point, the command completed successfully. I removed the dummy junction, and was able to commit the changes and Un-Mount the wim file.
PS C:\ DISM.exe /Unmount-Wim /MountDir:'E:\MountedImage' /commit

I created a runbook on several automation accounts that move around files and folders on Datalake Storage Accounts (gen 1). The runbook works without hitches on 2 automation accounts, but did not work on the other 2.

There were quite a few differences in the versions of the added modules: the runbook worked on the older versions of the modules, but not the newer. Specifically the cmdlet Move-AzureRmDataLakeStoreItem threw an error on the newer versions:
"Account name ***.azuredatalakestore.net/ is invalid. Specify the full account including the domain name."

After trying quite a few iterations of writing the account name (just the name, "***", as it should be according to documentation; "***.datalakestore.net/"; "adl://***.datalakestore.net";...), I finally reverted the modules to older versions, which solved the problem. I would assume the issues arises from the AzureRM.DataLakeStore module, given that the cmdlet resides there, but I'm not entirely sure (I reverted all modules).

ClassA.psm1
------------------
class ClassA
{
[string]Execute()
{
return "this is from ClassA"
}
}

ClassB.psm1
------------------
class ClassB
{
[string]Execute()
{
return "this is from ClassB"
}
}

ImportClasses.ps1
-------------------------
using module 'D:\Exemple\Atelier\ClassImportProblem\ClassA.psm1'
using module 'D:\Exemple\Atelier\ClassImportProblem\ClassB.psm1'

process_Classes.ps1
----------------------------
using module 'D:\Exemple\Atelier\ClassImportProblem\ImportClasses.ps1'

$a = [ClassA]::new()
$b = [ClassB]::new()

class HustonweHaveAProblem
{
[void]HereWeGo(){
$a = [ClassA]::new()
$b = [ClassB]::new()
}
}

Observation:

From that point, instances of ClassA and ClassB are working fine in the process_Classes script. But instances of ClassA and ClassB within the class HustonWeHaveAProblem{} throw errors.

Actual result:

At D:\Exemple\Atelier\ClassImportProblem\process_Classes.ps1:9 char:15
+ $a = [ClassA]::new()
+ ~~~~~~
Unable to find type [ClassA].

At D:\Exemple\Atelier\ClassImportProblem\process_Classes.ps1:10 char:15
+ $b = [ClassB]::new()
+ ~~~~~~
Unable to find type [ClassB].
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : TypeNotFound

Expected Result:

Instances of classes should work within a class.