Greetings all,
Please download and install KB2913760 as this patch is targeted to address the issue.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just got a brand new Surface 2 64GB for christmas, and everything is super cool except one big problem that is driving me really mad!
Here what happens:
And you can see a picture demonstrating the problem here: https://skydrive.live.com/?cid=aa3b180c21be0d1c&id=AA3B180C21BE0D1C%216544&v=3&ithint=photo,.png&authkey=!AAdpXLa67DM2MQQ
My question is: is there a way to manually fix this or Microsoft can solve/update the drivers once and for all in a later update? Is my S2 broken or it's just software-related problem? Should I wait the next updates or take back my Surface 2?
Update: I see everywhere BSOD problems and drivers update problems after Refresh/Restore on ANY machine (Surface 2) by now, this is a serious problems that MS need to fix ASAP for who Refreshed/Restored its device, and cannot wait till 14th January: we need fully working updated drivers right now!
UPDATE #2: Not only Tegra 4 display drivers will fail to install, but ALL the December update/drivers except Firmware will.
Anyway, I found a manual solution for now, and it worked for me:
UPDATE #3:
FINAL SURFACE 2 BSOD/DRIVERS PROBLEM QUICKFIX:
(And you shouldn't have any more bad errors in EventLog or Reliability Report too)
And there's more, you would successfully upgrade to newer firmware without any problem from now on.
GOOD LUCK
THANKS for listen!
-Paolo
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Greetings all,
Please download and install KB2913760 as this patch is targeted to address the issue.
Hey guys, I've discovered why are drivers are not updating.
The problem seems to stem from that fact that when the drivers don't get updated properly at the beginning, the newer drivers are being left in the driver repository anyway.
Wherever you subsequently point windows to update the drivers from (online / downloaded from this thread etc), it will just refer itself back to the drivers already in the repository. Even uninstalling the video device through device manager and clicking the checkbox to remove all driver traces doesn't seem to be clearing the repository in some cases, which is why people are having varying results.
So to install the newer drivers without a refresh / downloading etc, do this (all at your own risk, I don't actually know what I'm doing I've just used some common sense!)
To clear the repository of the newer display drivers that are **not actually in use (**don't clear the older ones being used currently, I don't know what will happen if you do that):
Follow the instructions here http://technet.microsoft.com/en-us/library/cc730875.aspx to
a) Identify the OEM number to remove - its the .2767 display adapter one.
b) Then remove this oem number
Then you can install the latest drivers in device manager. I actually loaded the ones kindly uploaded here, but retrospectively I suspect you can just let windows search online and that will do the tick.
**EDIT: This is not the case, device manager will not find any more up to date drivers online for some reason**
As for the audio drivers - that seems to be more difficult as the audio is split into multiple different drivers, so identifying the right ones to delete is more difficult.
**EDIT: I deleted all the .2774, of which there were 3, and the audio will subsequently be able to update.** There will be more for the Miracast ones etc though.
What this all means, however, is that as soon as MFST release some newer drivers (which will not be in our driver repository), they will all update fine anyways.
Hope this helps!
**EDIT**
As this is being marked as the answer, I'll add:
After resetting my surface 2, it did install the new firmware update, but there's no driver update included.
Still on 9.17.13.2674 from august 14th.
Same Problem here and i did everything too what you did. Hoping too that MS will start a fix before next patchday!
As you already noticed, many have the same issue. So far I have tried the impossible and there is not a way to fix it. MS is working on it.