[SOLVED] Windows Update not working

[doveman]

Hi

I wonder if someone might be able to help me get Windows Update working again? I'm running Win7 x64 Ultimate.

I restored from a True Image as my previous installation had got somewhat cluttered and was having a few problems. After restoring, IE9 had some problems (kept locking up/crashing) so I decided to uninstall it and use IE8 and then reinstall IE9 sometime. In fact, IE8 has been having similar problems with locking up but anyway. In the meantime, Windows Update has been working OK to install new updates.

Today I decided I should reinstall IE9 because of the problems I'm still having with IE8. However, whenever I tried to install IE9 via Windows Update, or the one available update for IE8 instead, it failed with a 246 error.

I tried the MS FixIt (MicrosoftFixit.wu.MATSKB.Run.exe) which said that the Update Download location had moved and it was going to reset it to default. That didn't help and strangely it's found the same problem on subsequent runs as well.

Then I tried Option One from http://www.sevenforums.com/tutorials/91738-windows-update-reset.html to reset the Windows Update History. Same problem.

Then I tired Option Two Reset and Re-register Windows Update Components and re-booted. Same problem.

Then I ran sfc /scannow which found no issues.

Then I ran the System Update Readiness Tool and rebooted.

Then I followed the instructions to delete the contents of the SoftwareDistribution/Datastore and Download folders here http://windows.microsoft.com/en-PH/windows-vista/Windows-Update-error-80070002. I checked the Installed Updates after this as suggested and it's blank now but that may have been caused by one of the earlier attempts to fix it of course. I don't really mind not being able to see which updates were installed anyway.

After that Windows Update went into a loop, first offering KB2676562 and KB2679255 and after that KB2709715 and then back to the first two, all of which it said were successfully installed.

I tried turning off and re-enabling WU via change settings and now it's just giving me a 80070002 error when I try and Check for Updates, so I don't really know what to do next and would appreciate any help. Apart from the problem with WU and IE8/IE9, I've got this installation working quite nicely now so I hope we can fix these problems and I don't have to start from scratch again.

 

[niemiro]

Hello, and welcome to Sysnative Forums :)

Thank you for giving such a detailed account of what you have already tried. It makes it so much easier for me, and it is also quicker as I won't be recommending stuff you have already tried. Thank you :)

I checked the Installed Updates after this as suggested and it's blank now but that may have been caused by one of the earlier attempts to fix it of course. I don't really mind not being able to see which updates were installed anyway.

Just in case you are interested, this will occur when you either run Option One from the Seven Forums tutorial, or the manual deletion of the SoftwareDistribution folder. This isn't a particularly big problem, just in case you were interested.

Now onto what to actually do:

You have tried all of the simple fixes, and none of these have fixed the problem (but have ruled out many possible causes in the process), so it is time to dig into the logfiles, to see the exact reason why Windows Update won't progress. Then we can consider a fix.

The System Update Readiness Tool has two main functions. Firstly, it automatically fixes a few, but not many, problems. However, in addition to this, it is extremely good at detecting problems, even if it can't automatically fix them, so I will be looking at its logfile where it records these detected problems (CheckSUR.log) with great interest.

Also, the 0x8007002 error code usually shows up particularly clearly in a CBS.log, so I will be grabbing a copy of that too.

Those will be enough to get me started, and I can request more as and when I need them, which is extremely rarely.

So, the above was a bit of waffle for your own interest, but here is what you actually need to do:

Please copy the entire C:\Windows\Logs\CBS folder to your Desktop, right click on it > Send to > Compressed (zipped) folder, and upload the newly created .zip file here.

Thank you :)

Richard

 

[doveman]

Hi niemiro, thanks for the welcome and for taking the time to explain a couple of things to me :)

Please find attached a zip of the CBS folder as requested.

I should add that I did try one other Fixit (MicrosoftFixit.wu.LB.33269616388427092.15.1.Run.exe) before my previous post, which I seem to have forgotten to mention and that I tried one more (MicrosoftFixit50202.msi) for the 0x8007002 error since my previous post but to no avail. I shall refrain from trying anything else unless you advise from now on though, to avoid confusion :)

 

[niemiro]

Good morning :)

I am going to have to make this fix in a couple of parts. For this reason, you will probably not see an immediate improvement after just this post. Please don't be disheartened, and stick with me.

