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
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

319 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-01-05T05:58:59+00:00

    looked at the ReportingEvents.log file and have included the link to the file.  I see it is showing Windows Update Client failed to detect with error 0x80004004.

    Since something finally worked let's leave that for now.

    Not sure if there is anything else useful in the log

    At the end.   Can you remember this happening?

    {516B89A4-793F-443E-8F49-B8FC4966DDF2} 2017-01-02 15:34:29:948-0600 1 190 [AU_SCHEDULED_INSTALL_SUCCESS] 101 {0B9090E6-3F73-4B3A-ADFC-EFE7276F761F} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Windows RT 8.1 (KB3063843)

    {0929A344-671D-4830-8893-B86835DE6E8F} 2017-01-02 15:34:29:963-0600 1 194 [AU_SCHEDULED_REBOOT_REQUIRED] 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Restart Required: To complete the installation of the following updates, the computer will be restarted within 15 minutes:  - Windows RT 8.1 Update (KB2919355) - Update for Windows RT 8.1 (KB3063843)

    {6E59D7CB-AA42-43B1-B8CE-599080E2C43E} 2017-01-02 16:37:02:912-0600 1 190 [AU_SCHEDULED_INSTALL_SUCCESS] 101 {5911DD13-A3EB-4B85-AB7F-FBE526507F50} 206 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Windows RT 8.1 Update (KB2919355)

    An hour later but I would have expected that this was OK.

    BTW sorry about the confusion over the Catalog query.  I did that from W10.  So, an idea would be to download it from the Catalog using a machine which could do that, then pass it to the RT--how ever you would be able to do that.

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-01-05T01:04:55+00:00

    I ran the fsutil hardlink again and got the same exact results as before (pending deletes).  I also looked at the ReportingEvents.log file and have included the link to the file.  I see it is showing Windows Update Client failed to detect with error 0x80004004.  Not sure if there is anything else useful in the log, but I have included the link below.  I also tried the Update Catalog link you provided and it goes to the following page -

    This website does not support your computer's processor.

    This website is designed to only work with x86 and x64 processors, and does not provide support for computers using Itanium (ia64) processors.

    https://1drv.ms/u/s!Akikga\_Mwunx9UyYQdYYbrvGcf0O

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-01-04T22:22:12+00:00

    The list of bcrypt.dll found now looks normal.  So what are those other things supposed to represent?  I was thinking that they could represent some  pending applies after some other installs but there isn't any sign of that (where the file is represented by bcrypt.dll).  I suppose the GUID that are given with each of those PendingDeletes are another representation of a module version but without access to source or support documentation (AND PROCMON!) it may be hard to figure out what exactly.

    I suppose it is at least worthwhile doing another  fsutil hardlink list  just to see if your Restart cleaned those up at all.  Other than that I'm not sure what we could look at that would be best.  Try ReportingEvents.log first and if there is anything interesting in there (e.g. evidence that later security updates were found) use the timestamps in there to index into WindowsUpdate.log.  There will be more detail elsewhere but we don't know what we are looking for yet.  Even if there is nothing in ReportingEvents.log there might be something in WindowsUpdate.log but finding it could be tedious, even more tedious if we find we have to invoke verbose logging in WU to get such necessary clues.

    As for things to "try" I can imagine that running DISM would shake things up a bit.  And I am still hoping that someone will respond to my query about using the downloads that appear to be available from the Catalog for ARM products (e.g. recent rollups for RT 8.1).

    HTH

    Robert

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-01-04T17:41:24+00:00

    Robert - I have run the PS command you suggested and below is the output.  Also, I have done a proper manual restart since the last update.

    PS C:\windows> LS -Re -Fi bcrypt.dll -Fo -Ea "SilentlyContinue" | sort LastWriteTime | select Length, FullName | ft -wra

    p -AutoSize | Out-String -width 90

    Length FullName

    103808 C:\windows\WinSxS\arm_microsoft-windows-bcrypt-dll_31bf3856ad364e35_6.3.9600.16384_

           none_832eca4c0afc5c93\bcrypt.dll

    104320 C:\windows\WinSxS\arm_microsoft-windows-bcrypt-dll_31bf3856ad364e35_6.3.9600.17031_

           none_8361bc900ad6a705\bcrypt.dll

    104320 C:\windows\System32\bcrypt.dll

    Was this answer helpful?

    0 comments