Forum Home
Press F1
 
Thread ID: 127912 2012-11-21 20:02:00 Windows Update Error 8024402F Koenig Tiger (14621) Press F1
Post ID Timestamp Content User
1313855 2012-11-21 20:02:00 Appreciate advice on whether it's okay / secure to leave my ipv4 set to static dns address etc.After trying every fix here and on the web over the last couple of weeks to fix my Vista SP2 Home Premium pc the only thing that actually works is changing DNS server addresses to PREFERRED 4.2.2.1; ALTERNATE 4.2.2.2 etc

This change fixed it immediatly...Why ? All other fixes didn't work at all and just wasted time...

Everything else also still works fine so my question is should I leave it with a static IPV4 dns address or should I change it back to auto and then chnage to static everytime I want to user windowsupdate.In other words is it secure to have a static dns permantly?

I'm quite sure this Windows Update Error 8024402F is caused by another update installed prior..But which one???

Aprereciate any opinions or advice from all especially Speedy & Wainutech etc 		Koenig Tiger (14621)
1313856 2012-11-21 20:30:00 With the pc I fixed with the same issue.
I changed the DNS , ran winupdate once, then changed the DNS back to auto.
After running Winupdate the 1 time, it seemed to fix the issue.

Try changing DNS back to auto & see if Win update still works 		1101 (13337)
1313857 2012-11-21 20:43:00 Cant really see any reason not to leave them in. Being on telstra (cable) you have to have static DNS on the router other wise they dont work.

As for why --Seems theres some sort of DNS issue and windows updates lately. Dont know if its only Xtra DNS thats causing it, or some other reason.

Some also use Googles DNS which appear to work fine as well. 8.8.8.8 and 8.8.4.4

if interested, have a read about them: developers.google.com 		wainuitech (129)
1313858 2012-11-22 05:17:00 I had that exact error constantly recently. The fix that worked for me in the end was changing the DNS to Google DNS (8888 & 8844) which enabled me to update again. I changed my DNS settings it back to automatic the next day and have had no problems with WU checking for updates since (like 1101 above). catspyjamas (15614)
1313859 2012-11-22 06:23:00 I have changed it back to auto and you are right windows update still works.

I still wonder how or why this works though when all other stupid suggestions on the net don't work at all.

MS must be aware of this and will no doubt secretly roll out a fix eventually.

Next I want to persuade my DV6 to install sp1 for W7 as again all suggestions on this forum and the web don't work.So if anybody has any new ideas here then please let me know.
On this I have tried everything literally....It installs all updates okay except sp1... 		Koenig Tiger (14621)
1313860 2012-11-22 06:29:00 What happens if you try and install SP1?? Have you tried to get it manually then install SP1? Speedy Gonzales (78)
1313861 2012-11-22 07:02:00 I have literally tried anything and everything Speedy and even ordered the disk from ms but nothing works...I also downlaoded. Updated the readiness tool several times..Followed all MS ideas to the letter
but no success...

It basically installs then does the restart and then fails with error Error 0x80070490.

I tried all 8 steps of Wainuitech's process but no luck.It will install any and all other updates okay and runs great.

I need something new to try.I refuse to rebuild it as I shouldn't have to and besides I'm not convinced that would work at all.

If you have any other ideas by all means let me know.I won't give up and have been trying for a year and a half now to get it to install SP1. 		Koenig Tiger (14621)
1313862 2012-11-22 07:17:00 Have you been here?? read Ben Is's post/s. (social.technet.microsoft.com)

It looks like this fixed the same prob on some of the other user's computers

I wanted to add some additional information that helped me resolve these 0x80070490 Element Not Found issues.

I tried everything posted in every link I found regarding this error (SFC, selective startups, System Update Readiness Tool, etc, etc, etc.). The only thing I didn't do was to do a repair/upgrade from the Windows DVD. I'm an IT professional and the idea of having to reinstall/repair the OS from the DVD to install a service pack just didn't sit well with me. Although this was only my second install of SP1, I went under the assumption that I might come across these same errors on multiple machines across one of the networks I manage. Going around and performing the Upgrade process from the DVD on multiple machines would just not be feasible.

I also want to state that my solution below might not work for every occurrence of the 0x80070490 Element Not Found errors, but it worked in my case. When troubleshooting, remember all the following:

1) Make sure you have a backup - or good recovery skill as anything you do may cause additional problems

2) Document all changes you are making so that you can revert or at least provide a step-by-step of all changes made

3) Perform all operations as an Administrator ("run as administrator")

Basically, there are two log files that you will want to use to troubleshoot this error. The first is the Component Based Servicing log located here:

c:\Windows\Logs\CBS\CBS.log

This log file gets backed up and replaced with each attempt, so you should open and review this file directly after a failed upgrade.

In my case I searched the file for errors and found a section like the following:

Info CBS Doqe: q-uninstall: Inf: wvmbushid.inf, Ranking: 1, Device-Install: 0, Key: 532, Identity: wvmbushid.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: wvmbusvideo.inf, Ranking: 1, Device-Install: 0, Key: 533, Identity: wvmbusvideo.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: wvmic.inf, Ranking: 1, Device-Install: 0, Key: 534, Identity: wvmic.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: wvmbus.inf, Ranking: 1, Device-Install: 0, Key: 535, Identity: wvmbus.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: wstorvsc.inf, Ranking: 1, Device-Install: 0, Key: 536, Identity: wstorvsc.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: usbvideo.inf, Ranking: 2, Device-Install: 0, Key: 598, Identity: usbvideo.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16543, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: sffdisk.inf, Ranking: 2, Device-Install: 0, Key: 599, Identity: sffdisk.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16438, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Doqe: q-uninstall: Inf: sdbus.inf, Ranking: 2, Device-Install: 0, Key: 600, Identity: sdbus.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16438, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2011-04-14 12:02:33, Info CBS Perf: Doqe: Uninstall started.

