{"id":37573,"date":"2004-10-14T07:00:00","date_gmt":"2004-10-14T07:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2004\/10\/14\/the-procedure-entry-point-shcreatethreadref-could-not-be-located\/"},"modified":"2004-10-14T07:00:00","modified_gmt":"2004-10-14T07:00:00","slug":"the-procedure-entry-point-shcreatethreadref-could-not-be-located","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20041014-00\/?p=37573","title":{"rendered":"The procedure entry point SHCreateThreadRef could not be located…"},"content":{"rendered":"

\nSome people smarter than me have been working on this problem, and\nhere’s what they figured out. First, I’ll just reprint their\nanalysis (so that people with the problem and are searching for\nthe solution can find it), and then we can discuss it.\n<\/P>\n

\nUpdate (18 October 2005):\n\nThe official version of this document is now available<\/A><\/STRONG>.\nPlease use that version instead of following the steps below, which\nwere based on a preliminary version of the instructions.\n<\/P>\n

\n\n

\nIf you receive an error message: “Explorer.EXE – Entry Point Not Found –\nThe procedure entry point SHCreateThreadRef could not be located in the \ndynamic link library SHLWAPI.dll”,\nthis information will help resolve the issue. \n<\/P>\n

\nThis appears to have been caused by the following sequence of events:\n<\/P>\n

    \n
  1. \nYou installed Windows XP Service Pack 2\n
  2. \nThe installation of Service Pack 2 failed due to a computer crash\nduring the installation which resulted in the automatic\nService Pack Recovery process.\nOn next boot, you should have received an error message telling you\nthat the install failed, and that you need to go to the control panel\nand uninstall SP2 and then try re-installing it.\nThis message may have been dismissed accidentally\nor by another individual using your computer.\nIn any event, the Service Pack recovery process was not completed\nby uninstalling the service pack from the Add\/Remove Programs control panel,\nand the system is consequently\nin a partially installed state which is not stable. \n
  3. \nYou then installed the latest security update for Windows XP,\nMS04-038, KB834707.\nBecause your system is still partially SP2,\nthe SP2 version of this fix was downloaded\nand installed by Windows Update or Automatic Updates.\nHowever, the operating system files on the system\nare the original versions due to the SP Recovery process.\nThis results in mismatched files causing this error.\n<\/OL>\n

    \nTo recover the system, carefully perform the following steps:\n<\/P>\n

      \n
    1. \nBoot normally and attempt to log in to your desktop.\nAt this point you should get the error message listed above.\n
    2. \nPress Control+Alt+Delete at the same time to start the Task Manager.\n(If you are using classic logon, click the “Task Manager” button.)\nYou may get additional error messages but Task Manager will eventually start. \n
    3. \nOn the menu bar, select File and then New Task (Run).\n
    4. \nType in\ncontrol appwiz.cpl<\/CODE>\ninto the new task box and hit OK.\nYou may get additional errors that can be ignored. \n
    5. \nThe Add\/Remove Control Panel should now be running.\nYou can close Task Manager.\n
    6. \nNear the bottom of the list,\nfind the entry titled “Windows XP Hotfix – KB834707”.\n
    7. \nClick on it and click the “Remove” button.\nIt will take some time to complete.\nOnce the “Finish” button is visible, click on it and reboot your system.\nIf you get messages about additional software or hotfixes installed,\nyou can safely ignore them. \n<\/OL>\n

      \nDo NOT stop now!\nYour system is still in the “failed SP2 install” state.\nYou MUST complete the SP2 uninstall, and then re-install SP2.\n<\/P>\n

        \n
      1. \nStart the system and log in.\n
      2. \nClick on Start and then Control Panel. \n
      3. \nClick on the Add\/Remove programs item.\n
      4. \nNear the bottom of the list,\nfind the entry titled “Windows XP Service Pack 2”. \n
      5. \nClick on it and remove Service Pack 2.\nYou may get a warning about software you have installed after SP2.\nMake a note of it as you may need to reinstall some of them\nafter the uninstall operation. \n
      6. \nAfter Service Pack 2 has been successfully removed,\nyou should visit\n\nhttp:\/\/www.microsoft.com\/sp2install<\/A>\nfor instructions on installing Service Pack 2.\nYou can get SP2 from\n\nhttp:\/\/windowsupdate.microsoft.com<\/A>.\n
      7. \nAfter Service Pack 2 has been successfully re-installed,\nyou should re-visit Windows Update to get\nthe proper version of the latest critical security updates.\n<\/OL>\n

        \nFAQ:\n<\/P>\n

        \nQ: I don’t believe I am in the “partially installed SP2” state.\nIs there any way to check that?\n<\/P>\n

        \nA: After step 7, your system should be able to log in.\nThere are several ways to check.\n<\/P>\n

          \n
        1. \nOpen the file c:\\windows\\svcpack.log,\nand scroll to the very bottom of the file.\nAbout 10 lines from the end, you should see:\n
          \n0.xxx: Executing script \\SystemRoot\\sprecovr.txt\n0.xxx: In cleanup mode. System will not be rebooted.\n<\/PRE>\nIf you have these lines in svcpack.log,\nand you did not uninstall Service Pack 2 in Add\/Remove Programs,\nyou definitely have a machine in this partially installed state. \n
        2. \nClick on the Start button, then Run, and type\nwinver<\/CODE>,\nthen click OK.\nIf the version is\n“Version 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158: Service Pack 2”\nthen you have the correct SP2 install.\nIf, however, it has a number that is less than 040803 after the xpsp2,\nsuch as “Build 2600.xpsp2.030422-1633 : Service Pack 2”\nthen you definitely have a machine in the partially installed state.\n[Corrected typo in version numbering, 11am.]\n<\/OL>\n<\/STRIKE>\n<\/BLOCKQUOTE>\n
          \nNotice that\n\nthe default answer to every dialog box is “Cancel”<\/A>.\nThe Service Pack setup program detected a problem and gave instructions\non how to fix it, and yet people just ignored the message.\n<\/P>\n
          \nThe result of not fixing the problem is that you are left with a machine that\nis neither Service Pack 1 nor Service Pack 2 but instead\nis a Frankenstein monster of some files from Service Pack 1 and\nsome files from Service Pack 2.\nThis is hardly a good situation.\nHalf the files are mismatched with the other half.\n<\/P>\n
          \nThere was enough of Service Pack 2 on your machine that\nWindows Update downloaded the Service Pack 2 version of the\nsecurity patch and tried to install it.  This made a bad situation worse.\n<\/P>\n
          \nWhat’s the moral of the story?\n<\/P>\n
          \nFirst, that users ignore all error messages.\nEven error messages that tell how to fix the error!\nSecond, that ignoring some error messages often leads to worse error messages.\nAnd third, that once you get into this situation, you’re off in\nuncharted territory.  And there are only dragons there.\n<\/P>\n
          \n(These are the types of problems that are nearly impossible to\ndebug:  It will never happen in the test lab, because the test lab\npeople know that when an error message tells you, “The install failed;\nyou need to do XYZ to fix it,” you should do it!  All you can work\nfrom are descriptions from people who are having the problem, and\na lot of creativity to try to guess “What happened that they aren’t\ntelling me?”)\n<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"
          Some people smarter than me have been working on this problem, and here’s what they figured out. First, I’ll just reprint their analysis (so that people with the problem and are searching for the solution can find it), and then we can discuss it. Update (18 October 2005): The official version of this document is […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[104],"class_list":["post-37573","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-tipssupport"],"acf":[],"blog_post_summary":"
          Some people smarter than me have been working on this problem, and here’s what they figured out. First, I’ll just reprint their analysis (so that people with the problem and are searching for the solution can find it), and then we can discuss it. Update (18 October 2005): The official version of this document is […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/37573","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=37573"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/37573\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=37573"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=37573"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=37573"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}