Windows 10: windows powershell script not working.

Hallo!Problem: I wan´t to use a script to turn on autohide taskbar in desktop mode.if I put in: " powershell -command "&{$p='HKCU:SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StuckRects3';$v=Get-ItemProperty -Path $p.Settings;$v[8]=3;&Set-ItemProperty -Path $p -Name Settings -Value $v;&Stop-Process -f -ProcessName explorer}" , in powershell it works.But if I try the same command in a script-file I get following error://At line:1 char:111 + ... n\Explorer\StuckRects3';=Get-ItemProperty -Path .Settings;[8]=3;&Se ... +

:)

 

PowerShell scripts not working with Call operator

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing issues while developing a PowerShell script using the Call operator. I would suggest you to refer the articles

The Windows PowerShell ISE.



However, as the issue is related to developing PowerShell scripts, I would suggest you to post your query on

MSDN forums, where we have expertise and developers who are well equipped with the knowledge of developing PowerShell scripts in Windows.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

PowerShell scripts not working with Call operator

Hello

I have been developing a Powershell script using Powershell ISE, and for the most part i am very happy about it, however i have encountered what i believe to be a bug in the call operator (&).

When i use the call operator followed by a "pure" string everything works as it should, the command works and ISE runs as usual, but when i use the call operator followed by a variable, the command executes correctly, however ISE will no longer use the
intellisense function to automatically show a drop-down list of possible variables when using "$". It is still possible to press ctrl + space to force the drop-down to appear. This error will disappear when you delete the call operator or the variable.

Here is an eksample:
(This courses the problem)
$c = 'C:\Path\To\Script'
& $c

(This does not course the problem)
& 'C:\Path\To\Script'

I hope someone is able to help me understand what is happening here, and if it is a bug then give me an alternative solution to executing a script on the local PC though a script.

I use Powershell version 5.1.17763.503

***Original title: The Powershell call operator breaks my ISE***

 

Powershell script

Hi Muhammed DanishM S,

Thank you for posting your question in the Microsoft Community Forums.

I would like to let you know that the Windows PowerShell command-line and scripting language can be used to automate many Group Policy tasks, including configuring registry-based policy settings and various Group Policy Management Console (GPMC) tasks.

Refer to this article to know more.

‘Group Policy Cmdlets in Windows PowerShell’

For more information, I would suggest you to post your query in
MSDN Forums, where we have developers and support professionals who are well-equipped with the knowledge on PowerShell
scripts to assist you with your query.

Regards,

Srimadhwa B

Microsoft Community-Moderator