There are already PowerShell commands for reading searching and updating registry entries. I don’t think anyone is replacing one with the other, though.
Devices and Printers in Windows can go to hell where it belongs.
I guess I wasn’t clear. The average Windows user isn’t aware of PowerShell and would hardly be able to use reg itself. I agree that it is a great tool for managing registry in an environment, but I have seen professional technicians darn near cry over using cd to traverse directories.
Yes, and I’ve ran in to several guides that have used the powershell regedit commands instead of the GUI. Not only do the commands already exist, but they’re absolutely something some prefer over the GUI, even on Windows.
There are already PowerShell commands for reading searching and updating registry entries. I don’t think anyone is replacing one with the other, though.
Devices and Printers in Windows can go to hell where it belongs.
I guess I wasn’t clear. The average Windows user isn’t aware of PowerShell and would hardly be able to use reg itself. I agree that it is a great tool for managing registry in an environment, but I have seen professional technicians darn near cry over using cd to traverse directories.
Hey, and PowerShell commands aren’t GUI, bringing us back to the point of this post…
Yes, and I’ve ran in to several guides that have used the powershell regedit commands instead of the GUI. Not only do the commands already exist, but they’re absolutely something some prefer over the GUI, even on Windows.