After you've carried out some action - disabled an unnecessary service, say - click View > PowerShell Script, select the PowerShell Script tab, and you'll see scripts representing everything you've just done - perfect when you're learning the language.
This isn't so very unusual, but then that's where the PowerShell side comes in. Click a service, say, and you're able to start, stop, suspend, resume or restart it, change its start mode, set new logon accounts and passwords, and so on. Launch PowerGUI and you'll find details on every aspect of your system: running processes, services, event logs, network setup, your Registry, drive configuration, user groups and more.Īnd this isn't just a system information tool: you can carry out actions on most of the details you're viewing, too. So if you're not interested in scripting or PowerShell, that's not a problem. However, if I deleted the command value with the random string in it, using the "Open with PowerGUI Script Editor" option worked without a problem.Īgain, I'd like to note that it's not any of the SAPIEN products that modifies this registry, and we cannot guarantee any results when attempting this workaround.PowerGUI is an unusual combination of a system management tool and a graphical user interface for Windows PowerShell.īoth elements of the program can be used separately. When this value was present on my machine, using the "Open with PowerGUI Script Editor" option when right clicking on a ps1 file would open the script in PowerShell Studio. With that being said, the problem appears to be related to the existence of the command REG_MULTI_SZ value in the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Microsoft.PowerShellScript.1\Shell\open\command key which is updated by the PowerGUI program on installation. I'd first like to say that before attempting any of the following workaround steps that you perform a full backup of your registry and be aware that we are not responsible for any negative side effects that may be incurred. After some research, I've narrowed down the cause of this issue.
0 kommentar(er)
