Greetings all,
Please download and install the Surface Pro 2 System Firmware Update for March 11th. This is targeted towards the Telemetry Driver:
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I just picked up my Surface Pro 2 256GB today and it ran into problems right after applying the firmware update that seemed to have been released just today on Windows Update. I confirmed this problem was caused by the firmware update because I restored the tablet and the wireless was working fine and I applied the firmware update and that broke the wireless.
After the update, the Marvell AVASTAR Wireless Composite Device stopped working...meaning, the tablet does not recognize the wireless card. This is confirmed by going into the Device Manager and seeing 2 unknown devices (one of them was the wireless card, the other unrecognized device I will explain in the next paragraph) When I tried running the update driver function, it tried to reinstall the driver but returned the following error.
Windows encountered a problem installing the driver software for your device
Reinstall the drivers for this device (Code 18)
I had to go the manual route and there were 2 Marvell drivers listed and one Microsoft driver listed for the Marvell card. The 2 marvell drivers listed had exactly the same name. However, only choosing and applying the second one worked. So, the wireless was working again.
The other "unknown device" turned out to be something called "Surface Cover Telemetry". However, trying the same troubleshooting process for the wireless card did not solve the problem and the devices still remains "unknown" in the device manager. I just left it and carried on with installing my other software and apps as the tablet and the Type Cover 2 seemed to be functioning properly.
However, when I put the tablet to sleep by closing the Type Cover (while on battery power but charged up to 100%), the screen remained blank even though I opened up the cover again and tried to wake the tablet. I knew that the tablet was still on but the screen remained blank even after I tried touching it, typing on the keyboard as well as briefly tapping the on/off button. When I touch the Windows icon on the bottom frame of the tablet, I can feel a slight vibration and that told me that the tablet was on but the screen somehow is totally off.
I decided to do a soft reset of the tablet by holding on the on/off button for more then 10 seconds. However, the screen only worked properly after many attempts.
My questions are, could it be that this "unknown device" that needs the "Surface Cover Telemetry" driver is causing this blank screen problem? And if so, where can I download a driver that works?
Thanks.
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 the Surface Pro 2 System Firmware Update for March 11th. This is targeted towards the Telemetry Driver:
I’ve struggle with the same issue with my SP2 128 GB, I had to reset the SP2. Sadly by removing everything and reinstall windows.
Even after the first attempt, by removing everything, I still got problem with unknown device under device manager. I still went forward and took the windows update again and install all the patches and firmware and driver pack.
After reboot I still got problem with unknown device and now also the Bluetooth and wireless network doesn’t work for some reason.
Here's what I did. Do so at your own risk. Otherwise call Microsoft for support.
I went to reset the SP2 again, rebooted and as you know, unknown device under device manager still there. First thing I did was to download the Surface Pro 2 firmware and driver pack here and unzipped the file. Went into unzipped directory
Right click to the SurfaceCoverTelemetry.inf file and install it.
Now the, unknown device is gone. 2. Go to device manager and updated the Marvell AVASTAR 350N Wireless network controller.
Choose Brows my computer for driver and software and point it to the unzipped directory.
October2013SurfacePro2\Marvell\WLAN\win81\x64 3. In device manger under Firmware, I did update the Surface Pro System Aggregator firmware and also the UEFI driver. 4. Now reboot and go to windows update and install all the patches and Surface Pro 2 firmware and driver package, after reboot, SP2 should work as a charm now.
Good luck.
same problem here.
i've resetted my sp2 128g after the failure that the 1st fi3mware was, then installed the good one. telemetry still wasn't up but whatever.
then today i had to use my touchcover2 for a demo at a friends house.. it wouldn't work. the touchpad is working fine, keyboa4d is backlit even, but keys won't type. anything.
i did a search for drivers to solve these 2 '?' i had; searched under the keyboard drivers, then the ? disappeared, but kb still doesn't work.
i am pissed bc i don't want to have to do a reset AGAIN even tough i only have a Firefox, photoshop/illustrator, vlc... only a few. i don't get why Microsoft doesn't do anything about it and now sells surfacepro2 with a new i5 cpu....
Looked at the inf and determined the service.
Set windows driver foundation - user mode driver framework to startup type automatic instead of manual - fixed.
Hope this works for all.
Disregard...it's back.
This is the fix below:
http://systemsadminguy.wordpress.com/2013/11/16/how-to-update-surface-pro-2-recovery-image-drivers/
I followed your first suggestion, but nothing changed.
The fix you linked requires one to reset his/her Surface, which I don't want to do. MS should be releasing a fix soon.
Can anybody report actual issues connected to this missing drivers issue? I don't have any, so I can't figure out what those drivers (telemetry and audio) should have to do with my Type Cover 2.
Looked at the inf and determined the service.
Set windows driver foundation - user mode driver framework to startup type automatic instead of manual - fixed.
Hope this works for all.
Disregard...it's back.
This is the fix below:
http://systemsadminguy.wordpress.com/2013/11/16/how-to-update-surface-pro-2-recovery-image-drivers/