This post itself will also be in several parts. If you ever get stuck or require further explanation, please just stop and ask.

Some of the steps in this post may be quite complicated. Always stop and ask if you need help understanding something. Also, if you are not confident performing one of the steps, stop and ask for a simpler alternative, which there often is. However, you seem fairly competent in using computers, which is why I am giving you these quicker, but slightly more complicated methods.

WARNING: This fix has been designed specifically for doveman. If you are not doveman, do not follow these instructions, as you may cause harm to your computer.

Excellent, introductory spiel posted. Onto the fix :) Click to enlarge images.

Click Start > Search for regedit > right click on regedit.exe > select Run as Administrator

Expand HKEY_LOCAL_MACHINE, and look for a subkey called COMPONENTS



If you find it, jump to part one of the fix. If you do not find it, you must make it appear:

Single click on HKEY_LOCAL_MACHINE,



go to the File Menu > Load Hive... > navigate to C:\Windows\System32\config > select the COMPONENTS file (the one without a file extension - i.e. NOT COMPONENTS.log or similar, just COMPONENTS >



Click Open > Give it a key name of COMPONENTS > OK.



Now it should appear as in the first screenshot.



Ideally, do all of these fixes in a single sitting. If you have to restart your computer in between (which I would ask you not to, if at all possible), you will need to reload the COMPONENTS sub-hive as shown above after each restart.

PART ONE OF THE FIX:

Download the attached fixes.zip. Extract it to a new folder on your Desktop, double click on fix1.reg, and choose to import it into your registry.

PART TWO OF THE FIX:

Now I want you to import fix2.reg.

PART THREE OF THE FIX:

This is where, if you don't feel 100% confident, you need to stop and ask for additional instructions or an alternate method. It is important that the next two parts are done correctly.

I want you to remain in regedit, and navigate to this key:

HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\mdmusrgl.inf_31bf3856ad364e35_6®1.7600.16385_b2c1c88417dc71f1

Make sure you get EXACTLY the right key name as there are many keys with very similar names. Similar isn't good enough :)

If you can't find exactly the right key, stop and ask.

I want you to right click on that key and select Rename. I then want you to very carefully remove the corruption, and replace it with a normal full stop/period.

Old Name: mdmusrgl.inf_31bf3856ad364e35_6®1.7600.16385_b2c1c88417dc71f1
New Name: mdmusrgl.inf_31bf3856ad364e35_6.1.7600.16385_b2c1c88417dc71f1

Click anywhere to complete the rename.







FINALLY:

Please re-run the System Update Readiness Tool. If you have already deleted it, please re-download it, and save it somewhere safe (we will need it a few more times yet, most likely). If you still have it saved somewhere, then great, no need to re-download :)

After that, please get me a new copy of the C:\Windows\Logs\CBS folder, and we will see how much effect my fix has had.

Please don't expect Windows Update to work yet, though. I have only tried to fix about half of your corruptions so far, and it won't work until all are fixed.

Richard

 

[doveman]

Thank you for your very clear and detailed instructions :)

The COMPONENTS subkey was indeed not loaded so I had to load that as per your instructions.

Please find attached the new zip of the CBS folder.

 

[niemiro]

Awesome work! You have done amazingly!

Old log:

