How to reproduce:

With this Azure pipelines yaml snippets:

The special character are all encoded. And when I attach a file I get 500 error. Please see https://gist.github.com/chenbojian/6fcb3a8c3bbe42cc2851a1eefe9f4324

- job: win2019

  pool:

    vmImage: windows-2019

  steps:

  - powershell: |

      $PSVersionTable

      cmd /c 'echo this will crash powershell 1>&2'

      cmd /c 'echo this will crash powershell 1>&2'

      cmd /c 'echo this will crash powershell 1>&2'

- job: win2016

  pool:

    vmImage: vs2017-win2016

  steps:

  - powershell: |

      $PSVersionTable

      cmd /c 'echo this will crash powershell 1>&2'

      cmd /c 'echo this will crash powershell 1>&2'

      cmd /c 'echo this will crash powershell 1>&2'

The win2019 job will fail at the second command. The win2016 job will succeed with 3 lines of messages.
Here I use cmd to write stderr stream just for demo the bug. In my real case, I need this to work because git and yarn and other tools will write warning to stderr.

I also tried with my custom windows 2019 image. It is better. It will fail at the first command. At least it have a consistency behaviour. The different between custom 2019 and microsoft hosted 2019 is the .net framework 4.8.

There is an issue https://github.com/microsoft/azure-pipelines-image-generation/issues/1436 said that this is a powershell bug. I do think this is a powershell's bug.

In PowerShell console in Windows 10 there is a serious problem that prevents entering capitalized letters (i.e. pressing Shift+Letter does nothing). This happens with most but not all letters and depends on the keyboard layout that was active when PowerShell console was started. If PowerShell console is started with English (US) keyboard layout, than typing in English works without problems (only Shift+Space not work, but I see another issue about it). After switching to Russian keyboard layout, most letters with Shift not work. Only ЦУШЩХЪФЫСТ can be typed. But when PowerShell console is started with Russian keyboard layout, it is even worse. Only ШЩХЪЫЯСТЬ can be entered in Russian keyboard layout and no capital letter at all can be entered in English layout.

I found a huge memory leak in project which appears after execution PS command. Here I create example that represent my problem in "TestCase" comment.

After memory usage investigation I found that most of memory occupied by inner structures from System.Management.Automation. So I start to search the way to release resources and found that the same behavior can be reproduced in PS:
Get-Module -ListAvailable | ForEach { Import-Module $_.Name }
Get-Command -ListImported -CommandType Cmdlet,Alias

I already have tried to initiated garbage collecting and to remove all new variables that appears after script execution. I even have tried to start new Runspace into PowerShell ISE to run script, but resources still didn't release.

During my research I found that this code still eat a bunch of memory. You can see it in "TestLeak" comment. But if we change this:
Get-Process *
to this:
$res = Get-Process *
then memory doesn't leak. Variable goes out of scope and then freed up by garbage collector. But in first case it looks like PowerShell stores results somewhere in inner structures. I have tried to add variable to my script to store cmdlet's results but nothing changed like my variable never goes out of scope!

I can't free memory no matter what I do! Do I do something wrong or it is some kind of problem?

P.S. Error appears when I try to attach the files so add code as comments!

Problem Description

If you are using the using module statement, it will load the module without any issues. However, if you make a change to the module and run the using module statement again without restarting your PowerShell session, it will not load the new modified module into memory, and instead will continue to use the old existing module that was loaded. This makes doing development with using module statements very tedious as you must continually reload your PowerShell session whenever you make changes to the module.

Ideally we would just use Import-Module -Name [module name] -Force to avoid this issue, but that does not work for importing classes, so the using module statement must be used.

Steps to reproduce

Create the following module and script files:

In TestModule.psm1:
```powershell
class TestClass
{

[string] $ClassPropertyText = "Initial text"

}

function Get-ModuleFunctionText()
{

return "Initial text"

}

Export-ModuleMember -Function Get-ModuleFunctionText
```

In Test.ps1:
```powershell
using module '.\TestModule.psm1'

$instance = [TestClass]::new()
$instance.ClassPropertyText

Get-ModuleFunctionText
```

Run Test.ps1 and it will output:

Initial text
Initial text


Then modify TestModule.psm1 to:
```powershell
class TestClass
{

[string] $ClassPropertyText = "Updated text"

}

function Get-ModuleFunctionText()
{

return "Updated text"

}

Export-ModuleMember -Function Get-ModuleFunctionText
```

Run Test.ps1 again and it will still output:

Initial text
Initial text


Expected behavior

When running Test.ps1 the 2nd time, it should output:
none
Updated text
Updated text


Environment data

<!-- provide the output of $PSVersionTable -->

```powershell
> $PSVersionTable
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 Info

The problem can be somewhat reduced by using both the using module statement and Import-Module -Force statement, like this:
```powershell
using module '.\TestModule.psm1'
Import-Module -Name '.\TestModule.psm1' -Force

$instance = [TestClass]::new()
$instance.ClassPropertyText

Get-ModuleFunctionText
```

This code would result in the following output:

Initial text
Updated text


So here the module code was updated, but the class code was not.

Proposed Solution

To fix this issue I propose adding a -Force flag to the using module statement that forces the module to be reloaded into memory; the same way that the -Force flag works for the Import-Module cmdlet. This will allow developing code that uses the class construct to work much smoother.

I also proposed this same change to PowerShell Core at: https://github.com/PowerShell/PowerShell/issues/7654

I can't use power shell. If I open it, print these error
ハンドルされていない例外: System.Runtime.InteropServices.SEHException: 外部コンポーネントが例外をスローしました。
場所 System.Reflection.RuntimeAssembly.GetResource(RuntimeAssembly assembly, String resourceName, UInt64& length, StackCrawlMarkHandle stackMark, Boolean skipSecurityCheck)
場所 System.Reflection.RuntimeAssembly.GetManifestResourceStream(String name, StackCrawlMark& stackMark, Boolean skipSecurityCheck)
場所 System.Resources.ManifestBasedResourceGroveler.GetManifestResourceStream(RuntimeAssembly satellite, String fileName, StackCrawlMark& stackMark)
場所 System.Resources.ManifestBasedResourceGroveler.GrovelForResourceSet(CultureInfo culture, Dictionary`2 localResourceSets, Boolean tryParents, Boolean createIfNotExists, StackCrawlMark& stackMark)
場所 System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo requestedCulture, Boolean createIfNotExists, Boolean tryParents, StackCrawlMark& stackMark)
場所 System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
場所 System.Resources.ResourceManager.GetString(String name, CultureInfo culture)
場所 System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
場所 System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input)
場所 System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
場所 System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
場所 System.Management.Automation.Runspaces.PipelineThread.WorkerProc()
場所 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
場所 System.Threading.ThreadHelper.ThreadStart()