Article ID: 971204 - Last Review: June 10, 2011 - Revision: 1.1 Windows Vista and Windows Server 2008 service pack installation fails with error 0x80004005
Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows
(http://windows.microsoft.com/en-us/windows/help/end-support-windows-xp-sp2-windows-vista-without-service-packs)
. Source: Microsoft Support RAPID PUBLISHINGRAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION. SymptomWhen you try to install a Windows Vista Service Pack, You may encounter the following error message: Install Windows Service Pack Installation was not successful Unspecified error Error: E_FAIL(0x80004005) When you view the %windir%\Logs\CBS\CBS.log, you will find the following entries: <Date Time>, Info CSI 00000704 Calling generic command executable (sequence 54 (0x00000036)): [20]"C:\Windows\bfsvc.exe" CmdLine: [63]""C:\Windows\bfsvc.exe" C:\Windows\boot /nosystem32boot /nofonts" <Date Time>, Error CSI 00000709 (F) Done with generic command 54 (0x00000036); CreateProcess returned 0, CPAW returned S_OK Process exit code 15299 (0x00003bc3) resulted in success? FALSE Process output: [l:60 [60]"BFSVC: Failed to get system partition! Last Error = 0x3bc3 CauseWhen you install Vista SP2, the Vista SP2 installer must update the system boot files. If third-party disk management tools are used to "clone" disks or partitions, the SP2 installer will be unable to uniquely identify the correct system boot files.
ResolutionTo work around this issue, turn off the computer and physically unplug all drives that are not required for starting Windows. Power up the computer and restart the service pack installation. If the workaround is not successful, the alternative is to perform a clean-install. DISCLAIMERMICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS. Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|
Back to the top
