Troubleshooting Device Installation with the Setupapi log File

Download 331.5 Kb.

Page	34/49
Date	10.02.2021
Size	331.5 Kb.
	#55795

1 ... 30 31 32 33 34 35 36 37 ... 49

setupapilog

6.3Rebooting Required

Problems that require rebooting are common. For example, an installation might appear to complete successfully but, when the Plug and Play Manager attempts to start the device, the device reports that it cannot start. The following example contains messages indicating that a resource conflict exists and that rebooting is required.

@ 13:45:17.176 #T396 Install Device: Restarting device "Blender_Device_Instance_ID".

@ 13:45:21.993 #T397 Install Device: Restarting device "Blender_Device_Instance_ID" completed.

@ 13:45:22.063 #W114 Device "Blender_Device_Instance_ID" required reboot: Device has problem: 0x0c: CM_PROB_NORMAL_CONFLICT.

@ 13:45:22.103 #T222 Install Device: Calling 'RUNONCE'/'GRPCONV' items.

@ 13:45:22.163 #I138 Executing 'RUNONCE' to process 26 'RUNONCE' entries.

@ 13:46:27.847 #I121 Device install of "Blender_Device_Instance_ID" finished successfully.
In the previous example, the #W114 message is the one that states that a resource conflict exists and that rebooting is required. The #T222 and #I138 messages then report that the system executed runonce.exe and grpconv.exe, which must run before the system is rebooted.

Note

Rebooting might not solve a problem, but it is the first thing to try. For help with troubleshooting device installation, see “Troubleshooting Device Installation” in the Windows DDK documentation.

Tip

To find all the messages that state that rebooting is required, search for the word reboot in an English-language SetupAPI log file.

Tip

No message explicitly identifies the fact that the system is being booted. However, you can infer that the system was rebooted if the time that elapses between sections or time-stamped messages indicates a delay that is consistent with rebooting.

Download 331.5 Kb.

Share with your friends:

1 ... 30 31 32 33 34 35 36 37 ... 49