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.

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

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.

Integrated Modules are not loaded if you have a Network Path in $env:PSModulePath which is not reachable.

##############
I have customized the PSModulePath:

PS C:\Users\username> ($env:PSModulePath).split(';')
C:\Users\username\Documents\WindowsPowerShell\Modules
C:\Program Files\WindowsPowerShell\Modules
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
c:\Program Files\Microsoft Security Client\MpProvider\
C:\Program Files\Microsoft Monitoring Agent\Agent\PowerShell\
\\my.domain\share\Modules\

##############
If i try to execute e.g. Invoke-RestMethod

PS C:\Users\username> Invoke-RestMethod
Invoke-RestMethod : The 'Invoke-RestMethod' command was found in the module 'Microsoft.PowerShell.Utility', but the
module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'.
At line:1 char:1
+ Invoke-RestMethod
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Invoke-RestMethod:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CouldNotAutoloadMatchingModule

PS C:\Users\username> Get-Command Invoke-RestMethod
Get-Command : The term 'Invoke-RestMethod' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Get-Command Invoke-RestMethod
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Invoke-RestMethod:String) [Get-Command], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand

PS C:\Users\username> Import-Module Microsoft.PowerShell.Utility -Verbose
VERBOSE: Loading module from path
'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Microsoft.PowerShell.Utility\Microsoft.PowerShell.Utility.psd1'.
Import-Module : The network path was not found
At line:1 char:1
+ Import-Module Microsoft.PowerShell.Utility -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], IOException
+ FullyQualifiedErrorId : System.IO.IOException,Microsoft.PowerShell.Commands.ImportModuleCommand

Steps to reproduce
------------------
Disable-ScheduledTask -TaskName "Data Integrity Scan for Crash Recovery"
Disable-ScheduledTask : The system cannot find the file specified.
At line:1 char:1
+ Disable-ScheduledTask "Data Integrity Scan for Crash Recovery"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [
Disable-ScheduledTask], CimException
+ FullyQualifiedErrorId : HRESULT 0x80070002,Disable-ScheduledTask

Expected behavior
-----------------
This should disable the scheduled task and not crash.

You can workaround this by searching for the task object and disabling that way:

$Name = "Data Integrity Scan for Crash Recovery"
Get-ScheduledTask | where-object {($_.TaskName -eq $Name)} | Disable-ScheduledTask

Actual behavior
---------------
Crashes with the following exception:
Disable-ScheduledTask : The system cannot find the file specified.
At line:1 char:1
+ Disable-ScheduledTask "Data Integrity Scan for Crash Recovery"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [
Disable-ScheduledTask], CimException
+ FullyQualifiedErrorId : HRESULT 0x80070002,Disable-ScheduledTask

Environment data
----------------
Name Value
---- -----
PSVersion 5.1.15063.296
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.296
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Problem:

Get-AuthenticodeSignature does not return a time stamper certificate for files which have been time stamped with a valid time stamp server.

Steps to reproduce:

Using signtool.exe (from Windows SDK), view the signature info for signtool.exe. Verify that it has been time stamped, and that you can see the time stamper certificate.

Using Get-AuthenticodeSignature, view the signature of signtool.exe. Notice that the TimeStamperCertificate field is blank.

Consequences:

Powershell will report any signed file as valid as long as the signature is valid, regardless of whether or not the timestamp is valid.

Powershell version:
Major Minor Build Revision
----- ----- ----- --------
5 1 14393 1066

Invoke-RestMethod and Invoke-WebRequest Encoding bug

This is 4 years old bug,from Invoke-RestMethod and Invoke-WebRequest was born.

【Cause of the bug】
Utf8 web page incorrectly identified as iso8859-1.
Mistakenly convert THE! utf8("false ISO-8859-1") source string to utf8.
There may be more encoding incorrectly identified,encoding incorrectly conversion errors.

【bug with powershell version】
all version
powershell 5.0 with windows10 10586 ：yes tested.

【test code】
Invoke-WebRequest -Uri 'http://www.msn.com'; # return chinese messy code
(Invoke-WebRequest -Uri 'http://www.msn.com').BaseResponse.CharacterSet # utf8 web page,but return ISO-8859-1

Invoke-RestMethod -Uri 'http://www.msn.com';

【how to fix】
convert string encoding.
from utf8 to THE! "false ISO-8859-1"

$utf8 = [System.Text.Encoding]::GetEncoding(65001)
$iso88591 = [System.Text.Encoding]::GetEncoding(28591) #ISO 8859-1 ,Latin-1

$wrong_string = Invoke-RestMethod -Uri 'http://www.msn.com';
$wrong_bytes = $utf8.GetBytes($wrong_string)

$right_bytes = [System.Text.Encoding]::Convert($utf8,$iso88591,$wrong_bytes) #Look carefully
$right_string = $utf8.GetString($right_bytes) #Look carefully
write-host $right_string

【reporter】
I've been searching this bugs history list, I was the first reporter.
By the chinese powershell study & research group. QQ group No. is 183173532

【date】
2016-05-01