(f) CSI Missing Identity 0x00000000 appid mdmtron.inf_31bf3856ad364e35_6.1.7600.16385_1a632a9b22180b83 
(f) CSI Corrupt Deployment Keyform 0x00000000 appid mdmusrgl.inf_31bf3856ad364e35_6®1.7600.16385_b2c1c88417dc71f1 appid and keyform do not match; keyform is wrong.
(f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-onex_31bf3856ad364e35_6.1.7601.17514_none_03f1215c33fb2a93 
(fix) CSI Missing Identity CSI Registry Item Repaired amd64_microsoft-windows-onex_31bf3856ad364e35_6.1.7601.17514_none_03f1215c33fb2a93
(f) CSI Corrupt Identity 0xC0000161 (not UTF8) 635a6309244..3747a105055_31bf3856ad364e35_8.0.7601.21636_e3bdc400b4f52fe9 Bad identity
(f) CSI Corrupt Deployment Keyform 0x00000000 appid mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c20²376b9c50961e appid and keyform do not match; keyform is wrong.
(fix) CSI Missing Identity CSI Registry Item Repaired mdmtron.inf_31bf3856ad364e35_6.1.7600.16385_1a632a9b22180b83
(fix) CSI Corrupt Identity CSI Registry Item Repaired 635a6309244..3747a105055_31bf3856ad364e35_8.0.7601.21636_e3bdc400b4f52fe9
(f) CSI Missing Deployment Key 0x00000000 mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c202376b9c50961e HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 mdmusrgl.inf_31bf3856ad364e35_6.1.7600.16385_b2c1c88417dc71f1 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing C Mark 0x00000000 c!mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_48d5ea17c5a406fa amd64_mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_none_48d5ea17c5a406fa Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_48d5ea17c5a406fa successfully added to amd64_mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_none_48d5ea17c5a406fa
(f) CSI C Mark Deployment Missing 0x00000000 c!mdmussk1.inf_31bf3856ad364e35_6.1.7600.16385_48d5ea17c5a406fa amd64_mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_none_48d5ea17c5a406fa

+ one error in CBS.log

New log:

(f) CSI Corrupt Deployment Keyform 0x00000000 appid mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c20²376b9c50961e appid and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c202376b9c50961e HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!mdmussk1.inf_31bf3856ad364e35_6.1.7600.16385_48d5ea17c5a406fa amd64_mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_none_48d5ea17c5a406fa

+ one error in CBS.log

Another round of fixing is in order, but we have already made excellent progress. Well done :)

Please re-open regedit, and check to see whether COMPONENTS sub-hive is still loaded. If you have restarted your computer, you will have to reload it, otherwise it should still be there.

PART ONE:

Navigate to this key:
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c20²376b9c50961e

I want you to re-name this key also:

Old Name: mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c20²376b9c50961e
New Name: mdmusrf.inf_31bf3856ad364e35_6.1.7600.16385_c202376b9c50961e

Please delete and re-type all three characters. If you re-type just the corrupt 2, here, it may re-appear. Please just highlight and backspace all three digits, and then carefully re-type them.

Thank you.

 

[niemiro]

In addition to my above post, I want you to collect me some more information so I can plan the next parts of the fix.

Please open regedit, ensure the COMPONENTS hive is still loaded, and go to:

File > Export > Selected Branch:
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_mdmusrk1.inf_31bf3856ad364e35_6.1.7600.16385_none_48d5ea17c5a406fa

Give it a sensible name and save it somewhere you can easily find > Save

I then want you to repeat these steps, saving the following branch into a different file, but in the same folder:
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\msil_system.directoryser..protocols.resources_b03f5f7f11d50a3a_en-us_09a628e2cca77653

If you get any errors (such as "The selected branch does not exist. Make sure that the correct path is given."), please just let me know.

Finally, please navigate to the exported .reg files (let's say you called them export1.reg and export2.reg), highlight both of them > Send to > Compressed (zipped) folder, and upload the new .zip file here.

Thank you :)

 

[doveman]

Thanks. The log certainly looks a lot better so I can see we're making good progress :)

I did have to re-load the COMPONENTS sub-hive, even though I haven't restarted. I wonder if perhaps the System Update Readiness Tool unloaded it? After following your latest posts I closed regedit and re-opened it and the COMPONENTS sub-hive is still loaded now. Anyway, it's not a problem to reload it if it becomes necessary, just thought I should let you know in case it's relevant :)

Please find attached the exported branches as requested.

 

[niemiro]

Thanks again :)

Let's see if we can round up the last few stragglers in a single fix.

Several things will unload COMPONENTS - including a system restart, System Update Readiness Tool run (as you correctly guessed), and a few others. If I had been completely switched on, I would have realised that the SURT run I asked you for would have necessitated a reload. Ah well. You did well :)

Please ensure that COMPONENTS is still loaded, and load it if not. Then please import the attached registry fix (fix3.reg).

Restart your computer, and attempt to install some Windows Updates.

If it now works, then great :) However, I would still like you to come back, please, as I have seen a few things in your logs I would like to discuss with you (things I notice in your logs which although are not directly causing your current Windows Update problems, may cause problems in the future if not investigated)

If Windows Update still does not work, please re-run the System Update Readiness Tool, and post me a new copy of the C:\Windows\Logs\CBS folder.

It would not surprise me if it still doesn't work. Sometimes a second wave of errors won't appear until the first lot have been dealt with. If you can just get me the logs, we can go from there. We have fixed much and made excellent progress already.

