Uninstall Black Ice - command line & silent parameters

Comments

20 comments

  • Stephen Valdinger

    Is that GUID the same on all the computers with the older version? Sometimes that GUID changes. That's gonna be a real kick in the nuts if that is the case. Verify that for me quick and I'll go grab my thinking cap out of the shed while I wait.

    0
    Comment actions Permalink
  • Monica KVH

    There are five or six different paths across 37 computers with it installed. I've dealt with the same sort of thing from other applications I've needed to uninstall--but their publishers weren't so stingy with silent parameters!

    0
    Comment actions Permalink
  • Stephen Valdinger

    Do you have the original installer exe handy?

     

    0
    Comment actions Permalink
  • Monica KVH

    Sure do. We have the new msi and the old exe on the network drive, and the users who have the old versions have a setup executable in their C drive.

    0
    Comment actions Permalink
  • Stephen Valdinger

     Any chance I could get my hands on the EXE file?

    0
    Comment actions Permalink
  • Monica KVH

    Unfortunately that's against our security policies (vague, I know, sorry). The Black Ice website might have an executable available for demoing, but I'm not sure if you'd get an executable or an msi from their request form. I feel like I'm in the middle of a rock and hardplace sandwich.

    http://www.blackice.com/DownloadPages/Downloads/Form/TIFF-Monochrome%20printer%20drivers

    0
    Comment actions Permalink
  • Stephen Valdinger

    Totally get it, but I thought I'd ask. can you tell me a version # of the old one? I'll do some digging.

     

    0
    Comment actions Permalink
  • Monica KVH

    Looks like 14.40 is our most recent old exe version.

    0
    Comment actions Permalink
  • Stephen Valdinger

    Yeah I can't get to that version.

    Here's what I was going to try. do you have 7zip installed?

     

    If you do, right click the exe file and extract it to the current directory. 7zip will unbundle it into cab files and what not. Most times they just wrap an exe around an actual msi file. Once you have it.....give it a go with /x from PDQ

    0
    Comment actions Permalink
  • Monica KVH

    No such luck with that, I'm afraid. :( Got a bunch of icons and text files out of the extraction, but no msi.

    0
    Comment actions Permalink
  • Stephen Valdinger

    If you right click on the application in Inventory and select uninstall, does it actually do it? 

    0
    Comment actions Permalink
  • Monica KVH

    It does not. I've been allowing full scans after every attempt since I have a spare department PC to test out uninstall commands on. It's about a 30-36 second turn around time from the time I hit run to the time it returns with a 0, but after the scan Black Ice is still there.

    0
    Comment actions Permalink
  • Stephen Valdinger

    What's your timetable to have this done?  Saturday as in tomorrow? If you can wait until next week I can whip up some code to nuke it from orbit. 

    I'll need some info as far as Installation path(s), any registry key entries, and the output of Get-WMIObject win32_product | Where { $_.Name -Match "TIFF" }

    If I had that I might be able to walk a system and manually remove all the pieces and parts. 

    0
    Comment actions Permalink
  • Monica KVH

    Saturday as in anywhere between two weeks and a month from now.

    You know, I've been neglecting the registry so far but I do have a PowerShell script that I might be able to blow Black Ice away with.

    I'll toy around with it in my test environments on Monday and if I'm still swearing about it then I'll get you more info. I really hope PowerShell can tackle it.

    (P.S. I beat you to mentioning PowerShell. You feeling okay?)

    0
    Comment actions Permalink
  • Stephen Valdinger

    and perhaps the output of Get-WindowsDriver as well. I think it's in Windows 7, and I know it's in Powershell v5, not sure how far back that command goes.

     

    Get-WindowsDriver | Where { $_.ProviderName -match "Black" } should return data. 

    And scroll up missy. I mentioned Get-WmiObject right before you thank you very much.

    0
    Comment actions Permalink
  • Monica KVH

    LOL. My mistake. Normally you lovingly mention PowerShell by name and fly in with a majestic, flowing PowerShell cape. I don't know how the heck I missed that. Long day and reading cmdlets as normal words, I guess? Get-Excuse.

    I made sure as soon as I started here to get all the office PCs equipped with PS5 so no worries there ;)

    I'll see how all of this goes. I told the other admins we should just DBAN everything and start over.

     

    0
    Comment actions Permalink
  • Monica KVH

    Guess how fun this is?
    Black Ice and Monochrome Printer Driver (and all the other names it seems to like to have) are absent from the products and services classes for WMI. Get-WindowsDriver is apparently not recognized by my test environment (Win7, PS5).

    I emailed Black Ice's tech support asking for a silent parameter.
    All I got back was, in essence, "You can't uninstall an executable with an MSI installer. You'll have to uninstall manually with our special uninstaller utility or uninstall it from Programs & Features." *slow clap* Ten pounds of nope in a five-pound bag right there. They're so stingy with silent parameters. Maybe they don't have one.

    Any other suggestions, sir PowerShell guru?

    0
    Comment actions Permalink
  • Stephen Valdinger

    Have you read this?: http://www.blackice.com/private/rtk/Manually_Uninstalling_the_Printer_Drivers.htm

    You *could* roll your own Powershell script that removes all of that crap. You'll have a better understanding of what all that stuff means but it looks like they've laid out exactly what files are where based on what the driver is. 

    Is it a ton of work? You bet your ass it is. I would do it this way:

     

    For all the manual files that you need to remove create a hash table. Call it $DriverFiles. The code would look like this:

     

    $DriverFiles = @{

    Driver filename = File path

    .....

    .....

    }

    Then create an Object from the table

     

    $Object = New-Object PSObject -Property $DriverFiles

     

    You'll then be able to loop the object to remove them all

    Foreach ($o in $object){

    Remove-Item $o.Path -Force (I can't remember if -Confirm is a thing on that cmdlet, if it is throw on a -Confirm:$false)

    }

     

    Do the same thing for the registry entries, then create a section that removes the start menu shortcuts etc as laid out in the support document.

    0
    Comment actions Permalink
  • Monica KVH

    I'll give it a shot. Something tells me my fingers are going to go on strike because their folders are just so full of garbage. ._.

    I decided before your reply to see if it came up in Get-Package, and it did. Unfortunately all I got in the uninstall attempt was an error message *sad trombone*.

    I asked their support -again- for a silent parameter. We'll see if they give me the straight poop this time.

    0
    Comment actions Permalink
  • Monica KVH

    No straight poop from them this time, either.

    After even following their instructions (by which I mean slapping everything into PowerShell)--removing registries and files and whathaveyou--it's still there, staring me in the face, reboot after reboot.

    I guess the good news is the files and registries actually disappear? If nothing else I at least have a cleanup script out of the deal. But man, this is the most stubborn software to remove.

    0
    Comment actions Permalink

Please sign in to leave a comment.