windows could not search for new updates, error code 80070490

hi! :)

It's my first post here. my windows cannot be updated, i think since last month. I have run SFC but it says that "did not find any integral violation", and I've also run the System Update Readiness Tool but still nothing worked.
I have an HP laptop with window 7 Home premium sp1 32bit OS. I'm not so good in computer thing.
I attached the cbs.zip file and the screen shot of the windows Update Error Codes as instructed here. I'm not so good in computer thing. and not speaking English fluently but i would really try my best to express what i really want to say. I hope I posted this correctly and any help would be appreciated. Thanks a lot.

Hi mr27 & welcome to sevenforums. Sorry 'bout the delayed response, too short of qualified helpers, too many needy forum members.

I'll take a look at the logs you posted and reply shortly.

Please be patient. :)

Here's the relevant part of the CheckSUR.log

Unavailable repair files:
servicing\packages\Package_1_for_KB2345886~31bf3856ad364e35~x86~~6.1.1.2.mum
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.mum
servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_2_for_KB977165~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_3_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.mum
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~x86~~6.1.1.2.mum
servicing\packages\Package_for_KB2345886~31bf3856ad364e35~x86~~6.1.1.2.mum
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~x86~~6.1.2.1.mum
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.mum
servicing\packages\Package_for_KB977165_RTM~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_for_KB977165~31bf3856ad364e35~x86~~6.1.2.0.mum
servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB979900~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.6.7600.256.mum
servicing\packages\Package_1_for_KB2345886~31bf3856ad364e35~x86~~6.1.1.2.cat
servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.cat
servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_2_for_KB977165~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_3_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.cat
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~x86~~6.1.1.2.cat
servicing\packages\Package_for_KB2345886~31bf3856ad364e35~x86~~6.1.1.2.cat
servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_for_KB2454826~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_for_KB2522422_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2522422~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2598845~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~x86~~6.1.2.1.cat
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~x86~~6.1.2.1.cat
servicing\packages\Package_for_KB977165_RTM~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_for_KB977165~31bf3856ad364e35~x86~~6.1.2.0.cat
servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB979900~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.6.7600.256.cat

I'll see how many of those I have and post a fix protocol. Will take some time to find those.

If I don't have all of them, NoelDP most likely will.

Worst case scenario for your issue would be Repair Install posted by Brink, repair install reinstalls windows, preserves all your files, folders, music, video, pictures, etc. Piece of cake, I do them all the time with minor issues, easily corrected.

These files pertain to Windows Update Agent. There is no official dowload for those. I'll have to look and see if I have them on External HDD win7x32 Home Premium.

WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum
WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.6.7600.256.cat
WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.6.7600.256.mum
WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.cat
WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.6.7600.256.mum

Man, I don't have a single one of the missing files.

Have you considered a Repair Install, it replaces windows7x32 Home Premium and preserves your installed programs, files, folder, video, music, pictures, etc. Piece of cake. Performed 3 repair installs past few days with minor easily correctable issues.

Things you'll need:

1. Your 25 character Windows Product Key, usually located on computer case, or laptop battery compartment
2. Windows 7 x32 Home Premium disc, or ISO (disk image file)

If you don't have your product key, it's located in the registry in binary form (ones & zeros) I have a Visual Basic script that will convert binary to alphanumeric.

If you don't have Windows 7 x32 disc, you can download ISO file from Microsoft Download Center.
You'll have to enter your product key, for verification by Microsoft, and then the download will be available to you. It's smart to have a Win7x32 DVD, just in case you need it. :)

You can perform repair install 3 different ways:

1. You can burn ISO to DVD, can't copy and paste with windows, I use ImgBurn, (free) simple interface.
2. Or you can open ISO with WinRAR x32 (also free trial) and extract all files to file you created on desktop whatever name you wish for folder. (could leave it as new folder if you wish)
3. You can burn ISO to USB Flashdrive and active same as DVD instruction.

From DVD, insert DVD, double-click it and Setup.exe will execute, or right-click DVD, choose> open and double-click Setup.exe

From Folder you made on desktop with WinRAR, open folder and double click Setup.exe

When Setup.exe starts the first screen says install windows, click and follow instruction.

Three important steps during repair install:

1. Make sure you have the Windows Product key, and if you have to obtain it with Visual Basic script (double or triple check that you have copied the key exactly (I use a sheet of lined paper, 5 characters, skip line, next 5 characters, etc.
2. If you are given a choice on which os to install, make sure you choose the same operating system, win7x32 Home Premium.
3. When you get to screen that says Upgrade that's the choice to make, it doesn't actually upgrade, it reinstalls the win7x32 HP.

If your machine has 4gb of RAM or less, you'll most likely get an error if you try to install the 200 updates & 13 optional. Windows update uses RAM, you can watch it fill up with task manager, right click the bottom of your screen in center, choose Task Manager, click Performance tab. With 4gb of RAM I usually choose the first 100 updates and they download and install. If you get an error on one or more updates, it's because Windows Update isn't smart and randomly provides updates, if a prerequisite update is not installer first, then an update or a few fail. Go through this process of update, reboot, update a few times and your good to go. Keep you product key handy if microsoft tells you it's not genuine, and tells you to call M$ or as I did just reenter key. M$ checks for valid key, which it is because it was genuine on your install, and your good to go.