Error Opening Subkey Products Key
Contents |
than you would expect. WinDirStat is a great little utility to figure out where that space
Windows Installer Folder Huge
is going. If you use that program, you might discover that C:\Windows\Installer wicleanup is really big. Sometimes that directory is not as clean as it should be because of various msizap failed program installations or unclean uninstalls.Use the Windows Installer Cleanup Utility to safely get rid of the unneeded cruft. Download the installer here. Once installed, open up a
Windows Installer Cleanup Utility
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 D
& Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual C++ Visual F# JavaScript TypeScript Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and http://wyang0.blogspot.com/2010/06/clean-up-cwindowsinstaller.html Visual Studio. How to Safely Delete Orphaned Patches ★★★★★★★★★★★★★★★ February 1, 2007 by Heath Stewart (MSFT) // 21 Comments 0 0 0 If Visual Studio 2005 Service Pack 1 fails to install, you might find additional .msp files under %WINDIR%\Installer for each failed attempt. You should not simply delete these patches, however, because if one of the patches https://blogs.msdn.microsoft.com/heaths/2007/02/01/how-to-safely-delete-orphaned-patches/ was applied successfully to one target product, deleting that patch will cause future maintenance installs – including repairs, patch install, patch uninstall, and even product uninstall – to fail. After safely identifying orphaned patches, you can delete them. There are a couple of different ways to identify orphaned patches. If you have the Windows SDK or the older Platform SDK installed or are willing to install either, you can use msizap.exe to identify and remove orphaned data files such as patches. Run the following command. You will find msizap.exe in the bin folder of the Windows SDK or Platform SDK installation directory. msizap.exe G! If you don't want to install either SDK just to get this executable, you can determine which patches are registered and applicable and delete extra patches you find under %WINDIR%\Installer. I have attached a simple script to identify which patches are registered – those patches you should not remove. To successfully install the patch if you are having problems, please read about known issues with Vis
we highly recommend that you visit our Guide for New Members. HUGE Windows folder (22.2 GB) Help please!! Discussion in 'Windows XP' started by selenityaria, Apr 15, 2008. Thread Status: Not open for https://forums.techguy.org/threads/huge-windows-folder-22-2-gb-help-please.703897/page-2 further replies. Page 2 of 2 < Prev 1 2 Advertisement Elvandil Joined: Aug 1, 2003 http://ctrlf5.net/?p=152 Messages: 51,988 The cleanup utility does not remove files. Description of the Windows Installer CleanUp Utility Elvandil, Apr 17, 2008 #16 Hughv Joined: Jul 22, 2006 Messages: 8,450 Elvandil said: ↑ The cleanup utility does not remove files. Description of the Windows Installer CleanUp UtilityClick to expand... Then why does it say: "To do this, select the programs that you windows installer want in the Installed Products list in the Windows Installer CleanUp dialog box. After you make this selection, the utility removes only the Windows Installer configuration information that is related to those programs. Removes the files and registry settings that make up the Windows Installer configuration information for programs that you select ". Hughv, Apr 17, 2008 #17 Elvandil Joined: Aug 1, 2003 Messages: 51,988 The cleanup utility is designed to remove primarily registry error opening subkey information for failed installations or ones that did not complete. Removing those things from installed programs will cause them to pop a window requesting a reinstallation the next time they are run. The few files removed, if any, will make little difference to disk usage. Elvandil, Apr 17, 2008 #18 selenityaria Thread Starter Joined: Apr 15, 2008 Messages: 9 BIGGER PROBLEM NOW!! I was trying to reply to email in Outlook and I got an error message: "Microsoft Word is set to by your e-mail editor. However, Word is unavailable, not installed, or is not the same version as Outlook. The Outlook e-mail editor will be used instead. The program for the attachment may not have been installed properly or may have been moved or deleted. Reinstall the program in which the attachment was created." Then I tried opening a saved Word document, and Word will not open. No error message though. I tried restoring the files in my Recycle Bin, but that has not worked. 95% of all my docs were made with Word. OMG, what do I do?!?! selenityaria, Apr 17, 2008 #19 Elvandil Joined: Aug 1, 2003 Messages: 51,988 You'll need to reinstall Word to restore the missing Windows installer files and/or registry entries. Elvandil, Apr 17, 2008 #20 padutch Joined: Sep 1, 2001 Messages: 1,297 try a system restore padut
a "Unable to open sub key" or "Error 1402.Could not open key:" or "Error 1402.Could not open key: UNKNOWN\Components\XXXXXXXXXXXXXXXXXXXXXXXX" etc. Most of these errors are because you have already installed this product and un-installation or upgrade of the product did not complete properly. Hence there are some registry keys left with bad ACL's in the registry. The work around I mention here is for OS's Windows XP Sp2 and above. Meaning, you are seeing this problem either in Windows XP or Windows Vista or Windows 7. Open "RegEdit" and browse to the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components Right Click on Components select permissions Click Advanced Select the "Owner" Tab Select Administrators (Group) as owner and Click Apply. Then Select Checkbox that says "Replace owner on sub containers and objects" and Click apply. Browse back to the Permissions tab, select the Check box that says "Replace all child objects with inheritable permissions from this object" and Click apply You should see couple of Warnings similar to below image, but those are fine. Its just complaining about some restricted windows components. Hope this helps some one Tags: Microsoft, MSI, Technology, Windows 192 Responses to How to resolve “Unable to open Sub key” Error when installing an MSI package? Josh Romero February 6th, 2010 at 9:21 pm Thanks! Helped alot and was very simple to follow! lai February 7th, 2010 at 2:49 pm thanks for the tutorial! it was exactly what i needed! Albert Wydeen March 28th, 2010 at 10:53 pm Thanks a million, you are a life saver. I tried several times to get my SDK to install but ran into registery problems. Your solution worked like a charm David Tee April 7th, 2010 at 6:39 am Thanks so much for those instructions. I kept having trouble installing microsoft office 2010 Beta. I looked all over the internet for my kind of trouble. Come here and it worked like a charm. mbm April 11th, 2010 at 4:42 pm You saved me. Ralph Rainwater April 16th, 2010 at 7:28 am I add my thanks to you for your very simple, very effective instructions. Microbit April 18th, 2010 at 1:46 pm Finally, a solution that worked! Bless you. ashley April 20th, 2010 at 3:51 am omg mate i cannot believe it. I was pulling my hair out solving this problem then came accross your solution and it worked a trick. You wouldnt believe how thankful I am to you for this. Your a legend and a life saver!! I had problems with the registry when trying to install cs4 photoshop. even the clean cs4 did not work amongst other crap tutoria