2011-04-14 12:02:33, Info CBS Doqe: [Forward] Uninstalling driver updates, Count 52

2011-04-14 12:02:34, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 11.

2011-04-14 12:02:34, Info CBS DriverUpdateUninstallUpdates failed [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2011-04-14 12:02:34, Error CBS Doqe: Failed uninstalling driver updates [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2011-04-14 12:02:34, Info CBS Perf: Doqe: Uninstall ended.

2011-04-14 12:02:34, Info CBS Failed uninstalling driver updates [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2011-04-14 12:02:34, Error CBS Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2011-04-14 12:02:34, Info CBS Shtd: Rolling back KTM, because drivers failed.

2011-04-14 12:02:34, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Temporary Rollback.

2011-04-14 12:02:34, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Temporary Rollback.



Like Andre.Ziegler posts above there seems to be an issue with a particular driver being found. In my case (like the original poster's), the last line referenced here before the error shows the sdbus.inf driver with a version of 6.1.7600.16438. This is the same as Andre finds in this poster's issue. Unfortunately the poster's original log files are no longer available at the link above, so I can't see if his log file is like mine. As you see from the excerpt above, there are multiple inf files being referenced, it just so happens that the sdbus.inf is last on the list (BTW, there are about 20-30 files being listed - my excerpt only shows the last half dozen or so line before the error).

It would seem (through a Google search) that version 6.1.7600.16438 of the sdbus.inf file is part of KB976422 (as Andre also notes). I attempted to reinstall this KB (using a convoluted method of first removing it from the registry, because it wouldn't properly uninstall. I won't go into this in detail because I don't think it was necessary in my final solution.

I repeated this procedure for the some of the additional drivers listed. My errors would sometimes vary, but mostly I continued to get the same errors in the CBS.log file time after time. I decided to hunt down some other log files. Since the errors seemed to be revolving around a failure to locate/load device drivers, I decided to look at the following log (which is the second important file you will want to reference)

c:\Windows\inf\setupapi.dev.log

I had two types of issues being logged in this file. The first was the failure to locate several inf files in the driver store. An example of this is below:

!!! sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad36 4e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo .inf' in Driver Store. Error = 0x00000490

<<< Section end 2011/04/14 17:13:38.216

<<< [Exit status: FAILURE(0x00000490)]

(BTW I recommend that you backup and delete your setupapi.dev.log file prior to your SP1 install attempt - this way you can be sure that what is logged is from your most recent attempt - as the file can be quite large to wade through).

I also found some errors in the file relating to "access denied" permissions issues while trying to copy temporary driver files to the C:\Windows\System32 directory. Unfortunately, I have deleted my older copy of the log, so I can't provide the exact error message.

To remedy these issues I performed the following steps:

1) For the drivers that can't be found in the driver store use the pnputil to load them.

Go to a Command Prompt and execute the following command:

pnputil -a [path to inf to load]

So, for the usbvideo.inf error above I would enter:

pnputil - a C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364 e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo. inf

You may get a pop up asking you to verify install of the driver. Once you verify to install the driver you should get a confirmation that looks similar to the below:

C:\Windows>pnputil -a C:\Windows\WinSxS\amd64_usbvideo.inf_31bf3856ad364 e35_6.1.7600.16543_none_8a1a2513d42628c3\usbvideo. inf

Microsoft PnP Utility

Processing inf : usbvideo.inf

Driver package added successfully.

Published name : oem32.inf

Total attempted: 1

Number successfully imported: 1



Perform this operation for each driver update .inf not found in the setupapi.dev.log file.

2) For the access denied permissions errors, simple rename each target file in the destination directory to .old. This will allow the files to be copied to their appropriate location on next run.

As I mention at the beginning of the post, I tried just about everything I found online to try to resolve this. I attempted a reinstall after each troubleshooting step (as I wanted to know exactly what resolved it). I must have attempted about 10-15 SP1 installs. In each attempt the SP1 seemed to install normally, started to shutdown my system, began configuring the update (somewhere between 9-11%) would reboot my system and then run through up to about 10-11% again when it would finally indicate failure and reversion.

Once I remedied the issues listed in the setupapi.dev.log as noted above (loaded each "missing" driver into the driver store, and renamed any target files to allow the re-copy), I reinstalled SP1 again and it went 100% smoothly.

While there may be other reasons you are getting the 0x80070490 Element Not Found issues, if you see similar issues in your log files, I think my steps may resolve the issue for you as well.

Good Luck! 		Speedy Gonzales (78)
1313863 2012-11-22 07:36:00 With the pc I fixed with the same issue.
I changed the DNS , ran winupdate once, then changed the DNS back to auto.
After running Winupdate the 1 time, it seemed to fix the issue.

Try changing DNS back to auto & see if Win update still works

Please tell me how to change the dns, in the router or where? I have been trying to resolve the exact same problem with the Vista machine at Seniornet for sometime now!

LL 		lakewoodlady (103)
1313864 2012-11-22 17:48:00 Under the LAN or wireless connection in Windows LL. Right mouse on the icon (for whatever connection youre using (Ethernet/Wireless) in the taskbar. You change the DNS server ip under the connection / properties / ipv4 Speedy Gonzales (78)
1 2