Why do we have to *guess* what Microsoft is doing with this firmware fix?
Doesn't being a paying customer entitle you to the company answering your questions honestly? Or at all....
Hey, MS - we're all guessing at what's going on. Why don't you just tell us?
How's that for a novel idea!
It would of course be good if Microsoft would discuss the problem and offer guidance. However, the best way to get them to emerge from their reluctance to comment may be to develop specific questions that someone can pose to Microsoft to result in us getting
some guidance.
For example, do we all fall into the following two groups:?
1. Those for whom the 10 December firmware update is listed in their update history as Succeeded, to whom the 18 January firmware update is offered. The recommendation for these people is clearly to install the firmware update.
2. Those for whom the 10 December firmware update is listed in their update history as Failed, who do not get offered the 18 January update. For these people the recommendation is unclear. At least some of us are now being offered the 24 October firmware
update for a second time, despite having installed that firmware update in October, and it being listed as Succeeded. Are we supposed to reinstall the 24 October firmware update, plausibly to repair the failed 10 December firmware update? Since some are
reporting problems after reinstalling the 24 October firmware update, it would be important to get some advice as to whether to try reinstalling that update that is listed as Succeeded.
Do the SP2 users fall into these 2 groups? If so, can we get Microsoft to answer the specific question of whether group #2 should reinstall the 24 October update?
Some more data from this group could help formulate such a question, so specific that it would look bad for Microsoft to stonewall.
The problem I am having is that I went back and dipped the device... yet still had issues. So will this ever be resolved? Because me device is not showing a failed update I am worried that I will not get the patch required to fix this.