I haven't received anything yet
...my patience is really being tested here
Microsoft didn't update any web page related to this firmware update.
I believe that the current release is for testing, and that the full release will be Tuesday.
If that is not the case, then the update is NOT provided by region, but by hardware revision/configuration (driver version installed).
Sources from Marie Jo at ZDNet states that this is a firmware of multiple ones to come (
Some Microsoft Surface Pro 2 users report a firmware fix rolling out | ZDNet). And as you remember, everyone had different experience when they installed the December firmware update. Some got it installed just like that, others got it installed after some hacking or workaround, others with changing drivers, others not even be able to install. So this indicated that they are different revision of hardware, and that means that Microsoft needs to put everyone Surface Pro 2, to the 'same page'. So this firmware update, is to fix a group of people problem with the December update (see it a custom firmware update), and other firmware for the groups are coming.
So while your patience is running thin, I strongly believe that you would prefer to get a proper firmware upgrade which fixes your issue, and not 'another December style firmware' and toss the Surface Pro 2 across the room, and b***** and moan how incompetent Microsoft is. It would have been nice to get more transparency, don't get me wrong on that, but that is what I think the situation truly is, if there isn't a mass firmware release by Tuesday.
Microsoft screwed up, I doubt it was intentional. I am sure everything went smoothly with the Pro 1 and Surface 1, they truly thought that their testing and procedure were correct. I am sure they even got experts. And with the Pro 2 everything falls down.
This is seen by software developers as the demo curse or the release curse. Where everyone, including yourself deeply tested the problem. You are using daily yourself to detect all bugs and issue, and everything is solid. Then comes the demo, or you release it, and then everything collapsed, because they are situation or system configurations you simply did not think about.
Example, look at Maple. This is math software, a VERY expensive software. over 2000$ software right there. 100$ for student
Guess what? There was a version of it, at some point, that the setup would get stuck if you have Chrome running. It doesn't touch Chrome, but for some reason the setup can't install some files, and the setup jams. While the company do say to close Chrome before starting the setup... some people also have the same problem without having Chrome installed... Firefox? IE? no.... Logitech mouse/keyboard drivers, SetPoint software. You have to kill it from the task manager, then the setup works. Strange, never used to be an issue, the setup was apparently not changed, everything was tested.. it's full Java including the setup, so one would think you are in a sandbox style environment... but nope. (this bug might actually be fixed by now, I don't know...)
Nvidia.. produced (well the selected manufacture produces the GPU, they just make the plans), their GPU always produced the same way.. but one day after more than a year for most people, massive disaster... graphic chips failing everywhere...OEM freaking out as huge amount of people what RMA'ing (sending for repair) their systems, costing manufactures millions of dollars loss. Why? Because the manufacture of the processor of the graphic card, either produced or ordered silicon wafer that was a hint, just a hint (less than 0.2 mm) thinner. So, it was a mess of who fault it was (as Nvidia is the one checking the GPU's produce and distributes them to manufacture that put it in computers or build the graphic card). It's been years they are working with the same chip manufacture, it's been years that they make GPUs. Yet, I guess they never though about checking for that, or didn't know the consequences of that, as the issue only appeared about a year of usage. So yea.. a curse, if you will.
Bad luck like this happens. In my book, it's OK, IF and ONLY IF, they are
active in fixing the problem, and not hiding the issue under the rug (Apple would probably tell you: too bad! No issue! You broke the system! You are not using it right). And if they learned their lesson and it doesn't happen again.