{"id":893,"date":"2008-11-05T20:06:22","date_gmt":"2008-11-05T20:06:22","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/heaths\/2008\/11\/05\/visual-studio-2008-sp1-may-complain-that-another-patch-is-installed-even-after-removing-it\/"},"modified":"2019-02-17T15:29:56","modified_gmt":"2019-02-17T22:29:56","slug":"visual-studio-2008-sp1-may-complain-that-another-patch-is-installed-even-after-removing-it","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/setup\/visual-studio-2008-sp1-may-complain-that-another-patch-is-installed-even-after-removing-it\/","title":{"rendered":"Visual Studio 2008 SP1 may complain that another patch is installed even after removing it"},"content":{"rendered":"

If Visual Studio 2008 SP1<\/a> prompts you to run the Microsoft Visual Studio Patch removal tool<\/a>, it means that a patch or product is installed that would cause issues when installing VS2008 SP1. The dialog is shown below.<\/p>\n<\/p>\n

\"Microsoft<\/div>\n<\/p>\n

If you run the the patch removal tool and are still seeing this dialog, please follow the workaround below.<\/p>\n

Workaround<\/h3>\n

You will need to search and possible modify your machine\u2019s registry.<\/p>\n

\n

Warning<\/b> If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.<\/p>\n<\/blockquote>\n

You need to search for \u201cE4F34490B4BE97847AB7446D8AB3D908\u201d which is a representation of the patch code for SP1 Beta – ENU. Only if it is found under key locations described below can you remove it.<\/p>\n

    \n
  1. Click Start<\/strong> and then click Run<\/strong>. <\/li>\n
  2. In the Open<\/strong> box, type regedit.exe and click OK<\/strong>. If you are prompted with a User Account Control (UAC) dialog, please authenticate as an administrator or click Continue<\/strong>. <\/li>\n
  3. In the Registry Editor, click on the very top node on the left. <\/li>\n
  4. Click on the Edit<\/strong> menu and then Find<\/strong>. <\/li>\n
  5. Paste \u201cE4F34490B4BE97847AB7446D8AB3D908\u201d (without quotes) into the Find<\/strong> dialog, and click Find Next<\/strong>. <\/li>\n
  6. For each key location it\u2019s found, take note of the path shown in the status bar at the bottom of the Registry Editor window. You may also click on the Favorites<\/strong> menu and click Add to Favorites<\/strong>, then record the full key location. <\/li>\n<\/ol>\n

    If you find this key under \u201cHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18Products\u201d then the patch is still installed for a product. Try running the patch removal tool again and make sure it completes successfully. If you\u2019re prompted for source, please provide that source to continue.<\/p>\n

    If you do not<\/strong> find this key under \u201cHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18Products\u201d then you may delete the other keys where this was found. This may include one or both of the following locations.<\/p>\n