Windows-itpro-docs: Surface Dock Firmware Update log

[BR77BE]

Why do the four characters "/l*v" appear under LOCATION in Table 1? Are they part of a location?
Why do I have no SurfaceDockFWI.log anywhere on my Surface after updating the dock firmware?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2a7b356e-3dbd-7f59-845e-a92e05865a52
• Version Independent ID: 711c5497-373f-662c-7fae-ba60f046e50c
• Content: Microsoft Surface Dock Firmware Update
• Content Source: devices/surface/surface-dock-firmware-update.md
• Product: w10
• Technology: windows
• GitHub Login: @Dansimp
• Microsoft Alias: dansimp

[ceaton001]

The "/l*v" [plus a path] should be appended to the msiexec command to create a log file, it's not created by default. I have already logged a doc bug for this.

[gchirlin]

There are additional Event ID values not listed in Table 2 of this article. Some of them include:
2007: Firmware update finished
2008: BEGIN dock telemetry
2011: END dock telemetry.

Although the description for the events (in the Event Viewer for Level: Information, Source: SurfaceDockFwUpdate) begins with "cannot be found", the interpretation is provided at the end of the General tab text.

[gchirlin]

Although there are no Event error messages, and Event 2007 says that the Firmware update finished. hr=0, the registry does not indicate the update is complete. This is after several power cycles and two days. I am using a Surface 6 with Windows 10 Pro v1903. The registry entry for Component10CurrentFwVersion is correct (and matches that of Component10OfferFwVersion). However, the registry entry for Component20CurrentFwVersion is incorrect: 0x0499a170, not matching the (correct) Component20OfferFwVersion of 0x04a1d570 per the table in this article. It seems to have stalled without actually making the update (or at least updating the registry). Any advice?

[e0i]

Hello, @BR77BE It is to our understanding that the PR #5093 addresses this issue. The PR has been created in response to same feedback provided by @ceaton001.

Additional feedback provided by @gchirlin is under investigation and content updates will provided as necessary.

Thank you all for providing valuable feedback and engaging with the community. Much appreciated.

[Justin-DynamicD]

There are additional error codes missing (beyond those identified above)

2006: Failed to send offer/payload pairs

[Denjiki]

@gchirlin had the same exact issue as I had. According to the setupapi.dev.log file, the firmware updated successfully. I also show Event ID 2007 in Event Viewer. However, the registry shows Component20CurrentFWVersion is 0x04915a70 (76634736) and not the same as the OfferFwVersion, which is 0x04a1d570. For what it's worth, my Component10CurrentFwVersion is correct & the same as the OfferFwVersion as well. So exactly as @gchirlin described. I am using a Surface Laptop 1.

[IoTNoob]

@gchirlin had the same exact issue as I had. According to the setupapi.dev.log file, the firmware updated successfully. I also show Event ID 2007 in Event Viewer. However, the registry shows Component20CurrentFWVersion is 0x04915a70 (76634736) and not the same as the OfferFwVersion, which is 0x04a1d570. For what it's worth, my Component10CurrentFwVersion is correct & the same as the OfferFwVersion as well. So exactly as @gchirlin described. I am using a Surface Laptop 1.

Same on Surface Book 1 but then when i disconnect Dock from Surface the LAN led start blinking. Then after a 5/10 min power from dock was removed. After 1/2 min power restore and then again blinking but its stop after while. Then connection to Surface and in reg i can see the proper version in 10 and 20.

[e0i]

@gchirlin @Justin-DynamicD The missing error codes that you have mentioned are now part of the documentation.