Microsoft Surface Dock Updater doesn't exist anymore so this should be taken out of the steps for checking on the update process.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
It looks like it still does but unless there the newest version dumps the build number back to the 1.X line?
Is this a mistake or is Microsoft just being Microsoft with the confusion?
It doesn't, if you download the latest version all you can do is check the registry for update information and the dock updater tool does not exist. Downloads for it has also been removed entirely.
So they have updated the file to support MSI but it is still a dock firmware updater.
If you continue to the to click the links the updater happens in the background while you work. The tool, where it says to use Microsoft Surface Dock Updater does not exist for download anymore.
@officedocsbot assign @jvsam
Thank you for bringing this to our attention @novarichuffman. And thanks for sharing the Tech Community link @Typhoon87. Reading through the ongoing conversation, it seems that it's only applicable to certain versions.
The firmware (MSI) is only installable on Windows 10 1803 and beyond (any edition). o In Windows 10 S mode, the previous tool didn’t work and it this one won’t since it’s a MSI package (no executables were able to run)...
Can you please confirm? It would help if you can let us know what specific information you want us to suggest to the doc author. Isn't the note added at the beginning of the doc enough? Should we add Requires Surface devices running at least Windows 10 version 1803 or later? The more information you can provide, the faster we can create a PR and submit it for review. Looking forward to your suggestions.
It seems that the instructions are wrong, you will never find anything in your Start Menu > All Apps after installing the new MSI.
@jvsam Say I had the old Dock Updater, the Microsoft Surface Dock Updater would exist on my devices. This new version (.msi) which runs in the background would not have any such application installed on these devices. The suggestion is to remove that part from the doc and instead refer to the regedit where you can see the status of your dock update.
I didn't look into it but the part where you can check a log of the installation seems like it could use more clear instruction.
The instructions recommend uninstalling the old updater first (which I did from control panel using appwiz.cpl), so no Start menu entry is found at all. I know it said no reboot was required, but I rebooted in an effort to get it to show up so I could find it.
@LtCmdrKeene Yes, that is because the author must have been confused and modified an old version of this doc where that would apply. If you had used the old updater in the past, thats exactly how it processed the fw update but since its now a background process it should basically just be removed from the doc.
Got ya. Well I can at least confirm it worked as expected otherwise. I opened regedit, looked at the key values and they were outdated. Unplugged my Surface Book 2 for around 30 seconds, plugged it back in, and nearly immediately the registry updated with the new values as described in the doc.
Can confirm as well, I have updated a few of the surfaces at our office via this new method.
I was hoping this would resolve a bug where my external monitor continuously turns on/off when the PC tries to put the monitor into standby mode. Is there an appropriate forum to post feedback about the dock itself? Maybe just the feedback hub, I'm not sure.
Likely the feedback hub, numerous surfaces of all types have docking issues that require a combination of enabling external montiors and restarting the surface while docked. It is a huge pain!
Hello @LtCmdrKeene and @novarichuffman, thank you so much for the clarification. This has been an interesting discussion. We always want to engage community users in improving the quality of the technical documentation, hence, the creation of this Github feedback system.
If you had used the old updater in the past, thats exactly how it processed the fw update but since its now a background process it should basically just be removed from the doc.
Which part of the doc you recommend removing or changing (perhaps restating) so we can assist in creating a pull request and submit it to the author for review? If you have a preferred messaging, please let us know. If you are familiar with the doc contribution process, I would also recommend you doing that.
As for submitting feedback or suggestions related to Microsoft Surface, yes you can submit it on UserVoice/Feeddback Hub. Your feedback goes directly to the Microsoft engineering team and they would love to hear what you think.
Hey, @jvsam
Looks like the change has been made, if im not mistaken.
That's great @novarichuffman. To confirm, are you talking about the change on step 2?
- After you connect Surface Dock to your Surface device, the tool checks the firmware status while running in the background.
Here are the recent updates to this doc.
Correct md file: https://github.com/MicrosoftDocs/windows-itpro-docs/blob/public/devices/surface/surface-dock-firmware-update.md
Yes that change is appropirate, the logging should be mentioned as part of the MSI execution. I see some comments that it is convoluted @jvsam
the logging should be mentioned as part of the MSI execution.
Thanks for the confirmation @novarichuffman. For the logging, specifically which information? Are you pertaining to this?
- If unable to verify, review Event logging and Troubleshooting tips in the next section.
Do you have any suggestions on how it should be written that will make it easier for Surface users to understand (or follow the steps)?
@jvsam I believe it should accurately tell the reader to declare those parameters during the installation.
Noting that the user can declare this as additional parameters upon installing the .msi
Thanks for the suggestion @novarichuffman. Make sense to provide more clarity.
If you are not busy @illfated, do you want to review this and create a PR with the recommended update? On a related issue (see #5046), a user mentioned that the log file is not created by default. Let me know, thanks as always!
Sure, I can do that. Thank you for the suggestion.
Sorry for the delay, I have not been well enough to do any constructive work lately. I will do my best to follow up this week.
No worries @illfated. You've been helping the community a lot, you deserve a break! :-)
@illfated, a gentle reminder. Only if you are not busy! :-)
Thank you for the reminder. Yes, it has been quite some time where I have had less surplus to be able to make any effort to contribute with much more than just comments and obvious PR content. I have also noticed some other tickets related to this issue, so there may have been some changes to the documentation lately, in light of the issue discussed above.
@illfated thanks. I see one that may be related, I'll get into that. The suggested update here with regard to logging will clear some of the confusion.
Thank you. I noticed that there is at least 1 existing PR for this page, so maybe we could ask @j0rt3g4 if this is something he could add to his existing PR.
There is also https://github.com/MicrosoftDocs/windows-itpro-docs/pull/5274 by @VLG17 related to this.
Thanks @illfated, #5274 suggests to delete the location path, but here, it's recommending to add or call out /lv %windir%\logs\ SurfaceDockFWI.log* when installing the .msi update. #5098 is also a different update.
@j0rt3g4 will you be able to assist and add this update on your PR? Thank you in advance.
@illfated do you have any recommended messaging so @j0rt3g4 can add it to his PR?
@jvsam sure thing I'd do it
Thank you so much @j0rt3g4!
Hi @novarichuffman, there have been a couple of approved changes to this documentation that will address the issues raised here. The content updates will be displayed here at docs.microsoft.com in the next scheduled publishing run. Feel free to re-open or create another issue through the doc's feedback feature, if you have other suggestions or ideas to improve the quality of this documentation.
Thank you for your feedback and for being part of the Microsoft Docs community!
@officedocsbot close
Most helpful comment
@jvsam sure thing I'd do it