04-04-2019 05:07 AM
We are trying to get information from Western Digital about how to debug this. We know that sanupdater.exe is failing, but we don't know why. When we try same config here and at WD, it works.
04-04-2019 05:22 AM
If it's possible to test on a clean-install of Win10, that's my only suggestion at this point.
I know that's a lot to ask but our only theory at this point is that it's something in your image that is interfering with the update, since we can't reproduce the problem here. I'm also asking WD to provide a version of sanupdater that has more logging but I'm not sure if they have that or not.
04-04-2019 05:32 AM
04-04-2019 06:02 AM - edited 04-04-2019 06:05 AM
Then lets wait.
Mainly because I'm not going to do this whole process every time there's a firmware update.
04-09-2019 06:36 AM - edited 04-09-2019 06:37 AM
I got this tool from WD: https://1drv.ms/u/s!ApXWjQB7_a1bhf1ovl0McF1vkV7gTw
Here are their comments:
1: This is our generic update tool combined with Lenovo unique FW image.
2: This can run on Win10 for WDC SN720, having the FW rev of 10114101 to update it to 10160101
3: This is a custom-build tool – it is only one exe file containing Lenovo unique FW
4: This tool generates Log with more information in the same folder where this program is : called “wdupdlog.txt” – please ask the customer to collect and send it to us regardless of the results.
5: Although we don’t expect issues (break anything) with the tool, as usual please remind Customer to backup critical data before running the tool as a precaution. Just we cannot be sure in what conditions the drive is now, backup would be safer and recommended. We ran sniff test and it went fine (but given we cannot reproduce the original failure, it cannot be a full guarantee…).
If you decide to try this, could you please capture wdupdlog.txt and upload it here? Thanks!
04-09-2019 11:37 PM