Issue
I am trying to write logs to a single log file using the PSlogging PowerShell module.

The Script is using the Foreach-object parallel.

The script works, But sometimes the script gets stuck in between.

Please help me to resolve it? Is there a better way to achieve this?

Powershell core 7

code

```
$sScriptVersion = '1.0'

$sScriptVersion = '1.0'
$sLogName = 'custom.log'
$sLogPath = "C:\Users\Dixon\Desktop\automation\azure\log"
$sLogFile = Join-Path -Path $sLogPath -ChildPath $sLogName

Start-Log -LogPath $sLogPath -LogName $sLogName -ScriptVersion $sScriptVersion

$allServers = $(Get-AzVM -Status)

try {

$allServers | ForEach-Object -parallel {


    $sScriptVersion = '1.0'

    $sLogName = "parallel-" + $_.Name +".log"

    #Log File Info

    $sLogPath = "C:\Users\Dixon\Desktop\automation\azure\log"

    $sLogFile = Join-Path -Path $sLogPath -ChildPath $sLogName

    Import-Module .\modules\pwshAzMod\pwshAzMod.psd1 -Force

    $version = "1.0.11"

    $vmName = $_.Name

    $vmLocation = $_.Location

    $vmResourceGroupName = $_.ResourceGroupName

    $powerState = $_.PowerState | Out-String

    if ($powerState -match "running") {

        if ($_.OSProfile.WindowsConfiguration) {

            Write-LogInfo -LogPath $sLogFile -Message  "Start --- Windows Servers --- $vmResourceGroupName $vmLocation $vmName $version $powerState"

            Write-LogInfo -LogPath $sLogFile -Message  "Done --- Windows Servers --- $vmResourceGroupName $vmLocation $vmName $version"

        } 

        elseif ($_.OSProfile.LinuxConfiguration) {

            $extensionName = "CustomScript"

            Write-LogInfo -LogPath $sLogFile -Message  "Start --- Linux Servers --- $vmResourceGroupName $vmLocation $vmName $version $powerState"

            Write-LogInfo -LogPath $sLogFile -Message  "Done --- Linux Servers --- $vmResourceGroupName $vmLocation $vmName $version"

        }

        else {

            Write-LogInfo -LogPath $sLogFile -Message  "OS Type not handled"

        }

    }

    else {

        if ($_.OSProfile.WindowsConfiguration) {

            Write-LogInfo -LogPath $sLogFile -Message  "Deallocated --- Windows Servers --- $vmResourceGroupName $vmLocation $vmName $version $powerState"

        }

        elseif ($_.OSProfile.LinuxConfiguration) {

            Write-LogInfo -LogPath $sLogFile -Message  "Deallocated --- Linux Servers --- $vmResourceGroupName $vmLocation $vmName $version $powerState"

        }

        else {

            Write-LogInfo -LogPath $sLogFile -Message "Deallocated --- Other Servers --- $vmResourceGroupName $vmLocation $vmName $version $powerState"

        }

    }

}  -ThrottleLimit 5

}
catch {

$errorMessage = $_

$errorMessage

}
finally {

Get-Content $sLogPath/parallel-*.log | Add-Content $sLogFile

Remove-Item –path $sLogPath\*  -Filter parallel*

Stop-Log -LogPath $sLogFile

}
```

Hello there, not too sure where to post my findings as this is my first time reporting a Windows bug, so I hope I chose the right category.

I discovered a potential bug in the Cmdlet Where-Object which involves the -LT option and misspelling the selection property. I reproduced the error on a clean VM of Windows 10 (please refer to the images attached), although I initially noticed this bug in Windows Server 2016. Instead of no output due to the wrong spelling of the property "Length", the initial output of the command piped into Where-Object is listed. This might result in errors in scripts not being detected because a wrong result is presented.

This bug only applies to the option -LT (lower than), -GT (greater than) does not seem to be affected, as you can see in my screenshots.

Please let me know, if you require any other pieces of information.

The "compress-archive" module stores path delimiters in non UNC format (backslashes instead of slashes) which differs from the builtin zipper in Win10 (Send to Zip-Archive).
This leads to unrecognized files on decompression by i.e. Microsoft Dynamics NAV 2016 (decrompression of an imported zipfile "ControlAddIn.Zip")
If you build the same archive with the Win10-Zipper, the files are recognized correctly.
Used PS-Version : 5.1 build 18362 rev 145
Win10-Pro 64bit version: 10.0.18362.267
Command executed from Visual Studio:
powershell Compress-Archive -Path ".\ControlAddIn\AddIn*" -CompressionLevel Fastest -DestinationPath "$(SolutionDir)ControlAddIn.zip"
I cannot append the two Zip-Archives to let you compare these files by yourself therefore I post an image of the differences ("PS-Compress-Archive Bug.jpg")
- "ControlAddIn.zip" was created with powershell
- "ControlAddIn_M.zip" was created with Send to Zip-Archive in Windows Explorer

Hey every body,

"New-AzVM" has a strange behaviour (maybe a bug), if you pass vn and subnet as parameters and
the vn exists but the subnet doesn't, it will try try to delete the vn (cascading) and recreate it. This
will fail if you have other VMs in the vnet but will succeed if you have empty subnets deleting all of them (OUCH!).

Steps to reproduce:

1. login to portal and create 1 vnet (say vnProd2 ) and 2 subnets (say snProd, snDev)


2. login to Azure from powershell (module AZ)


3. run the following command:
   New-Azvm -Location "northeurope" -ResourceGroupName "rgTest" -virtualnetworkname vnProd2 -SubnetName "snProd101" -Image CentOS -Name linux06
   In my head that command should create the new snProd101 since it doesn't exist, and it will, too bad it will recreate the vnet deleting the existent subnets snProd and snDev.