Good luck!

Richard

 

[doveman]

Brilliant, that seems to have fixed it thanks :)

I've only tried installing the one IE8 update but that downloaded and installed without any problems.

There is one minor anomaly, in that when it finishes installing, it produces an extra identical Windows Update screen so that I have two to close. It was doing that before we started to fix it though (of course, then I had two WU screens with errors on as the updates failed to install, whereas now I have two WU screens showing that the updates were installed successfully, so that's a major improvement!). Perhaps this is related to one of the things you saw in the logs that you wanted to discuss?

Either way, I'm very happy that I can use WU again and very grateful for your help :)

 

[niemiro]

Brilliant, that seems to have fixed it thanks :)

I've only tried installing the one IE8 update but that downloaded and installed without any problems.

There is one minor anomaly, in that when it finishes installing, it produces an extra identical Windows Update screen so that I have two to close. It was doing that before we started to fix it though (of course, then I had two WU screens with errors on as the updates failed to install, whereas now I have two WU screens showing that the updates were installed successfully, so that's a major improvement!). Perhaps this is related to one of the things you saw in the logs that you wanted to discuss?

Either way, I'm very happy that I can use WU again and very grateful for your help :)

I am really glad that your problem seems to be now solved :)

Unfortunately, I do not know why your Windows Update is opening a second window, and I don't really have any idea how to go about fixing it. I am very sorry, but I have never seen anything like this before.

The thing which concerns me slightly is that the type of corruption your computer had is very rare. Not unheard of, but very rare.

Basically, you had about five bitshifts (where a binary 0 spontaneously changes to a 1, or vice versa). Usually, I see software causes of Windows Update file system or registry corruptions: powercuts during the updating process, a double failure in the updating and roll back procedures, messy driver uninstalls, etc. etc.

But your computer didn't have any of these: it had bitshifts. And to me, bitshifts mean hardware failure. Any part of hardware or software which handles the binary directly can theoretically be at cause (basically any piece of hardward, low level drivers, or filter driver). But you didn't have anything close to a normal distribution. The corruptions you had were mainly in the COMPONENTS sub-hive, and mainly grouped together in areas of similar versioning (likely to be stored contiguously, or near contiguously, on storage). This to me suggests hard disk failure.

It is not absolute proof, but I do think you should be aware that I have a suspicion that your hard drive (or perhaps some other part of hardware) is going bad. I am not suggesting that you should immediately throw it out, merely that good backups are even more essential than ever, IMO. I think that you should plan for your harddisk to suddenly die, or even just come to open a document, and find it can no longer be read (probably due to a single bitshift)

Just for your information.

If you want me to talk further about various hardware diagnostics, please don't hesitate to ask.

It has been a pleasure to work with you :)

Richard

 

[doveman]

Thanks.

The WU opening a second window is such a minor annoyance that if that's the only problem I still have (and I haven't noticed any others yet) I can live with it.

As for the bitshifts, it might be relevant that one of my RAM sticks recently died. I've replaced the RAM now but it caused a few BSOD before I diagnosed the problem so perhaps the COMPONENTS corruption was caused by that.

Anyway, I'll certainly bear your advice about ensuring I have good backups in mind.

Thanks again for your help :)

 

[niemiro]

No problem :)

It has been a pleasure to work with you. The dying RAM stick is probably the cause here - it could certainly cause bitshifts in this pattern and timeframe, and so is the most likely cause.

Take care,

Richard

 

[doveman]

Thanks, it's good to know you agree the faulty RAM stick is the most likely cause and that my HDD probably isn't dying. I still need to make sure my backups are up-to-date though :)

It was a pleasure to work with you as well. I was very impressed with how quickly you identified the problem and fixed it and I feel very lucky to have found this forum.

All the best.

 

[niemiro]

Thanks, it's good to know you agree the faulty RAM stick is the most likely cause and that my HDD probably isn't dying. I still need to make sure my backups are up-to-date though :)

It was a pleasure to work with you as well. I was very impressed with how quickly you identified the problem and fixed it and I feel very lucky to have found this forum.

All the best.

The logfiles reveal all and allow for a very quick diagnosis. It just takes quite a long time to learn to read the logfiles!

Feel free to send over friends or family who have Windows Update problems

 

[Sonia Parada]

Hola buenas tardes me puede por favor indicar el significado de la palabra Doveman : Eh:
Mil gracias

