I have a problem with loading classes from a module.

Script is just two lines as following:
using module AzureAD
class TestClass { [Microsoft.Open.AzureAD.Model.Application] static DoIt() { return $null; } }

If I run this, using .\Script.ps1 I get the following error:
At C:\path\Script.ps1:3 char:20
+ class TestClass { [Microsoft.Open.AzureAD.Model.Application] static D ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unable to find type [Microsoft.Open.AzureAD.Model.Application].
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : TypeNotFound

However, if I run "using module AzureAD" from the command line first and then run the script, it works fine...

What is the difference in running using module from the command line versus running it in the script?

Steps to reproduce

Windows 10 Pro, 1703 15063.608
"Developer mode" activated

PS D:\Partage\tmp> New-Item -Type File a

Répertoire : D:\Partage\tmp

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 04/10/2017 11:42 0 a

PS D:\Partage\tmp> New-Item -Type SymbolicLink -Target a -Path b
New-Item : Cette opération nécessite un privilège d'administrateur.
Au caractère Ligne:1 : 1
+ New-Item -Type SymbolicLink -Target a -Path b
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : PermissionDenied: (D:\Partage\tmp\a:String) [New-Item], UnauthorizedAccessException
+ FullyQualifiedErrorId : NewItemSymbolicLinkElevationRequired,Microsoft.PowerShell.Commands.NewItemCommand

PS D:\Partage\tmp>

Well this did not work, let's try with good old CMD.exe

PS D:\Partage\tmp> cmd
Microsoft Windows [version 10.0.15063]
(c) 2017 Microsoft Corporation. Tous droits réservés.

D:\Partage\tmp>mklink b a
Lien symbolique créé pour b <<===>> a

D:\Partage\tmp>

Now let's do it as Administrator, to check it's not some weird syntax issue

PS D:\Partage\tmp> ri b
PS D:\Partage\tmp> New-Item -Type SymbolicLink -Target a -Path b

Directory: D:\Partage\tmp

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---l 04/10/2017 11:45 0 b

PS D:\Partage\tmp>

Expected behavior

As I'm in "developper mode" I expect New-Item -Type SymbolicLink to work without elevation.
Actual behavior

I get an incorrect "elevation required" error message, incorrect because mklink works in the same context
Environment data

PS D:\Partage\tmp> $PSVersionTable

Name Value
---- -----
PSVersion 5.1.15063.608
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.608
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Hi,
Recently I am working on a Telegram Bot creation with power shell, everything working fine except uploading the images via API.

If I use cURL, it is working fine using following command, So, technically it should work with native PowerShell commandlet.

curl -s -X POST "https://api.telegram.org/bot11111111:Mykey/sendPhoto?chat_id=-123456789&quot; -F photo="@D:\MyPic.JPG" -F caption="Test"

I have already tried following, but none worked. As per the API Guide (https://core.telegram.org/bots/api), we have to use multipart/form-data for uploading any file, for cURL, without specifying this also works.

Invoke-RestMethod -Uri "https://api.telegram.org/bot$MyBotKey/sendPhoto?chat_id=XXXXXXXXX&quot; -Method Post -InFile "D:\MyPic.JPG" -ContentType "multipart/form-data"
Invoke-WebRequest -Uri "https://api.telegram.org/bot$MyBotKey/sendPhoto?chat_id=-XXXXXXXXX&quot; -Method Post -InFile "D:\MyPic.JPG" -ContentType "multipart/form-data"

For Invoke-RestMethod, I have got this:
{"ok":false,"error_code":400,"description":"Bad Request: there is no photo in the request"}

For Invoke-WebRequest, I have got this,
The remote server returned an error: (400) Bad Request.

For Invoke-WebRequest without content type, I have got this,
{"ok":false,"error_code":400,"description":"Bad Request: there is no photo in the request"}

I guess this might be a Bug.

Hi there

in this case I have to remove and reinstall an OS while booting from usb stick. But this is only one example - it´s not the first time im seeing this behaviour.

if (Test-path c:) {Get-Volume -DriveLetter c | Get-Partition | Remove-PartitionAccessPath -AccessPath c:\}

In this line the term C is used three times

First time as c: (here would be c:\ also possible)
Second time as c (neither c: nor c:\ is working here)
Third time as c:\ (neither c nor c: is working here)

I´m working with variables - this means I have to create 3 Variables to obey all this rules.

My suggestion - decide for one notation and use this consistently! everywhere!

The ErrorAction parameter on Stop-transcript doesn't work.

for instance with SilenlyContine:

PS G:\> Stop-Transcript -ErrorAction SilentlyContinue
Stop-Transcript : An error occurred stopping transcription: The host is not currently transcribing.
At line:1 char:1
+ Stop-Transcript -ErrorAction SilentlyContinue
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptCommand

Or with stop:
Script: Stop-Transcript -ErrorAction Stop; write-output "This message sould not be printed"
Result: Stop-Transcript : An error occurred stopping transcription: The host is not currently transcribing.
At home\Untitled4.ps1:1 char:1
+ Stop-Transcript -ErrorAction Stop
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptCommand

This message sould not be printed

I got some weird data when running below cmdlet

Get-MessageTrace -StartDate "09/11/2017 00:00:00" -EndDate "09/15/2017 00:00:00" -PageSize 10 -Page 1 | Get-MessageTraceDetail | Select-Object Date, MessageTraceID, Event, Data, Detail | Out-GridView

It seems the last event of the first MessageTraceID keeps repating itself and was added next to last event of the next MessageTraceID. And its data keep growing. Please see below image for the clear representation of the issue.
https://1drv.ms/i/s!AtOz2sztWjOapgIwkbjyq-sy4_jm

Below image is the correct MessageDetail of MessageTraceId 2b87f940-0eee-4c39-71a9-08d4f9757430
https://1drv.ms/i/s!AtOz2sztWjOapgPFCL102diF6jRz

And below image is the correct MessageDetail of MessageTraceId f602c9c7-2a5b-4a5a-1256-08d4f8e9ba58
https://1drv.ms/i/s!AtOz2sztWjOapgSFXfJiKurb23w0

Can you please check why it is happening?

Thanks in advance.

===================
> $PSVersionTable

Name Value
---- -----
PSVersion 5.1.14393.1198
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.1198
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
================================

I am using the first example in the syntax box from here:
https://technet.microsoft.com/en-us/library/jj873971(v=wps.630).aspx

The description for PreserveExistingBackups confuses me a bit, since its mentioning network shares, but the syntax example is for a disk location. I think I need it for the disk location, so I tried with the lines below.

Set-WBPerformanceConfiguration -OverAllPerformanceSetting AlwaysFull
$policy = New-WBPolicy
$disks = Get-WBDisk
$backupLocation = New-WBBackupTarget - Disk $disks[12] -PreserveExistingBackups $true -Label "Backup"
Add-WBBackupTarget -Policy $policy -Target $backupLocation

If I singlestep the script then everything looks fine after I have initialized the variable $backupLocation. The PreserveExistingBackups are set to true, when I recall the variable.
But once I execute the last line, where I use the Add-WBBackupTarget, then the setting of my $backupLocation variable is changed to false for the PreserveExistingBackups.

I am on a Windows Server 2012 R2 with PS 5.0.10586.117