Is MSIZAP still useful, or is it obsolete?I deployed Flash Player via a Software Installation policy. How to upgrade?What's a read-only domain controller actually useful for?How is Apache still working?IIS 7 Still Serving old SSL CertificateIs WINs Still supported by Microsoft?Windows Update Group Policy removed but still can't run updatesI deployed Flash Player via a Software Installation policy. How to upgrade?GPO still applying old settingInstall RSClientPrint for Reporting Services 2012 using .bat file and still be able to use 2005OLE error code 0x800704ec: This program is blocked by group policy. Using COM in VFP9New GPO not being applied, still overwritten by existing
What is a Recurrent Neural Network?
Why are the 2nd/3rd singular forms of present of « potere » irregular?
Why is current rating for multicore cable lower than single core with the same cross section?
Help, my Death Star suffers from Kessler syndrome!
Why didn't this hurt this character as badly?
What does YCWCYODFTRFDTY mean?
Why do Ichisongas hate elephants and hippos?
How deep to place a deadman anchor for a slackline?
Pawn Sacrifice Justification
How to verbalise code in Mathematica?
Single Colour Mastermind Problem
Feels like I am getting dragged in office politics
Illegal assignment from SObject to Contact
What's the metal clinking sound at the end of credits in Avengers: Endgame?
Is it possible to measure lightning discharges as Nikola Tesla?
Options leqno, reqno for documentclass or exist another option?
How to back up a running remote server?
How to replace the "space symbol" (squat-u) in listings?
Past Perfect Tense
Can fracking help reduce CO2?
gnu parallel how to use with ffmpeg
Why the difference in metal between 銀行 and お金?
Why do computer-science majors learn calculus?
Does jamais mean always or never in this context?
Is MSIZAP still useful, or is it obsolete?
I deployed Flash Player via a Software Installation policy. How to upgrade?What's a read-only domain controller actually useful for?How is Apache still working?IIS 7 Still Serving old SSL CertificateIs WINs Still supported by Microsoft?Windows Update Group Policy removed but still can't run updatesI deployed Flash Player via a Software Installation policy. How to upgrade?GPO still applying old settingInstall RSClientPrint for Reporting Services 2012 using .bat file and still be able to use 2005OLE error code 0x800704ec: This program is blocked by group policy. Using COM in VFP9New GPO not being applied, still overwritten by existing
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I update flash using MSI files installed by group policy. However, with every update, about a third of the workstations fail to update (Windows Vista and Windows 7 32/64-bit editions). In the event logs, this message appears:
"Adobe Flash Player 11 ActiveX -- Error 1714.The older version of
Adobe Flash Player 11 ActiveX cannot be removed. Contact your
technical support group. System Error 1612."
The only way I've been able to address the issue is to use the Microsoft Fit It tool. However, it's a very time consuming process, which takes about 15 minutes to mannually perform for each workstation, so it effectively kills a whole day every time a flash update comes out.
I came across this script which includes MSIZAP to remove failed uninstallations of flash. So, my question is: is the MSIZAP utility the best approach for removing flash programmatically, or is it obsolete at this point? The reason I ask is that most of the written materials that I've found on the subject are from 2009 or 2010.
@echo off
SET MSIZAP=\my.domain.comnetlogonbinmsizap.exe
SET DFSPATH=\my.domain.comdfsrootPackagesAdobe
SET UNINSTALL=%DFSPATH%uninstall_flash_player_x86.exe
SET INSTALL=%DFSPATH%install_flash_player_11.4.402.278_active_x.exe
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE
SET VER_FLAG_KEY=HKEY_LOCAL_MACHINESOFTWARE%WOW6432NODE%MacromediaFlashPlayer
SET VER_FLAG_VALUE=11,4,402,278
REG QUERY "%VER_FLAG_KEY%" /v CurrentVersion | find /i "%VER_FLAG_VALUE%" > NUL 2>NUL
if errorlevel 1 goto do_install
goto :EOF
:do_install
rem Uninstall all old versions of Flash.
start /wait /min "" "%UNINSTALL%" -uninstall activex
rem MSIZAP all old versions
start /wait /min "" "%MSIZAP%" TW! 2BD2FA21-B51D-4F01-94A7-AC16737B2163
start /wait /min "" "%MSIZAP%" TW! B7B3E9B3-FB14-4927-894B-E9124509AF5A
start /wait /min "" "%MSIZAP%" TW! FA1D6742-0515-4A94-AD5D-F0484026E4A2
rem Run new installer
start /wait /min "" "%INSTALL%" -install activex
rem Block future automatic updates
SET DEST="%windir%system32MacromedFlashmms.cfg"
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET DEST="%windir%SysWOW64MacromedFlashmms.cfg"
rem I'm using "sort" here because the redirect is being interpreted as "1>" and
rem doing "1 >" causes a space to be stored in the file, which "breaks" the file.
echo AutoUpdateDisable=1|sort>%DEST%
Source: I deployed Flash Player via a Software Installation policy. How to upgrade?
windows-server-2008 group-policy batch-file uninstall
add a comment |
I update flash using MSI files installed by group policy. However, with every update, about a third of the workstations fail to update (Windows Vista and Windows 7 32/64-bit editions). In the event logs, this message appears:
"Adobe Flash Player 11 ActiveX -- Error 1714.The older version of
Adobe Flash Player 11 ActiveX cannot be removed. Contact your
technical support group. System Error 1612."
The only way I've been able to address the issue is to use the Microsoft Fit It tool. However, it's a very time consuming process, which takes about 15 minutes to mannually perform for each workstation, so it effectively kills a whole day every time a flash update comes out.
I came across this script which includes MSIZAP to remove failed uninstallations of flash. So, my question is: is the MSIZAP utility the best approach for removing flash programmatically, or is it obsolete at this point? The reason I ask is that most of the written materials that I've found on the subject are from 2009 or 2010.
@echo off
SET MSIZAP=\my.domain.comnetlogonbinmsizap.exe
SET DFSPATH=\my.domain.comdfsrootPackagesAdobe
SET UNINSTALL=%DFSPATH%uninstall_flash_player_x86.exe
SET INSTALL=%DFSPATH%install_flash_player_11.4.402.278_active_x.exe
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE
SET VER_FLAG_KEY=HKEY_LOCAL_MACHINESOFTWARE%WOW6432NODE%MacromediaFlashPlayer
SET VER_FLAG_VALUE=11,4,402,278
REG QUERY "%VER_FLAG_KEY%" /v CurrentVersion | find /i "%VER_FLAG_VALUE%" > NUL 2>NUL
if errorlevel 1 goto do_install
goto :EOF
:do_install
rem Uninstall all old versions of Flash.
start /wait /min "" "%UNINSTALL%" -uninstall activex
rem MSIZAP all old versions
start /wait /min "" "%MSIZAP%" TW! 2BD2FA21-B51D-4F01-94A7-AC16737B2163
start /wait /min "" "%MSIZAP%" TW! B7B3E9B3-FB14-4927-894B-E9124509AF5A
start /wait /min "" "%MSIZAP%" TW! FA1D6742-0515-4A94-AD5D-F0484026E4A2
rem Run new installer
start /wait /min "" "%INSTALL%" -install activex
rem Block future automatic updates
SET DEST="%windir%system32MacromedFlashmms.cfg"
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET DEST="%windir%SysWOW64MacromedFlashmms.cfg"
rem I'm using "sort" here because the redirect is being interpreted as "1>" and
rem doing "1 >" causes a space to be stored in the file, which "breaks" the file.
echo AutoUpdateDisable=1|sort>%DEST%
Source: I deployed Flash Player via a Software Installation policy. How to upgrade?
windows-server-2008 group-policy batch-file uninstall
If you have a list GUIDs why not just walk them and uninstall? Something like:msiexec /x the-product-guid /qn-- That should uninstall the product[s]. I don't think MsiZap is supported.
– jscott
Feb 28 '13 at 15:54
1
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10
add a comment |
I update flash using MSI files installed by group policy. However, with every update, about a third of the workstations fail to update (Windows Vista and Windows 7 32/64-bit editions). In the event logs, this message appears:
"Adobe Flash Player 11 ActiveX -- Error 1714.The older version of
Adobe Flash Player 11 ActiveX cannot be removed. Contact your
technical support group. System Error 1612."
The only way I've been able to address the issue is to use the Microsoft Fit It tool. However, it's a very time consuming process, which takes about 15 minutes to mannually perform for each workstation, so it effectively kills a whole day every time a flash update comes out.
I came across this script which includes MSIZAP to remove failed uninstallations of flash. So, my question is: is the MSIZAP utility the best approach for removing flash programmatically, or is it obsolete at this point? The reason I ask is that most of the written materials that I've found on the subject are from 2009 or 2010.
@echo off
SET MSIZAP=\my.domain.comnetlogonbinmsizap.exe
SET DFSPATH=\my.domain.comdfsrootPackagesAdobe
SET UNINSTALL=%DFSPATH%uninstall_flash_player_x86.exe
SET INSTALL=%DFSPATH%install_flash_player_11.4.402.278_active_x.exe
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE
SET VER_FLAG_KEY=HKEY_LOCAL_MACHINESOFTWARE%WOW6432NODE%MacromediaFlashPlayer
SET VER_FLAG_VALUE=11,4,402,278
REG QUERY "%VER_FLAG_KEY%" /v CurrentVersion | find /i "%VER_FLAG_VALUE%" > NUL 2>NUL
if errorlevel 1 goto do_install
goto :EOF
:do_install
rem Uninstall all old versions of Flash.
start /wait /min "" "%UNINSTALL%" -uninstall activex
rem MSIZAP all old versions
start /wait /min "" "%MSIZAP%" TW! 2BD2FA21-B51D-4F01-94A7-AC16737B2163
start /wait /min "" "%MSIZAP%" TW! B7B3E9B3-FB14-4927-894B-E9124509AF5A
start /wait /min "" "%MSIZAP%" TW! FA1D6742-0515-4A94-AD5D-F0484026E4A2
rem Run new installer
start /wait /min "" "%INSTALL%" -install activex
rem Block future automatic updates
SET DEST="%windir%system32MacromedFlashmms.cfg"
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET DEST="%windir%SysWOW64MacromedFlashmms.cfg"
rem I'm using "sort" here because the redirect is being interpreted as "1>" and
rem doing "1 >" causes a space to be stored in the file, which "breaks" the file.
echo AutoUpdateDisable=1|sort>%DEST%
Source: I deployed Flash Player via a Software Installation policy. How to upgrade?
windows-server-2008 group-policy batch-file uninstall
I update flash using MSI files installed by group policy. However, with every update, about a third of the workstations fail to update (Windows Vista and Windows 7 32/64-bit editions). In the event logs, this message appears:
"Adobe Flash Player 11 ActiveX -- Error 1714.The older version of
Adobe Flash Player 11 ActiveX cannot be removed. Contact your
technical support group. System Error 1612."
The only way I've been able to address the issue is to use the Microsoft Fit It tool. However, it's a very time consuming process, which takes about 15 minutes to mannually perform for each workstation, so it effectively kills a whole day every time a flash update comes out.
I came across this script which includes MSIZAP to remove failed uninstallations of flash. So, my question is: is the MSIZAP utility the best approach for removing flash programmatically, or is it obsolete at this point? The reason I ask is that most of the written materials that I've found on the subject are from 2009 or 2010.
@echo off
SET MSIZAP=\my.domain.comnetlogonbinmsizap.exe
SET DFSPATH=\my.domain.comdfsrootPackagesAdobe
SET UNINSTALL=%DFSPATH%uninstall_flash_player_x86.exe
SET INSTALL=%DFSPATH%install_flash_player_11.4.402.278_active_x.exe
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE
SET VER_FLAG_KEY=HKEY_LOCAL_MACHINESOFTWARE%WOW6432NODE%MacromediaFlashPlayer
SET VER_FLAG_VALUE=11,4,402,278
REG QUERY "%VER_FLAG_KEY%" /v CurrentVersion | find /i "%VER_FLAG_VALUE%" > NUL 2>NUL
if errorlevel 1 goto do_install
goto :EOF
:do_install
rem Uninstall all old versions of Flash.
start /wait /min "" "%UNINSTALL%" -uninstall activex
rem MSIZAP all old versions
start /wait /min "" "%MSIZAP%" TW! 2BD2FA21-B51D-4F01-94A7-AC16737B2163
start /wait /min "" "%MSIZAP%" TW! B7B3E9B3-FB14-4927-894B-E9124509AF5A
start /wait /min "" "%MSIZAP%" TW! FA1D6742-0515-4A94-AD5D-F0484026E4A2
rem Run new installer
start /wait /min "" "%INSTALL%" -install activex
rem Block future automatic updates
SET DEST="%windir%system32MacromedFlashmms.cfg"
rem Detect 64-bit Windows
IF NOT "%ProgramFiles(x86)%"=="" SET DEST="%windir%SysWOW64MacromedFlashmms.cfg"
rem I'm using "sort" here because the redirect is being interpreted as "1>" and
rem doing "1 >" causes a space to be stored in the file, which "breaks" the file.
echo AutoUpdateDisable=1|sort>%DEST%
Source: I deployed Flash Player via a Software Installation policy. How to upgrade?
windows-server-2008 group-policy batch-file uninstall
windows-server-2008 group-policy batch-file uninstall
edited Apr 13 '17 at 12:14
Community♦
1
1
asked Feb 28 '13 at 15:20
Force FlowForce Flow
66242044
66242044
If you have a list GUIDs why not just walk them and uninstall? Something like:msiexec /x the-product-guid /qn-- That should uninstall the product[s]. I don't think MsiZap is supported.
– jscott
Feb 28 '13 at 15:54
1
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10
add a comment |
If you have a list GUIDs why not just walk them and uninstall? Something like:msiexec /x the-product-guid /qn-- That should uninstall the product[s]. I don't think MsiZap is supported.
– jscott
Feb 28 '13 at 15:54
1
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10
If you have a list GUIDs why not just walk them and uninstall? Something like:
msiexec /x the-product-guid /qn -- That should uninstall the product[s]. I don't think MsiZap is supported.– jscott
Feb 28 '13 at 15:54
If you have a list GUIDs why not just walk them and uninstall? Something like:
msiexec /x the-product-guid /qn -- That should uninstall the product[s]. I don't think MsiZap is supported.– jscott
Feb 28 '13 at 15:54
1
1
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10
add a comment |
1 Answer
1
active
oldest
votes
Are you trying to install the new version over the old, and rely on its installer do the removal? Or do you tell the windows installer to first uninstall the old, before installing the new?
If you do the former, I recommend you switch to the later, because I had almost only good experience with this. The only exception was when Adobe once put a wrong version number into the uninstall command inside the msi (but that was 100% reproducable, and thus immediately visible on a test machine before the deployment).
See https://serverfault.com/a/441131/144344 and https://serverfault.com/a/564881/144344
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f483437%2fis-msizap-still-useful-or-is-it-obsolete%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Are you trying to install the new version over the old, and rely on its installer do the removal? Or do you tell the windows installer to first uninstall the old, before installing the new?
If you do the former, I recommend you switch to the later, because I had almost only good experience with this. The only exception was when Adobe once put a wrong version number into the uninstall command inside the msi (but that was 100% reproducable, and thus immediately visible on a test machine before the deployment).
See https://serverfault.com/a/441131/144344 and https://serverfault.com/a/564881/144344
add a comment |
Are you trying to install the new version over the old, and rely on its installer do the removal? Or do you tell the windows installer to first uninstall the old, before installing the new?
If you do the former, I recommend you switch to the later, because I had almost only good experience with this. The only exception was when Adobe once put a wrong version number into the uninstall command inside the msi (but that was 100% reproducable, and thus immediately visible on a test machine before the deployment).
See https://serverfault.com/a/441131/144344 and https://serverfault.com/a/564881/144344
add a comment |
Are you trying to install the new version over the old, and rely on its installer do the removal? Or do you tell the windows installer to first uninstall the old, before installing the new?
If you do the former, I recommend you switch to the later, because I had almost only good experience with this. The only exception was when Adobe once put a wrong version number into the uninstall command inside the msi (but that was 100% reproducable, and thus immediately visible on a test machine before the deployment).
See https://serverfault.com/a/441131/144344 and https://serverfault.com/a/564881/144344
Are you trying to install the new version over the old, and rely on its installer do the removal? Or do you tell the windows installer to first uninstall the old, before installing the new?
If you do the former, I recommend you switch to the later, because I had almost only good experience with this. The only exception was when Adobe once put a wrong version number into the uninstall command inside the msi (but that was 100% reproducable, and thus immediately visible on a test machine before the deployment).
See https://serverfault.com/a/441131/144344 and https://serverfault.com/a/564881/144344
edited Apr 13 '17 at 12:14
Community♦
1
1
answered Sep 17 '15 at 21:43
Klaus HartneggKlaus Hartnegg
1736
1736
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f483437%2fis-msizap-still-useful-or-is-it-obsolete%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you have a list GUIDs why not just walk them and uninstall? Something like:
msiexec /x the-product-guid /qn-- That should uninstall the product[s]. I don't think MsiZap is supported.– jscott
Feb 28 '13 at 15:54
1
Keep in mind that these programs failed to be fully uninstalled through group policy, and can't be reinstalled or upgraded until cleaned out with the fix it tool. As far as I was aware, msiexec only works when things are actually functioning properly.
– Force Flow
Feb 28 '13 at 16:14
Are you repackaging the Flash installer with an MSI, or using one they've provided? MSI hasn't changed significantly in several years, so the underlying mechanics haven't really changed. That said, zapping in the first place is a brute force mechanic that may have led to future failures. The Fix It is fundamentally automatable if you're facile with PowerShell, though I wouldn't officially recommend it. (I work for Microsoft, so I won't recommend it - I'm just saying the guts are PowerShell and theoretically it could be done.)
– Matthew Wetmore
Mar 16 '17 at 4:10