Feature update to Windows 10, version 1703 - Error 0x80070005

Hi,

Error code 0x80070005 is also known as "ACCESS DENIED." It usually occurs when you lack a file or a registry permissions that are required to install the update. For us to assist you better, kindly answer the following questions:

• Have you made any changes to your computer prior to this issue?
• Which Version and OS Build number of Windows 10 is currently installed? To check, press the Windows key, type winver, and press the Enter key.
• Have you tried using the Windows Update Troubleshooter to troubleshoot the issue? You can download and run the troubleshooter for Windows 10 on this link.

Regards.

Hi,

Error code 0x80070005 is also known as "ACCESS DENIED." It usually occurs when you lack a file or a registry permissions that are required to install the update. For us to assist you better, kindly answer the following questions:

• Have you made any changes to your computer prior to this issue?
• Which Version and OS Build number of Windows 10 is currently installed? To check, press the Windows key, type winver, and press the Enter key.
• Have you tried using the Windows Update Troubleshooter to troubleshoot the issue? You can download and run the troubleshooter for Windows 10 on this link.

Regards.

Hi,

• The user account when the upgrade attempts to download/install is a local account and has administrative permissions.
• The only change to the computer recently was installation of the Update for Windows 10 Version 1607 for x64-based Systems (KB4033637) Aug 28 2017.
• Windows Version 1607 (OS Build 14393.1593)
• I just tried using the Update Troubleshooter (again). It found and fixed some things, but the Update has failed to install twice since running the Troubleshooter.

I have the same problem.  But I would like an answer to SFZ-2017's question: "Is there a way I can stop the update from trying to install?"  I, too, have version Windows Version 1607 (OS Build 14393.1593) installed.  The problem is just the continued failings of Windows 10 Creator (1703) to install.  So I just want my auto updating to stop trying to install it (1703).

Is there really any reason I can't just stick with Windows 10, version1607, and continue to automatically receive and install its upgrades, like I have been doing?

Thanks for answering my questions, especially the one in my second sentence above - the on SFZ-2017 asked initially!

I have the same issue. Did the troubleshooting repair and this comes up after selecting next on the troubleshooting dialog box.

Hi Cadkiller007.

 The only way I found to fix this problem was to revert to an earlier backup of windows10 64bit.
Once I did this I was able to update as normal.
If you wish, you may want to try a great back up program, Macrium Reflect.

The free version is the one I use and its very user-friendly. I do a back up every week to another Hard drive and after a month or so I will delete earlier backups that are really no longer necessary.
I hope this helps.

Lo

I have the same problem...

Version 1703 Build 15063.729

I have exactly the same problem and the same error. My computer (HP EliteBook 8560w) has repeatedly failed this update (Feature update to Windows 10, version 1703) since 12 August 2017. 

My current Windows 10 version is 1607 (OS Build 14393.1914). 

Having tried the Windows Update troubleshooter that has detected and resolved exactly the same issues as those described by others in this discussion, I decided to contact Microsoft Support. To my surprise  the error codes did not assist. I went as far as accepting their full remote control access to my computer. They have attempted a clean install (leaving my personal apps and files in place) using their latest (July 2017) Windows.iso file.

The update failed twice and on both occasions at 28%! 

The Microsoft (2nd level support person) told me that the only way forward would be to run a clean install thereby losing all of my applications and personal files!? 

This sounds like advising that to survive one must commit suicide.

Surely there must be a better way to resolve this issue?