I am trying to build custom Windows System Utility script which offers some tasks with relevant keypress choices.

For cleanup task, I am trying to invoke CCleaner64.exe from this script, with it's correct switches as mentioned here. And the script I built so far is below:

$ScriptDir = Split-Path $MyInvocation.MyCommand.Path
if (-Not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator')) {

if ([int](Get-CimInstance -Class Win32_OperatingSystem | Select-Object -ExpandProperty BuildNumber) -ge 6000) {

    $CommandLine = "-File `"" + $MyInvocation.MyCommand.Path + "`" " + $MyInvocation.UnboundArguments

    Start-Process -FilePath PowerShell.exe -Verb Runas -ArgumentList $CommandLine

    Exit

}

}
Set-Location $ScriptDir; Echo 'Current Directory: ' + (Get-Location | Out-String)

function SysUtilMenu {

param (

    [string]$Title = 'Windows System Utility'

)

Clear-Host

Write-Host "============ $Title ==========="

Write-Host "1: Do task 1 here."

Write-Host "2: Cache/Temp Files Cleanup."

Write-Host "Q: Exit this Application."

}

Do
{

SysUtilMenu

$selection = Read-Host "Press key to run given task..."

switch ($selection)

{

    '1' {

        ## Do task 1 here...

    } '2' {

        $CclnrApp64 = "$Env:ProgramFiles\CCleaner\CCleaner64.exe"

        Start-Process $CclnrApp64 -ArgumentList '/Clean'

        Start-Process $CclnrApp64 -ArgumentList '/Registry'

    }

}

}
Until($selection -eq 'q')

But when I press '2', it doesn't invoke CCleaner64.exe in the taskbar, which I checked.

I don't get, why the same Start-Process line doesn't work in that script, but if I open the Powershell terminal separately and run below commands one-by-one, it works perfectly ?

$CclnrApp64 = "$Env:ProgramFiles\CCleaner\CCleaner64.exe"
Start-Process $CclnrApp64 -ArgumentList '/Clean'

Is it due to Script's Self-Elevation, I have taken care of setting the location of the script instead of C:\Windows\System32.

Suggestion with detailed explanation is greatly appreciated...

Summary of the issue

Currently powershell is unable to implement [Composition Over Inheritance](https://www.makeuseof.com/tag/basic-programming-principles/#composition-over-inheritance) because of a lack of support for custom interfaces, which prevents multiple inheritance of behavior interfaces

There is a way to get it to work, but it only works when running the code by hand, not in automated scripts

Proposed technical implementation details (optional)

The issue with the workaround boils down to a problem in the parser error: InterfaceNameExpected
It fails to recognize that using Add-Type will add types, instead it incorrectly assumes the given type will not be available

I think we should either allow a keyword to override this error, or educate the parser on the usage of Add-Type

Examples

I have included 3 examples (each has a readme.txt with relevant details):
A single file script that fails when run as a whole, but works if you manually run it line by line
A split that works, but is forced to have an incorrect dependency tree
A split that fails, because it's using a correct dependency tree

Note: The splits use dot sourcing, you'll need to adjust the paths to the appropriate folders on your computer

Files

(the click to upload isn't working [on chrome or edge] so here are dropbox links)

Fail - Single File: https://www.dropbox.com/s/xuava34s1dglqyh/Fail%20-%20Single%20File.zip?dl=0

Success - Bad Dependency Layout: https://www.dropbox.com/s/sz17020w56mtjpx/Success%20-%20Bad%20Dependancy%20layout.zip?dl=0

Fail - Good Dependency Layout: https://www.dropbox.com/s/fr38uj6b45jhqk4/Fail%20-%20Good%20Dependency%20Layout.zip?dl=0

This issue is a problem I'm having using Add-VMHardDiskDrive.

I am not able to use a WSL path as argument. It seems the cmdlet can't access paths located in other network devices.

Steps to reproduce


Add-VMHardDiskDrive -VMName test -Path \\wsl$/Ubuntu/home/<image path>


Expected behavior

The cmdlet returns the success message describing that the disk was mounted successfully in the hyper-v virtual machine specified.

Actual behavior

```
Add-VMHardDiskDrive : 'test' failed to add resources to
'test'.
An unexpected error occurred: The network name cannot be found. (0x80070043).
'test' failed to add resources. (Virtual machine ID
4F4777B2-4DFD-4A07-89B6-44FFC5BE2D3F)
'main-image-1611598805' encountered an unexpected error: The network name cannot be
found. (0x80070043). (Virtual machine ID 4F4777B2-4DFD-4A07-89B6-44FFC5BE2D3F)
At line:1 char:1
+ Add-VMHardDiskDrive -VMName test -Path \wsl$/Ubunt ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [Add-VMHardDiskDrive], Virtualizatio 

nException

+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.A 

ddVMHardDiskDrive
```

Environment data

```
Name Value

PSVersion 5.1.19041.610

PSEdition Desktop

PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}

BuildVersion 10.0.19041.610

CLRVersion 4.0.30319.42000

WSManStackVersion 3.0

PSRemotingProtocolVersion 2.3

SerializationVersion 1.1.0.1
```

Can someone explain why IF statements fails when enclosed in () without a variable? See example below:

$x = 5
$y = 6

Fails

( if ($x -eq $y) { "Match" } ELSE { "No Match" }  )

Works

if ($x -eq $y) { "Match" } ELSE { "No Match" }  

( $xy = if ($x -eq $y) { "Match" } ELSE { "No Match" }  )

Returned Error

if : The term 'if' 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.

When importing a module that uses expressions to define custom powershell classes, if a class definition references two or more previously defined, custom powershell classes, PowerShell runtime throws an "Could not load type" exception.

Version: PowerShell 5.1, Windows 10
Code to reproduce:
The below code can either be put into into a module file or run directly in a powershell window:

Invoke-Expression @'

enum EnumOne {

    One = 1

    Two = 2

    Three = 3

    Four = 4

}

'@


Invoke-Expression @'

class ClassOne {

    [string]$Property1

    ClassOne([string]$prop1) {

        $this.Property1 = $prop1

    }

}

'@

Invoke-Expression @'

class ClassTwo {

    [ClassOne]$ClassOne

    [EnumOne]$Enum

    ClassTwo([ClassOne]$one, [EnumOne]$enum) {

        $this.ClassOne = $one

        $this.Enum = $enum

    }

}

'@

Error Output:

Invoke-Expression : At line:1 char:1

+ class ClassTwo {

+ ~~~~~~~~~~~~~~~~

Error during creation of type "ClassTwo". Error message:

Could not load type 'EnumOne' from assembly '⧹powershell, 

Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.

At line:1 char:1

+ Invoke-Expression @'

+ ~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : ParserError: (:) [Invoke-Expression], 

ParseException

    + FullyQualifiedErrorId : TypeCreationError,Microsoft.PowerShell.Commands.InvokeExpressionCommand

Entering this reproducibly hangs Windows PowerShell 5.1:

$r = iwr 'https://marketplace.visualstudio.com/items?itemName=austin.code-gnu-global'
$r

Here's what one gets with Set-PSDebug -Trace 2:

> $r
DEBUG: 94+ >>>> {
DEBUG: ! CALL function '<ScriptBlock><DynamicParam>'
DEBUG: 97+ >>>> $getCommand = $executionContext.InvokeCommand.GetCmdlet(
DEBUG: ! SET $getCommand = 'Get-Command'.
DEBUG: 99+ >>>> $foreachObject = $executionContext.InvokeCommand.GetCmdlet(
DEBUG: ! SET $foreachObject = 'ForEach-Object'.
DEBUG: 101+ >>>> $whereObject = $executionContext.InvokeCommand.GetCmdlet(
DEBUG: ! SET $whereObject = 'Where-Object'.
DEBUG: 107+ >>>> $command = & $getCommand Out-Default -Type Cmdlet
DEBUG: ! SET $command = 'Out-Default'.
DEBUG: 108+ >>>> $targetParameters = @{}
DEBUG: ! SET $targetParameters = 'System.Collections.Hashtable'.
DEBUG: 109+ >>>> $PSBoundParameters.GetEnumerator() |
DEBUG: 118+ >>>> $argList = @($targetParameters.GetEnumerator() |
DEBUG: 118+ $argList = @( >>>> $targetParameters.GetEnumerator() |
DEBUG: ! SET $argList = ''.
DEBUG: 123+ >>>> $command = $null
DEBUG: ! SET $command = ''.
DEBUG: 126+ >>>> $command = & $getCommand Out-Default -Type Cmdlet `
DEBUG: ! SET $command = 'Out-Default'.
DEBUG: 134+ >>>> $dynamicParams = @($command.Parameters.GetEnumerator() |
DEBUG: 134+ $dynamicParams = @( >>>> $command.Parameters.GetEnumerator() |
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: 135+ & $whereObject >>>> { $.Value.IsDynamic })
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 135+ & $whereObject { >>>> $.Value.IsDynamic })
DEBUG: 135+ & $whereObject { $.Value.IsDynamic >>>> })
DEBUG: ! SET $dynamicParams = ''.
DEBUG: 139+ if ( >>>> $dynamicParams.Length -gt 0)
DEBUG: 154+ >>>> }
DEBUG: 13+ >>>> {
DEBUG: ! CALL function '<ScriptBlock><Begin>'
DEBUG: 19+ >>>> $foreachObject = $executionContext.InvokeCommand.GetCmdlet(
DEBUG: ! SET $foreachObject = 'ForEach-Object'.
DEBUG: 22+ >>>> $wrappedCmd = $ExecutionContext.InvokeCommand.GetCommand(
DEBUG: ! SET $wrappedCmd = 'Out-Default'.
DEBUG: 28+ >>>> $targetParameters = @{}
DEBUG: ! SET $targetParameters = 'System.Collections.Hashtable'.
DEBUG: 29+ >>>> $PSBoundParameters.GetEnumerator() |
DEBUG: 38+ >>>> $newPipeline = { & $wrappedCmd @targetParameters }
DEBUG: ! SET $newPipeline = ' & $wrappedCmd @targetParameters '.
DEBUG: 39+ >>>> $finalPipeline = $newPipeline.ToString()
DEBUG: ! SET $finalPipeline = ' & $wrappedCmd @targetParameters '.
DEBUG: 43+ >>>> $steppablePipeline = [ScriptBlock]::Create(
DEBUG: ! SET $steppablePipeline = 'System.Management.Automation.SteppablePipel...'.
DEBUG: 45+ >>>> $steppablePipeline.Begin($PSCmdlet)
DEBUG: 49+ >>>> }
DEBUG: 1+ >>>> $r
DEBUG: ! CALL function '<ScriptBlock>'
DEBUG: 52+ >>>> {
DEBUG: ! CALL function '<ScriptBlock><Process>'
DEBUG: 56+ if( >>>> ($ -is [System.IO.DirectoryInfo]) -or ($ -is [System.IO.FileInfo]))
DEBUG: 62+ elseif( >>>> $ -is [System.ServiceProcess.ServiceController])
DEBUG: 68+ elseif( >>>> $ -is [Microsoft.Powershell.Commands.MatchInfo])
DEBUG: 74+ >>>> $steppablePipeline.Process($)

Moving to PS7 is not an option since I need $r.ParsedHTML

I really think there is a bug in Where-Object with $_.LastAccessTime
It always returns Last Write Time, NOT Last Access Time. However, Select-Object works..

Sample -
Get-ChildItem -Recurse -Path c:\ | Where-Object {$_.LastAccessTime -le (Get-Date).AddDays(1)}

Result -

Mode LastWriteTime Length Name

...list of files...

I have tested with PowerShell 2.0 (Windows 2008 R2) 4.0 (Windows 2012 R2) and 5.1 (Windows 2016 and Windows 10).

It WORKS as expected on Powershell 2.0

However, this sample works, but I am unable to finger out how to do anything (like Remove-Item) with the results.

< save the below as a .ps1 file and pass 2 parameters, c:\ and 1 >
Param([string[]]$path, [int]$numberDays)
$cutOffDate = (Get-Date).AddDays(-$numberDays)
Get-childItem -Path $path -recurse -force | where {!$.PsIsContainer} | Select Fullname,LastAccessTime | Where-Object {$.LastAccessTime -ile $cutOffDate }

Put this directly into the Office 365 Admin console if you are forcing us to use something that never works unless you've become a professional with it AND get all the updates on all the changes that happen in just a single month, so put it directly in Office 365 just like Azure has and YOU keep it updated with the right libraries and modules and all that so when we need to run a command, we don't have to search for 45 minutes to get it going, or when you need to run tech support, you know the platform it's running on because it's yours, not ours.