Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event logged reporting storflt driver failed to load on restart after you install Windows Server 2008 SP2


View products that this article applies to.

Source: Microsoft Support

↑ Back to the top


Rapid publishing

RAPID 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.

↑ Back to the top


Symptom



After you install the Service Pack 2 update on a physical computer that is running Windows Server 2008 and rebooting, the following event appears in the System log:



Log Name:����� System

Source:������� Service Control Manager

Event ID:����� 7026

Level:�������� Error

Description: The following boot-start or system-start driver(s) failed to load: storflt



Note: This problem is only seen on physical systems that are running Windows Server 2008. It does not affect Hyper-V virtual machines running Windows Server 2008.

↑ Back to the top


Cause



The problem results from changes between the Hyper-V driver manifests installed by SP2 and the corresponding version in release version of Windows.

↑ Back to the top


Resolution



This event can be safely ignored. The storflt driver is only needed when Windows Server 2008 is running as Hyper-V guest. To prevent this error from being logged every time that the system restarts, perform the following steps to delete the references to the storflt driver. :



1.���� Open an elevated command prompt

a.���� Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

2.���� Delete the storflt driver

a.���� sc delete storflt



Note: Do not this on a Hyper-V virtual machine. On restart the virtual machine will most likely generate a Stop Error 0x0000007b. If you encounter this problem, booting to Last Known Good may be able to restore the registry to the previous state.

↑ Back to the top


Disclaimer

MICROSOFT 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.

↑ Back to the top


Keywords: KB971527, kbnomt, kbrapidpub

↑ Back to the top

Article Info
Article ID : 971527
Revision : 1
Created on : 5/19/2009
Published on : 5/19/2009
Exists online : False
Views : 373