I ended up writing extensively about customizing your PowerShell command prompt at my site. The reason for this is that the post is very detailed and longer than the posts we usually do on 4sysops. If you would like to know more check out my article here: https://www.commandline.ninja/customize-pscmdprompt/
The tool in this article does not accept pipeline input because i did not include the parameter to do so. This required to be able to pass a list to the function. Take a look at my website https://www.commandline.ninja . I'll write up a newer version of this tool on my site this week.
Giving credit to you as my online ‘mentor’, I now have scripts on how to automate VM creation (complete with virtual hard drive and Win10 OS, and virtual network). Another one that I was able to create is a script that automates network configuration and internet settings configuration to enable internet access for the generated VMs. All thanks to you!
Now as I went back in here, it seems like I’m not the only one having trouble with parameter availability across Powershell versions. We use Powershell 5.1 in here. Now I’m looking forward to create 2 programs/utilities out of the 2 scripts that I’ve mentioned above, complete with password verification before you can use said utilities. However, I’ve just found out that the parameters -MaskInput and -AsPlainText are only available in PowerShell 7.0.
Admitting again that I’m a newbie in PowerShell coding, I wanted to create codes to verify equality of passwords being entered. If you have a more efficient syntax that is 5.1 friendly, that would be great! But my obvious question should be: What equivalent parameters can I use? Or is there a workaround set of syntax in 5.1 so I can convert to plain text string what has been stored in System.Security.SecureString (in readable or unencrypted form, of course).
Ah thanks for your comment. I now understand a bit of why it wasn’t working before. I was running the remove/block script by as is without having used your add extension script first. After I ran the add extension script and then followed up with the removal it works as intended. When I ran this without using the add extension script it would just disable and grey out the ability to enable the extension but doesn’t remove the extension from the list (chrome://extension). Would you be able to expand on how I could run the removal/block script, and have it also remove the it from the list without going through the add extension script first? Hopefully that makes sense haha.
Thanks for the write up. From my understanding of this script should also remove the extension from the Chrome extension list (chrome://extension) right? If it is meant to I can’t seem to get that bit to work. If not how does one remove the extension from the chrome list?
Error 0x800f0954 usually occurs at the time of installing the .NET Framework or sub-components on Windows 10. Here’s how to resolve this issue in simple steps.
In recent days, most Windows 10 users are reporting error 0x800f0954 while installing .NET Framework 3.5 or its subcomponents. Whatever may be the reason behind the error, the good thing is that you can fix the error by following some simple steps. Here are the best possible solutions to deal with this situation.