Forum Discussion
Feb 09, 2024
Get-StartApps : The term 'Get-StartApps' is not recognized as the name of a cmdlet, function, script
I have a command such as
(Get-StartApps | Where-Object name -eq 'Notepad').AppId
or just simply
Get-StartApps
which works just fine via PowerShell ISE.
I, on the other h...
- Feb 11, 2024
The only suggestion I have now is replacing your "powershell.exe" statement with a full path alternative of:
C:\Windows\SysNative\WindowsPowerShell\v1.0\powershell.exeCheers,
Lain
Feb 09, 2024
I've come up with a workaround, still testing, but using the following seems to work
((New-Object -ComObject Shell.Application).NameSpace('shell:::{4234d49b-0245-4df3-b780-3893943456e1}').Items() | Where-Object { $_.name -like 'Notepad' } ).Path
but I'd still love to understand why the standard CmdLet doesn't work. Are there others that act in the same manner and should be avoided? How can I identify them so as to not waste countless hours fighting with them?
((New-Object -ComObject Shell.Application).NameSpace('shell:::{4234d49b-0245-4df3-b780-3893943456e1}').Items() | Where-Object { $_.name -like 'Notepad' } ).Path
but I'd still love to understand why the standard CmdLet doesn't work. Are there others that act in the same manner and should be avoided? How can I identify them so as to not waste countless hours fighting with them?