J'ai remarqué that my Windows 10 is no longer updating itself. When I exécutez le Paramètres app and problème an mise à jour command, this message appears.
>
Il y avait some problèmes l'installation mises à jour, but we'll try again later. Si vous keep seeing this and want to search the web or contact support for information, this may help: (0x80070006)
Of course, standalone mises à jour installer well. J'ai également been able to run a manual mise à jour from PowerShell and get Windows 10 to build 14393.970. Plus, Windows Defender keeps updating itself, so updating in general is possible.
J'ai tried running Microsoft Windows Mise à jour Troubleshooter. (The latest version from Microsoft website.) Nothing happened. J'ai également tried an [equivalent from tenforums.com](https://www.tenforums.com/tutorials/24742-reset-windows-update-windows-10-a.html). Not seulement did it not fix my problème, it broke Windows Defender too. (Système Restore came to rescue.)
Windows Mise à jour erreur 0x80070006
Re: Windows Mise à jour erreur 0x80070006
J'ai had this problème sur mon work PC and found that erreurs reporting an invalid handle can arise from Windows Mise à jour running in its own processus.
Vous pouvez try checking if Windows Mise à jour is running in its own processus, and si cela is, réglez-le sur `share` and redémarrer.
To check si cela is in its own processus, vous pouvez run `sc query wuauserv` in an elevated invite de commandes, and check what `TYPE` is reported. Par exemple, one that is is set to run as its own processus will look like this:
```
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>sc query wuauserv
SERVICE_NAME: wuauserv
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
```
To réglez-le sur shared (as it should be), run `sc config wuauserv type= share`, ensuite redémarrer your PC (redémarrer is necessary parce que of some problème avec SIDs not being correct sans bringing down the shared processus).
Once done, Windows Mise à jour devrait être fonctionnel (provided il y a rien else wrong avec it) and running `sc query wuauserv` should return a `TYPE` of `20 WIN32_SHARE_PROCESS`.
Vous pouvez try checking if Windows Mise à jour is running in its own processus, and si cela is, réglez-le sur `share` and redémarrer.
To check si cela is in its own processus, vous pouvez run `sc query wuauserv` in an elevated invite de commandes, and check what `TYPE` is reported. Par exemple, one that is is set to run as its own processus will look like this:
```
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>sc query wuauserv
SERVICE_NAME: wuauserv
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
```
To réglez-le sur shared (as it should be), run `sc config wuauserv type= share`, ensuite redémarrer your PC (redémarrer is necessary parce que of some problème avec SIDs not being correct sans bringing down the shared processus).
Once done, Windows Mise à jour devrait être fonctionnel (provided il y a rien else wrong avec it) and running `sc query wuauserv` should return a `TYPE` of `20 WIN32_SHARE_PROCESS`.