Resetting Surface RT in NOV 2016. Cannot get Windows RT 8.1 Update 3. [Solved]

Anonymous
2016-11-15T05:47:14+00:00

Hi

I reset my Surface RT recently. After resetting, I could not get Windows RT 8.1 Update 3 back like before.

My Windows Update now checking for update forever. I left it open for 24 hours, the process is in infinite loop.

  1. I tried the method reset the Windows Update components (Stop services, delete Windows\SoftwareDistribution). It doesn't work.
  2. I check my installed update, I can't find KB2919442.
  3. I can't download or update any apps from Windows Store too. (wsreset.exe tried)

================

Updates (JANUARY 2017) *You can skip this to the solution below

================

  1. gianpietromerighetti found Windows RT 8.1 update 3 standalone installer
  2. Evan Forrest made a step by step guide to get Windows RT 8.1 Update 3
  3. Windows update and Windows Store issues are still not solved.
  4. According to Barb Bowman, Surface Support is aware of the problem and working to push a fix out quickly but don't have an exact time frame.

================

Solution (Issues solved)

================

Thanks to one of the community member Stjinchan found a solution and provided a complete guide.

Step 1: Download KB3173424 from HERE.

Step 2 : Download KB3172614 from HERE.

Step 3: TURN OFF your WiFi, and reboot the surface.

Step 4: Install KB3173424 by opening it.

Step 5: Reboot the surface.

Step 6: Install KB3172614 by opening it.

Step 7: Reboot the surface.

Step 8: TURN ON your WiFi, start searching for updates.

▲ Windows Update: I completed every updates using the method above.

▲ Windows Store: My Windows Store is working and got a new interface.

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 No comments
Answer accepted by question author
Anonymous
2017-01-17T19:55:27+00:00

After contacting Microsoft, and doing research for at least a few weeks, I found a solution to this major problem.

Alright, so I got a permanent solution for the Windows Update searching disaster! :)

Step 1: Restore your Surface RT with the recovery image from the microsoft website. (optional)

Step 2: Set up your surface and head to Windows update.

Step 3: Search for updates, after 30m-1h you will see a firmware update, press install without modifying the update list.

Step 4: After the installation succeeded, and your surface rt restarted go ahead and search again for updates.

Step 5: Again you will see a package of updates, this update includes the Windows RT 8.1 Update 1 update (kb2919355).

Step 6: When you finished installing the updates and your surface rebooted again, go to "installed updates" and check if kb2919355 is installed.

Step 7: If not, try to install the updates again. If it did, start searching for updates again.

Step 8: Once Windows Update is searching for at least 4 hours we came at the point where most of us are stuck.

THE SOLUTION

Step 9: Download kb3173424 from HERE.

Step 10 : Download kb3172614 from HERE.

Step 11: Turn off your Wifi, and reboot the surface.

Step 12: Install kb3173424 by opening it.

Step 13: Reboot the surface.

Step 14: Install kb3172614 by opening it.

Step 15: Reboot the surface.

Step 16: Turn on your Wifi, start searching for updates and after 10+/- minutes you will see 180+ updates coming your way :D.

I hope this helps a lot of people, since it was a major problem on the Surface RT.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

319 additional answers

Sort by: Newest
  1. Anonymous
    2017-02-17T16:26:01+00:00

    What do i enter to pipe it?

    A pipe looks like this:  |  and was already being used in the original pipeline.

    So, modifying the original pipeline would look like this

    SCHTASKS /QUERY /V | clip

    Since you are now using  PATHEXT=.exe  you don't need to specify that command's file extension as clip.exe.

    Otherwise, note the point:  schtasks was not being specified as schtasks.exeeither, so without its file extension and without there being a  PATHEXT=.exe  to guide the command processor nothing would happen, hence cleanup.txt would be a null file, as you observed.  More importantly without the PATHEXT=.exe there would be no way for the original scheduled task to run (if it was being started by the syntax shown where cmd.exe was only being entered as cmd), so that would explain why the "update" kept being re-offered--nothing was being "cleaned".

    FYI

    Robert


    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-02-17T13:13:58+00:00

    path does have exe among others.

    Was that a typo?  It's  PATHEXT=.exe

    No, not a typo.  i knew you knew what i was talking about.

    cleanup.txt comes up blank

    Have you looked at what is there?

    <repeat>

    instead of using the  findstr  I found it illuminating to pipe to  clip.exe  and then Paste the whole thing into Notepad.  Presumably then you could do your own manual Find (F3) for wnf

    </repeat>

    What do i enter to pipe it?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-02-17T06:23:56+00:00

    path does have exe among others.

    Was that a typo?  It's  PATHEXT=.exe

    cleanup.txt comes up blank

    Have you looked at what is there?

    <repeat>

    instead of using the  findstr  I found it illuminating to pipe to  clip.exe  and then Paste the whole thing into Notepad.  Presumably then you could do your own manual Find (F3) for wnf

    </repeat>

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-02-17T02:27:52+00:00

    still no change.

    still keeps offering the same update.

    I also get definition updates, and today I got a office 2013 update. those install ok, then back to the same one again.

    path does have exe among others.

    cleanup.txt comes up blank.

    Was this answer helpful?

    0 comments No comments