Windows 2003 driver load sequence

The following is the registry key for this database:. If the LKG configuration is already being used, the boot fails. Please refer to the following link: Automatically Starting Services. Please also check the following link:. Troubleshooting the Startup Process. Best Regards,. Forum Support. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft.

Good afternoon Dave. Thanks for your reply. In fact I look for some official documentation from Microsoft that lists the boot order of Windows services. I read an article which says that you can delay the startup of a service. I need that type of document. I searched the Internet and not found. Any update on this issue? If there is anything that I can do for you, please feel free to let me know. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. However, be aware that a driver in the device stack cannot depend on being loaded sequentially after a device's lower drivers, because the driver might are loaded previously when another device was configured.

Filter drivers in a filter group cannot predict their load ordering. For example, if a device has three registered upper-filter drivers, those three drivers will all be loaded after the function driver but could be loaded in any order within their upper-filter group.

A driver for a child device can depend on the drivers for the parent device being loaded before the child drivers are loaded.

These drivers are in memory when the kernel gets control. Boot-start drivers are loaded before most of the devices are configured, so their load order cannot be determined by device hierarchy. The operating system ignores INF Dependencies entries for boot-start drivers.

If a boot device has child devices, those devices are enumerated. The child devices are configured and started if their drivers are also boot-start drivers. If a device's drivers are not all boot-start drivers, the PnP manager creates a device node devnode for the device but does not start the device yet.

After all the boot drivers have loaded and the boot devices are started, the PnP manager configures the rest of the PnP devices and loads their drivers. The PnP manager walks the device tree and loads the drivers for the devnodes that are not yet started that is, any nonstarted devnodes from the previous step. As each device starts, the PnP manager enumerates the children of the device, if any.

The load ordering is based on the physical device hierarchy. At the end of this step, all the devices are configured, except devices that are not PnP-enumerable and the descendants of those devices. A Select Adapter dialog appears listing the available drivers. In the Select Adapter dialog, select the appropriate mass storage controller driver version Windows bit or bit that you are installing, then press Enter. For example, for the X which contains an Intel-based integrated disk controller, select:.

A dialog similar to the following appears stating that the setup will load support for the specified mass storage device. The Windows setup process continues and a Setup Notification dialog appears.

At the Setup Notification dialog, press Enter to continue. At the Welcome to Setup dialog, press Enter to continue. The Windows Licensing Agreement dialog appears. To accept the license agreement, press F8. A dialog appears that shows the existing partitions on the server and the unpartitioned space. To delete the existing partition, press D.

A confirmation dialog appears to verify that you really want to delete the partition. A confirmation dialog with a caution notice appears and describes the partition that you are about to delete. To create a partition in the unpartitioned space, press C. A dialog appears that allows you to specify the size of the new partition. Either accept the default size of the partition to be created or use the Back Space key to delete the size specified and enter a new size and press Enter.

A recommended size of 40, megabytes is usually sufficient for a Windows installation. This will leave adequate space on the disk for installations of other media. The setup process formats the partition and copies the files to the Windows installation folders. This process might take several minutes.

Follow the on-screen instructions to complete the initial setup of Windows Server until you are prompted with the following message:. Remove disks or other media.

Press any key to restart. When this message appears you will need to complete one of the following steps, depending on which driver delivery method you have chosen, to complete the installation:.

Then, press any key to restart the system and complete the Windows Server Installation. Proceed to Post Installation.

This section explains the initial information you will need to install the Windows Server operating system software over an established PXE-based network via a customer-provided Windows Remote Installation Services RIS image. The following requirements must be met prior to performing the Windows Server installation from a RIS image. Press F8 to specify a temporary boot device.

The Please Select Boot Device menu appears. The PXE installation boot device is the physical network port configured to communicate with your network installation server. In the Boot Agent dialog, press F12 for a network service boot.

The Welcome to Client Installation wizard appears. In the Welcome to Client Installation wizard, press Enter to continue. The next dialog prompts you for a user name, password, and domain name.