Read More:

[Quote = Niemiro; 27638] Buenos días :) Voy a tener que hacer esta revisión en un par de piezas. Por esta razón, es probable que no vea una mejora inmediata después de sólo este post. Por favor, no se desanime, y aferrarse a mí. Este post misma será también en varias partes. Si alguna vez se queda atascado o necesita más explicaciones, por favor, simplemente parar y preguntar. Algunos de los pasos de este post puede ser bastante complicado. Siempre parar y preguntar si necesita ayuda para entender algo. Además, si usted no está seguro de realizar uno de los pasos, parar y preguntar por una alternativa más simple, que a menudo existe. Sin embargo, parece bastante competente en el uso de los ordenadores, por lo que les estoy dando estos más rápido, pero los métodos un poco más complicados. ADVERTENCIA: Esta corrección se ha diseñado específicamente para Doveman . Si no está Doveman , que no siguen estas instrucciones, ya que puede causar daño a su equipo. Excelente, perorata introductoria publicada. En el arreglo :) Haga clic para agrandar las imágenes. Haga clic en Inicio > Buscar regedit > haga clic derecho en regedit.exe > seleccione Ejecutar como administrador Expand HKEY_LOCAL_MACHINE , y buscar una subclave llamados COMPONENTES Si lo encuentra, saltar a la primera parte de la solución . Si no lo encuentra, debe hacer que aparece: Un solo clic en HKEY_LOCAL_MACHINE , vaya a la Archivo Menú> Cargar sección ... > navegue a C: \ Windows \ System32 \ config > seleccione el COMPONENTES archivo (el uno sin extensión de archivo - es decir, no COMPONENTS.log o similar, simplemente COMPONENTES > haga clic en Abrir > Darle un nombre de clave de COMPONENTES > OK . Ahora debería aparecer como en la primera pantalla. lo ideal es hacer todas estas soluciones en una sola sesión Si. usted tiene que reiniciar el equipo en el medio (que le pediría que no lo hiciera, si es posible), tendrá que volver a cargar los componentes sub-colmena como se muestra arriba después de cada reinicio. PARTE dE lA REVISIÓN: Descarga los adjuntos correcciones .zip . Extraer a una nueva carpeta en el escritorio, haga doble clic en fix1.reg , y optar por importar en su registro. SEGUNDA PARTE dE lA REVISIÓN: Ahora quiero que permite importar f i x2.reg . TERCERA PARTE dE Remedio: .. Aquí es donde, si no se siente seguro al 100%, tiene que parar y preguntar por instrucciones adicionales o un método alternativo es importante que las dos partes siguientes se realizan correctamente Quiero que permanezca en regedit y vaya a esta Seguro que obtiene exactamente el nombre de la clave correcta, ya que hay muchas claves con nombres muy similares. similares no es lo suficientemente bueno :) Si no puede encontrar exactamente la tecla derecha, parar y preguntar. Quiero que hacer clic derecho en esa tecla y seleccione Cambiar nombre . Entonces yo quiero que usted pueda eliminar con mucho cuidado la corrupción, y reemplazarlo con una parada / período total normal. Antiguo Nombre: mdmusrgl.inf_31bf3856ad364e35_6 ® 1.7600.16385_b2c1c88417dc71f1 Nuevo Nombre: mdmusrgl.inf_31bf3856ad364e35_6 . 1.7600.16385_b2c1c88417dc71f1 Haga clic en cualquier lugar para completar el cambio de nombre. FINALMENTE : Por favor, vuelva a ejecutar la herramienta de preparación de actualización del sistema. Si ya ha eliminado, por favor volver a descargar y guardar en un lugar seguro (que será todavía necesita un par de veces más, lo más probable). Si todavía tengo guardado en algún lugar, entonces bien, no hay necesidad de volver a descargar :) Después de eso, por favor, dame una nueva copia de la C: \ Windows \ Logs \ CBS carpeta, y vamos a ver cuánto efecto tiene mi arreglo tenido. Por favor, no espere que Windows Update para trabajar todavía, aunque. Sólo he intentado fijar aproximadamente la mitad de sus corrupciones hasta el momento, y no va a trabajar hasta que todos se fijan. Richard [/ quote]













View attachment 2034





View attachment 2035



View attachment 2036



View attachment 2037





























View attachment 2040

View attachment 2038