Micorosoft Surface RT won't connect to microsoft account or updat

Anonymous
2017-10-03T18:48:50+00:00

Hi there,

I have tried to sign into my Microsoft Account to connect the Surface RT, but every time it ends up with a message : "Sorry, we couldn't connect to Microsoft services right now. If this problem persists, search for "network problems" on the Start screen"

I have checked the clock, which is one of the culprits as per the forums, but i don't see any problem with it.

I have reset the surface to see if that would reset something but same result.

I have Run the WSReset.exe to same result.

I do not know what to do, without the Microsoft login, I can not do anything through the Microsoft Store.

Cheers,

Mohammad

Surface | Other

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.

0 comments
Answer accepted by question author
Anonymous
2017-10-04T08:10:15+00:00

Hi Mohammad,

We are aware that there are customers experiencing issues with Windows RT/8.1 devices connecting to their Microsoft accounts. Our engineers are currently working to resolve the issue as soon as possible.

In the meantime, please continue to use your local Windows login account for the time being. You may try to reattach your Microsoft account as a connected account at a later time.

We appreciate your understanding. Feel free to post back if you need further assistance.

Regards.

Mod Edit: Marking as answered to raise visibility.

(Update 10/11/17) A change was implemented on 10/10 that should resolve this issue.

Was this answer helpful?

6 people found this answer helpful.
0 comments

67 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-09-20T22:59:22+00:00

     current version is 8.1.

    The most significant thing after that is whether you have applied KB2919355 and anything else which supersedes it.  Unfortunately I have not found a way of making a list of supersedence except by sorting by InstalledOn but in the thread I linked to we found that the presence of that detail is not reliable.  Nevertheless in case your InstalledOn values are reliable here is the PowerShell pipeline I had suggested in the other threads I linked to.

    Get-HotFix | sort InstalledOn | ft InstalledOn, HotFixId -AutoSize  |  .\clip.exe

    The last stage is optional.  The idea is to pipe all the output to ClipBoard so you can then open a Notepad window (for example), do a Paste in it and do Finds etc. more conveniently that way.  I would be interested to know whether you have KB2919355 (for a start) and how big the other KB numbers are.  So, I suppose if you have the same problem with missing InstalledOn values which cause a problem for the sort stage an alternate pipeline which could be almost as informative would be

    Get-HotFix | sort HotFixId  | ft InstalledOn, HotFixId -AutoSize  |  .\clip.exe

    HTH

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-09-21T04:26:55+00:00

    So basically MS just bricked my Surface RT?  I had to reset it last week because the available storage memory kept shrinking for no reason, and disk clean up didn't really free up any space.  The reset cleared the memory issue, but now cant log on to my MS account, or update anything.  Same error as affecting everyone else.  If MS doesn't do anything to fix this bug, the machine is useless, if not severely crippled.

    Was this answer helpful?

    0 comments
  3. Barb Bowman 80,810 Reputation points MVP Volunteer Moderator
    2017-09-21T09:35:45+00:00

    I've been asking twice a day.

    >> From reading your other posts I can see that the bug relates to the account sign in issues. Do you have any idea on a timeframe for a possible fix?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-09-21T13:56:00+00:00

    cant log on to my MS account, or update anything.  Same error as affecting everyone else.

    That sounds different from what is being reported here.   Also, there are workarounds to get the RT "up to date".  And finally I think the only people who are affected at all by either problem are those who have tried to do a factory refresh.

    I have been meaning to mention also a detail which has not been discussed much.   Apparently KB3000850 may not be offered any more, yet that (as I mentioned) is what I still see as my "Most recent cumulative update".  I have tried elsewhere in these forums to find out what others are seeing now instead for that.   E.g. I imagine in most cases it will be KB2919355.   You need to get into the modern View your update history and apparently there is no automated way of getting there.  E.g. one way would be to start from Search Settings  (press Win-w), and type something that matches View your update history for Windows (vi up his  works for me and just vi is enough to see it listed first), then press Enter.

    Windows Image File Boot (WIMBoot) Overview

    <quote>

    November 2014: Windows 8.1 Update PCs configured with WIMBoot will not receive November Update (KB3000850).            

    </quote>

    So I think a natural question to arise seeing this fact would be:  "Does a factory refresh of a Win 8.1 RT result in a PC configured with WIMBoot?"   If so it could explain why so few others would see KB3000850 as their "Most recent cumulative update" and then it might also explain some missing functionality that would account for their problem symptoms.

    FYI

    Robert

    Was this answer helpful?

    0 comments