/build/static/layout/Breadcrumb_cap_w.png

Internet Explorer(IE) 11 64 bit Uninstallation.

Hi all,

I have packaged IE11 using IEAK for windows 7 64 bit.
Installation goes fine. But for uninstallation I have created script with below command. And it runs fine when I run manually but fails to revert to old version of IE after uninstallation when I push through SCCM.

cmd /c FORFILES /P %WINDIR%\servicing\Packages /M *11.*.mum /C "cmd /c echo @fname && start /w pkgmgr /up:@fname /quiet /norestart /quiet exit"

cmd /c FORFILES /P %WINDIR%\servicing\Packages /M *11.*.mum /C "cmd /c echo @fname && start /w pkgmgr /up:@fname /quiet /norestart /quiet"

Kindly let the know how to proceed further to uninstallation IE11 on 64 bit machine.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: deepjyotii 9 years ago
Senior Yellow Belt
1
The uninstallation of the application needs to be executed through 64-Bit context which is done manually. But, SCCM executes it in 32-Bit context and as a result of which uninstallation fails. The possible reason for this issue you might have the 32-Bit version of SCCM Client installed (see in Control Panel) and SCCM executes the command lines in 32-Bit context.
Resolution :
Windows Installer allows execution of 32-bit and 64-bit process from/within 32-bit MSI.
You can make use of MSI as a Wrapper to invoke a custom action which will be used to uninstall IE 11.
You can then add
Adding 4096 to the attributes in the custom action table, flags a script CA as a 64 bit version. - See more at: http://www.itninja.com/question/internet-explorer-ie-11-64-bit-uninstallation#sthash.jXSLaqT1.dpuf
Adding 4096 to the attributes in the custom action table, flags a script CA as a 64 bit version. - See more at: http://www.itninja.com/question/internet-explorer-ie-11-64-bit-uninstallation#sthash.jXSLaqT1.dpuf
Adding 4096 to the attributes in the custom action table, flags a script CA as a 64 bit version. - See more at: http://www.itninja.com/question/internet-explorer-ie-11-64-bit-uninstallation#sthash.jXSLaqT1.dpuf
4096 to the attributes in the custom action table, flags this script CA as a 64 bit version. (msidbCustomActionType64BitScript (4096))
You can club the custom action attributes with other processing options like: Asynchronous No Wait which is again a good trick and have many advantages.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