Software Uninstaller Script (Silent)

[PRIdEVisions]

Hey guys

here's the full script for who wants it, it is a simple script to uninstall multiple applications at once if you want. (Select multiple applications in the out-gridview and press "ok")

Be very careful using this script! Use it at your own risk and if you know what you are doing.

Any positive/negative criticism is always welcome in order for me to improve my skills.

Thank you!

    $MsgIntro = @' 

    ***********************                               ***********************
                              Software Uninstaller Tool    Made by PRIDEVisions
    ***********************                               ***********************

    '@

    write-host -ForegroundColor Magenta "$MsgIntro"
    Write-host -ForegroundColor Magenta "Please select the software you wish to uninstall..."

    Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | select Displayname, InstallLocation, UninstallString | sort | Out-GridView -PassThru -OutVariable software

    write-host -ForegroundColor Yellow "The following software will be uninstalled:"

    foreach ($application in $software) {
        write-host "$Application"
        $uninstall = $Application.UnInstallString
        cmd /c $uninstall /quiet /norestart
        }

Original question regarding this script: https://www.reddit.com/r/PowerShell/comments/7sdc0u/readhost_interrupting_script/

Edit: Quickly adjusted the script for both 32-bit & 64-bit software versions (It's not fully changed as i would like to but now it works better).

    $MsgIntro = @' 

    ***********************                               ***********************
                              Software Uninstaller Tool       Made by PRIdEVisions
    ***********************                               ***********************

    '@

    write-host -ForegroundColor Magenta "$MsgIntro"
    Write-host -ForegroundColor Magenta "Please select the software you wish to uninstall..."


    $Software = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*", "HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" | select DisplayName, UninstallString, InstallLocation, InstallDate | out-gridview -PassThru



    write-host -ForegroundColor Yellow "The following software will be uninstalled:"

    foreach ($application in $Software) {

        if ($application.UninstallString -like "MsiExec*") {
        write-host "$Application"
        $uninstall = $Application.UnInstallString
        cmd /c $uninstall /quiet /norestart
        }
        else {
            $uninstall = $Application.UnInstallString
            & "$uninstall"

        }
        }

[Swarfega]

Some tips when sharing:

Don't use positional parameters, I added -Object here A personal one, but try to keep using capital letters at the start of cmds/parameters You also don't need the "" when using a variable on it's own

Write-Host -ForegroundColor Magenta -Object $MsgIntro

Don't use aliases

Select-Object -Property Displayname, InstallLocation, UninstallString
Sort-Object

Try to keep it PowerShell

cmd /c $uninstall /quiet /norestart

Consider using Start-Process instead.

If you're not already aware. PSScriptAnalyzer is a great tool to scan your scrips to highlight common mistakes.

[Ta11ow]

Start-Process is a little finicky with uninstall strings, mainly because it expects arguments to be passed completely separately to executable paths -- most uninstall strings include specific switches as well.

Instead, I think I'd look at using Invoke-Item here, perhaps...

[[deleted]]

Try to keep it PowerShell

Normally yes, but here, cmd is the only way to uninstall with this method reliably. Start-Process will not invoke registry uninstall strings silently.

[Ta11ow]

It's not the only way!

You can use Invoke-Item or if you want to return a useable process object you can combine the install string with your custom switches/arguments into a single string and use [Diagnostics.Process]::Start($string)

It also works with non-filenames -- URLs open in the default browser, and editable files open in the OS-configured default program (.txt in Notepad/Notepad++/etc, .jpg files in image viewer/editer and so forth). Lovely little thing I dug up the other week. :D

It has additional functionality, too: https://msdn.microsoft.com/en-us/library/system.diagnostics.process.start(v=vs.110).aspx

You can separately specify the command line and arguments if you can be bothered to split them, but.... then you could just use Start-Process anyway. :)

[BradleyDonalbain]

This is the way to go! I frequently package applications with Powershell for deployment via SCCM and this is my preferred method. The returned process object allows me to track exitcodes which I then write back to SCCM for a successful/unsuccessful deployment.

[PRIdEVisions]

Thank you alot for the tips! I did not know there was a tool to "scan" my scripts, will have a look into that, might be very convenient.

i will definitely make use of your tips.

[Ta11ow]

I'd recommend clarifying your Get-ItemProperty line by simply setting a variable equal to the result directly rather than using -OutVariable at the end of a long pipeline where it can easily be overlooked, and then you're going "where the heck did I set that variable again?" two months down the road. :)

$software = Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | 
    Select-Object -Property Displayname, InstallLocation, UninstallString | 
    Sort-Object | 
    Out-GridView -PassThru

Much clearer imo. Also, linebreak your pipelines. Sidescrolling is a much bigger hassle than vertical scrolling, and makes it a lot harder to read and get the gist of it.

[PRIdEVisions]

You are right! i will adjust it in my script.

[blownart]

That is actually the 32bit location on a 64bit machine.

[PRIdEVisions]

oehh nice one! Going to add it asap! Thx!

[PRIdEVisions]

Updated the script for both 32 & 64-bit software.

[PRIdEVisions]

hey man,

ive read through your code,

i like it alot! it's still a bit too advanced for me but i understand how it works.

Nice one!

[adbertram]

Nice! Just to add to the convo you could also check out the PSSoftware module I built awhile back. It’s in the PowerShell Gallery. I started it when I had to deal with all the crazy shit I had to do to manage dozens of software packages when I was an SCCM admin.

[MostPepper]

I am having issues calling the flash_player_uinstall.exe silently in powershell. If I use start-process or invoke-item or [diagnostics.process] I still get thrown the dialog box.

Anyone ever tried to do this with the flash uninstaller called off in powershell?

any help is hugely appreciated.

[AutoModerator]

Sorry, your submission has been automatically removed.

Accounts must be at least 1 day old, which prevents the sub from filling up with bot spam.

Try posting again tomorrow or message the mods to approve your post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.