Msizap.exe G Error 2
Contents |
than you would expect. WinDirStat is a great little utility to figure out where that space is going. If you use that program, you might discover that C:\Windows\Installer is really big. Sometimes windows installer folder huge that directory is not as clean as it should be because of various failed program wicleanup installations or unclean uninstalls.Use the Windows Installer Cleanup Utility to safely get rid of the unneeded cruft. Download the installer here. Once
Windows Installer Cleanup Utility
installed, open up a command prompt and type:cd "\Program Files\Windows Installer Clean Up\"msizap G!In one case that I saw, 7 GB was reduced down to about 1.5 GB.I do not recommend using the other utility included with the installer unless told to do so elsewhere. This is the utility that you will see a new entry for in the Programs menu and is not a command line program. Its purpose is not related to the one this post is written about.If you see an error message like:MsiZapInfo: Performing operations for user S-1-5-21-.....Removing orphaned cached files.Error opening 9040110900063D11......\InstallProperties subkey of Products key for S-1-5-18 user. Error: 2.FAILED to clear all data.don't worry about it. The program has finished cleaning up all it can. If you're bothered by it and know your way around the Windows Registry, you'll find the GUID listed somewhere under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData. If you're sure it refers to something you've uninstalled already, go ahead and delete the key, run 'msizap G!' again and you shouldn't see the error message anymore.(Note: I am aware this information is already available online elsewhere in some for or other, but I found it to be somewhat scattered and confusing.) Posted by William Yang at 3:40 PM Reactions: Labels: tech 5 comments: igork806December 26, 2011 at 6:44 AMGreat tip :) My Windows\Installer folder was 50,6 GB, after trying this solution it is 1,63 GB !!!ReplyDeleteDan Dar3June 13, 2012 at 7:18 AMIt's available here now as well.Deleting of Windows Installer Cache (C:\Windows\Installer\) Fileshttp://support.microsoft.com/kb/2667628ReplyDeleteThomas Gail HawsDecember 9, 2012 at 10:26 PMThank you! You *did* explain it better.TomReplyDeleteRADRaze2KXJune 19, 2013 at 1:35 PMWorked like a charm. Reduced 79GB down to 4.9GB. Thank you William Yang!Mark BushOwnerRAD Computerswww.1radpc.comReplyDeleteBikram AgarwalDecember 24, 2013 at 8:38 PMWell, in my case, doesn't look like it did anything. It immediately returned four lines of Error : 2 and Installer folder is still taking up 7.6 GB as before. :(ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Problems removing Orphaned Files using the MSIZAP.exe Want to Advertise Here? Solved Problems removing Orphaned Files using the MSIZAP.exe Posted on 2010-01-12 SSRS MySQL Server MS Server OS 1 Verified Solution 7 Comments 7,705 Views Last Modified: 2012-05-08 Hi there, I am running out of http://wyang0.blogspot.com/2010/06/clean-up-cwindowsinstaller.html space on my C dive. I have Visual Studio 2005 running on my Server, so i have tried to run the MSIZAP.exe command to delete the orphaned files so that this might give me some space. This usually works. however today i am getting the following error. Error opening *****\InstallProperties subkey of Products key for **** user. Error:2 Failed to Clear all data. I don't know why this is happening. Does https://www.experts-exchange.com/questions/25047336/Problems-removing-Orphaned-Files-using-the-MSIZAP-exe.html anyone have any idea's on what i can do here? Kind Regards, Putoch. 0 Question by:Putoch Facebook Twitter LinkedIn Google LVL 19 Active today Best Solution byderoode This can happen when trying to uninstall an application that puts it's install settings and windows installer keys in Hkey_current_user in stead of Hkey_local_machine, and after installing the application Go to Solution 5 Comments LVL 4 Overall: Level 4 Message Expert Comment by:condortek2010-01-13 Check if for defects in your hard drive and then the registry security, try to clear permissions in the registry, we assuming that you are working with the user Administrator, Regards 0 Message Author Comment by:Putoch2010-02-02 This is still a problem for me. i checked for defects but found nothing. 0 LVL 19 Overall: Level 19 MS Server OS 3 MySQL Server 1 SSRS 1 Message Active today Accepted Solution by:deroode2010-02-18 This can happen when trying to uninstall an application that puts it's install settings and windows installer keys in Hkey_current_user in stead of Hkey_local_machine, and after installing the application either the user profile is deleted, or a de-install is tried with a different user. Why are you using msizap instead of regular uninstall? What you can try to do to get some space on your system dr
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph https://msdn.microsoft.com/en-us/library/windows/desktop/aa370523(v=vs.85).aspx Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & http://www.sumnone.com/post/2011/07/16/cleaning-c-windows-installer-safely-without-msizapexedue-to-error-6 platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why windows installer Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows msizap.exe g error IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Windows Installer Reference Released Versions, Tools, and Redistributables Windows Installer Development Tools Windows Installer Development Tools Msizap.exe Msizap.exe Msizap.exe Instmsi.exe Msicert.exe Msidb.exe Msifiler.exe Msiinfo.exe Msimerg.exe Msimsp.exe Msistuff.exe Msitool.mak Msitran.exe Msival2.exe Msizap.exe Orca.exe PATCHWIZ.DLL Wilogutl.exe TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Msizap.exe Msizap.exe is a command line utility that removes either all Windows Installer information for a product or al
Installation Gotcha >> Cleaning C:\Windows\Installer safely without msizap.exe...due to error 6 16. July 2011 08:40 / William / How To Comments (3) Today I found myself cleaning up my C: drive on one of my servers. One of the offending folders was C:\Windows\Installer. Be carefulwhat you delete from this folder as you will run into another headache if you ever find yourself trying to uninstall a program (and possibly other annoyances) and the associated msp file is not there. Microsoft has created a tool called msizap.exe that SHOULDclean this folder upfor you by deleting all the orphaned patches. However, upon running: msizap.exe G! I got the following error: MsiZapInfo: Performing operations for user S-1-5-21-2914546075-379062757-4049983416-500Removing orphaned cached files. Error enumerating Products key for S-1-5-21-2914546075-379062757-4049983416-500 user. Error: 6.FAILED to clear all data. After googling this error, I found no solutions on how to resolve it. So, I found myselfcleaning this folder the hard way,but not as hard as it could have been. If you go here: http://blogs.msdn.com/b/heaths/archive/2007/01/31/how-to-safely-delete-orphaned-patches.aspx Someone from the msdn blog has created a script (wimsps.vbs) toshow you which patches are registered. These are the files you DON'T want to delete. So, I modified the script to move these files to another directory, sothey are out ofmy way while I sift through the other files. There are a couple of things to do before running the script: The first is to create a backup directory for your registered patches. (Otherwise, the script will error that the backup directory isn't there. (I realize I could modify the script to make the directory, but...I won't be using this script often and it's simply faster to create the directory.) The second thing to do is change the bakfolder variable to the proper path of your backup directory thenrun the script. Now you can go through the rest of the C:\Windows\Installer directory and not have to compare it to the script output list of registered patches. Once you are done, simply copy the registered files back to the C:\Windows\Installer directory, delete your backu