Search results

I had created two, drive C & D, partitions on the SP4 flash drive. I was using drive/partition C for Windows and all app installations. Drive/partition D was for all my data including OneDrive which I had remapped to drive/partition D. I reformatted drive/partition C to reinstall Windows 10, but...

That sucks. Considering that this a dynamically assigned IP, is there anything I could do to resolve this issue? PS: Strangely enough, I no longer have a problem accessing surfaceforums.net. At least for now, that is.

Your IP Address Is: 122.162.72.65 But strangely enough, I can now access the website without a proxy. I am no longer getting the "Your IP address has been banned." message.

The message does not show any IP address. All it says, is:

Several 'firmware' updates and one driver update were reported by 'Windows Updates' as having 'failed'. But the firmware & driver versions show the latest versions. Except one particular driver. In fact this one I had tried to install several times but without success. -> Intel(R) Control Logic...

I am using a proxy service to be able to login here and post this. For whatever reason I have been unable to access surfaceforums.net for a while now. Every time I try to access the site, I get the following message: Can someone help fix this issue so that I don't have to use a proxy each time...

Although I am able to connect my LG G3 via Miracast, at least it says it's connected and AirServer on the SP3 says it's waiting for device to start streaming, I am unable to actually mirror anything the SP3. It works fine between my LG G3 and my Samsung TV. But no luck with the SP3 via AirServer.

For me the most glaring omission is a USB-C port with USB 3.1 support. The USB-C port was something that I had taken for granted will be on the SP4. I am surprised that the media has not made a fuss about this omission. I really can't think of any reason for this omission. The lack of the LTE...

This solved the problem and Windows Update seems to be working fine now. Thanks a lot.

Since August 2nd, Windows 10 has been unable to update. Every time I run the update manually, I get the following error. Any help will be appreciated. Thanks.

Any idea why I am unable to download the Insider Hub App from the Store?

Couple of hrs is all I get before the SP3 runs out of juice. This is with Windows 10 Insider Preview Build 10130. With Windows 8.1 I used to get a little over 4 hrs.

June 2015 updates for the Surface Pro 3 The following updates will be listed as “System Firmware Update – 6/23/2015” when you view your update history. Note When Surface updates are provided via the Windows Update service, they are delivered in stages to Surface customers. As a result, not...

Considering that with Build 10130 the max I get is approx 2 hrs and never got better than 4 hrs with a charge, it's not like there's much of a choice but to keep the SP3 plugged in all the time.

Add me to the club of those who think that this dumbing down of OneDrive in Wndows 10 is really stupid. I used to keep all files "available offline" on my desktop and kept most files "available online" on the SP3 due to the limited storage. This reason alone is enough for me to reconsider moving...

15 minutes at 0% / 3% , really? Anyhow attempting again now. Luckily it doesn't require downloading the whole build again.

Build 10130 The update was stuck at 0%/3% for a long time, so I used the power button to restart. Upon restart I got a message stating "restoring previous windows" and then it proceeded to boot into Build 1o122. Once logged in I got the following error 'oxc19000101 - ox200oc' Bummer.

Be prepared for the 'System Firmware Update - ‎5/‎14/‎2015' to reappear even though it has seemingly, finally installed. Other than the many.many failed attempts, I have this firmware update listed as installed, four times already.

I am getting barely over 3 hrs. But then again I was getting about 4 hrs 15 min before this build and never got more than 4 hrs 30 min even when the SP3 was brand new.

I used the fixes route to update from 10074 to 10122. I am forced to use the 'power + volume' button when the 'power' button by itself fails to work. And with this build it is more often than not.