error 80070490

Discussion in 'Windows Update' started by gene7851, Aug 19, 2007.

  1. Here is a simple solution that has worked for me. I downloaded and installed
    a 30 day trial version of ErrorFix (registry cleaner). It recognized the MS
    updates, downloaded and installed them. When I checked the update history for
    vista the updates were listed there. However, windows updater still won't
    work and gives the same error. But at this point I have had enough and will
    purchase the registered version of this program and use it to obtain MS
    updates. I have been checking the internet about this problem and it seems to
    go back for quite a few months. But where is MS in helping to solve this
    problem. Maybe my next purchase will be an Apple computer....
     
    canadian user, Jan 14, 2010
    #61
    1. Advertisements

  2. PA Bear [MS MVP], Jan 14, 2010
    #62
    1. Advertisements

  3. Sure - another one that thinks that switching platforms (in any direction)
    will resolve all their problems. Please - do switch. Sometimes it works
    out for the switcher, most of the time it just presents itself in the form
    of new problems with fewer friendlier resources than previously to turn to
    and more money spent/more time spent. It doesn't matter if you started at
    the macintosh and are deciding to switch to windows or started at linux and
    are deciding to switch to windows or started with windows and decided to
    switch to macintosh - usually the change is worse than the solution to
    *your* problem would be. ( There in-lies the actual issue - seldom does
    anyone come to the conclusion that the problem is with their
    system/something wrong there and not some overall conspiracy of the
    OS/software companies to keep them from working/playing as they want to.
    ;-) )

    So here you are - and in your rant you only really gave two bits of
    information (accidentally I would say) which are in the subject line (error
    80070490) and the fact that you have Vista (sort of mentioned 'in passing').

    Based off that - not much to do but give it a shot. So - let's go through
    your problem *if* you are wanting to fix it.

    You should get the edition and version information...

    Start button --> RUN
    (no "RUN"? Press the "Windows Key" + R on your keyboard)
    --> type in:
    winver
    --> Click OK.

    The picture at the top of the window that opens will give you the general
    (Operating System name and edition) while the line starting with the word
    "version" will give you the rest of the story. Post _both_ in response
    to this message verbatim. No paraphrasing - instead - ensure
    character-for-character copying. That's the edition (in the top picture)
    and the exact version number in detail (the 'version' line.)

    What version of Internet Explorer are you currently using? Easy to find
    out. Open Internet Explorer and while that is in-focus, press and hold
    the "ALT" key on your keyboard. With the "ALT" key still pressed, press
    (just once, no holding) the "H" key. Now, with the "ALT" key still
    pressed, press (just once, no holding) the "A" key. That will bring up
    the "About Internet Explorer" window. It will give you the exact version
    you are using - repeat what you see there in response to this message.

    How to determine whether a computer is running a 32-bit version or
    64-bit version of the Windows operating system
    http://support.microsoft.com/kb/827218

    What AntiVirus application are you using? (Name and exact version, please.)
    - Was any flavor of "Norton" products ever installed?
    - Was any flavor of "McAfee" products ever installed?

    Do you have a third party firewall - or are you using the built-in Windows
    firewall?

    Do you ever run any antimalware applications? If so - which ones and when
    did you scan with them last (full scan, not quick)?

    Some stuff you can do... In order (may seem like quite a bit, but you let
    the
    machine get into quite a state, this should clean it up.)

    Reboot so you start with a fresh machine. For everything here you will
    need to logon as an user with administrative (installation) priviledges.

    Download/install the "Windows Installer CleanUp Utility":
    http://support.microsoft.com/kb/290301

    After installing, do the following:

    Start button --> RUN
    (no "RUN"? Press the "Windows Key" + R on your keyboard)
    --> type in:
    "%ProgramFiles%\Windows Installer Clean Up\msizap.exe" g!
    --> Click OK.
    (The quotation marks and percentage signs and spacing should be exact.)

    It will flash by *quick*, don't expect much out of this step to get
    excited about. But the cleaner your machine is to start with, the
    better your luck will be later (not really luck - more like preparedness,
    but that's not as fun to think about, eh?)

    Yeah - you will get tired of rebooting - but let's soldier on and reboot
    again and logon as an user with administrative priviledges.

    This time (and this is one of the more time-consuming steps) you will be
    running (one at a time with a reboot in-between) three different
    anti-spyware/anti-malware applications to ensure you come up clean.

    Download, install, run, update and perform a full scan with the following
    (freeware version):

    SuperAntiSpyware
    http://www.superantispyware.com/

    Reboot and logon as administrative user.

    Download, install, run, update and perform a full scan with the following
    (freeware version):

    MalwareBytes
    http://www.malwarebytes.com/

    Reboot and logon as administrative user.

    Download and run the MSRT manually:
    http://www.microsoft.com/security/malwareremove/default.mspx

    You may find nothing, you may find only cookies, you may think it is a
    waste of time - but if you do all this and report back here with what you
    do/don't find as you are doing all of it - you are adding more pieces to
    the puzzle and the entire picture just may become clearer and your
    problem resolved.

    Reboot and logon as administrative user.

    At this point - if the machine was mine - I would follow these directions:
    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/ea20ba99-017e-4ae0-975b-1ef8b771dff8

    In other words... Use the .NET Cleanup Tool (Method 2), reboot and install
    the .NET Updates in this order:

    - .Net Framework 3.5
    (http://www.microsoft.com/downloads/details.aspx?familyid=333325FD-AE52-4E35-B531-508D977D32A6)
    - .Net Framework 1.1
    (http://www.microsoft.com/downloads/details.aspx?familyid=262D25E3-F589-4842-8157-034D1E7CF3A3&)
    - .Net Framework 1.1 SP1
    (http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&)

    Needs repeating in full?
    When installing updates using Windows update or Microsoft Update you may
    receive Error 0x643 or 0x80070643 (23 Oct-09)
    http://support.microsoft.com/kb/976982

    =====================

    Step #1 => Before doing anything else, write down what .NET Framework
    versions are currently installed:

    How to determine which versions of the .NET Framework are installed and
    whether service packs have been applied
    http://support.microsoft.com/kb/318785

    Step #2 => Now see Resolution Method 2 in this related KB article...

    When you try to install an update for the .NET Framework 1.0, 1.1, 2.0, 3.0,
    or 3.5, you may receive Windows Update error code "0x643" or Windows
    Installer error code "1603" (ignore the title, if need be)
    http://support.microsoft.com/kb/923100

    After running the .NET Framework Cleanup Tool, reinstall all .NET Framework
    versions (but only the ones you wrote down in #1 above) manually using the
    download links on the page then run Windows Update manually to install
    security updates for same.

    NB: If you remove .NET Framework 3.5 (SP1) using the tool, reinstalling .NET
    Framework 3.5 will also install .Net Framework 2.0 SP2 and 3.0 SP2; then
    Windows Update will offer .NET Framework 3.5 SP1.

    IMPORTANT! => If you remove .NET Framework 3.5 (SP1), reinstall your .NET
    Framework versions in the following order:

    1. .Net Framework 3.5, then...
    2. .Net Framework 1.1, then...
    3. .Net Framework 1.1 SP1

    NB: KB923100 references this page:
    http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx. Please read
    ALL of it as well as the related page
    http://blogs.msdn.com/astebner/pages/8904493.aspx before using the .NET
    Framework Cleanup Tool.

    I would then check the hard drive(s) for errors and straighten things up...

    Windows Vista CHKDSK:
    http://www.windows-help-central.com/windows-vista-chkdsk.html

    Windows Vista Defragmentation:
    http://windows.microsoft.com/en-us/windows-vista/Improve-performance-by-defragmenting-your-hard-disk

    Now - before checking for more updates - I would do something else, but you
    have not yet provided your operating system details. So...

    32-bit Windows Vista ______ Edition with No SP or Service Pack 1 or 2

    How do I reset Windows Update components?
    http://support.microsoft.com/kb/971058

    .... and click on the "Microsoft Fix it" icon. When asked, select "RUN",
    both times. Check the "I agree" box and click on "Next". Check the box
    for "Run aggressive options (not recommended)" and click "Next". Let
    it finish up and follow the prompts until it is done. Close/exit and
    reboot and logon as administrative user.

    64-bit Windows Vista ______ Edition with No SP or Service Pack 1 or 2

    Download, install and run...

    System Update Readiness Tool for x64-based Systems
    http://www.microsoft.com/downloads/details.aspx?FamilyId=f6f353c0-d00e-43e7-97ef-0feefc7ff064

    Reboot and logon as administrative user.

    Now - after all that - try your updates again.

    Come back and let everyone know if it worked out for you or at least provide
    the requested information so someone might be able to help you further.

    Now you might say that you have tried all of this before - but was it all at
    once and all in the order given? If not - please - follow the directions as
    given all at once ignoring whether or not you think/know you have done one
    step before and/or you think you have done an equivalent step.

    Worst case - after you do all this - you will still have a problem but a
    much cleaner system and will have provided those here with something they
    can work with instead of just waiting on someone else to fix the problem
    with your system.
     
    Shenan Stanley, Jan 14, 2010
    #63
  4. gene7851

    matt_j Guest

    i did the same thing as well and still no help. i tried to re-update it and
    it failed again too.
     
    matt_j, Feb 2, 2010
    #64
  5. "shaker ismail
     
    shaker ismail, Feb 9, 2010
    #65
  6. gene7851

    London User Guest

    None of these rubbish work and every link I tried to download - none of them
    work.

    If I to upgrade from Vista to 7, will this go away?

    This error is now effecting my iTune/iPhone firewire upgrade.

    Can someone come back to me?

    Thanks and regards,
     
    London User, Mar 13, 2010
    #66
  7. No one even knows what your specific problem or specific operating system
    is. You have hijacked a 2 month old conversation (at least the part you
    responded to - the conversation actually started 3 months ago...) and gave
    *no details* even though the very part you responded to gave you
    instructions on how to do so.

    My suggestion is simple - give some details on *your* issue.

    You should get the edition and version information...

    Start button --> RUN
    (no "RUN"? Press the "Windows Key" + R on your keyboard)
    --> type in:
    winver
    --> Click OK.

    The picture at the top of the window that opens will give you the general
    (Operating System name and edition) while the line starting with the word
    "version" will give you the rest of the story. Post _both_ in response
    to this message verbatim. No paraphrasing - instead - ensure
    character-for-character copying. That's the edition (in the top picture)
    and the exact version number in detail (the 'version' line.)

    What version of Internet Explorer are you currently using? Easy to find
    out. Open Internet Explorer and while that is in-focus, press and hold
    the "ALT" key on your keyboard. With the "ALT" key still pressed, press
    (just once, no holding) the "H" key. Now, with the "ALT" key still
    pressed, press (just once, no holding) the "A" key. That will bring up
    the "About Internet Explorer" window. It will give you the exact version
    you are using - repeat what you see there in response to this message.

    How to determine whether a computer is running a 32-bit version or
    64-bit version of the Windows operating system
    http://support.microsoft.com/kb/827218

    What AntiVirus application are you using? (Name and exact version, please.)
    - Was any flavor of "Norton" products ever installed?
    - Was any flavor of "McAfee" products ever installed?

    Do you have a third party firewall - or are you using the built-in Windows
    firewall?

    Do you ever run any antimalware applications? If so - which ones and when
    did you scan with them last (full scan, not quick)?

    At least then, you are not walking into a mechanics shop and saying, "My
    2006 vehicle doesn't run. It makes a clicking noise. How do I fix it?"

    Upgrading from one OS to another seldom fixes an issue (unless that upgrade
    is truly a clean installation - then the problem *may* go away if the issue
    was not hardware related.)

    No one here probably ever left you to have to come back to you. ;-)
     
    Shenan Stanley, Mar 13, 2010
    #67
  8. gene7851

    Jepsiba Guest

    Hello everyone.

    I had the same problem (80070490) with Windows Update on Vista 32 bits.
    I tried everything I could find on Microsoft and other forums, nothing
    really solved the problem, so what I did was download the updates directly
    from the Microsoft site by entering the update code on the search bar. It
    took me to the download page and I installed by myself all missing updates
    which would not install.
    Windows update is working fine since.
    I hope this helps.

    Cheers
    Jepsiba
     
    Jepsiba, Mar 23, 2010
    #68
  9. gene7851

    PCBILL Guest

    I think I have it all figured out....all the updates you get the 80070490
    error, look in your update history...you will see that they have already been
    installed , that is why you are getting the error
     
    PCBILL, Jun 1, 2010
    #69
  10. <bzzzzt> WRONG! Thank you, step down. Next?
     
    PA Bear [MS MVP], Jun 1, 2010
    #70
  11. gene7851

    gg Guest

     
    gg, Jun 7, 2010
    #71
  12. gene7851

    TCR2121 Guest

    Did this work in the end?

     
    TCR2121, Jun 16, 2010
    #72
  13. For the many affected that are scouring the Net for a solution to this
    problem there is hope! After much digging I found the "System Update
    Readiness Tool for Windows" (REF:
    http://support.microsoft.com/kb/947821/en-us). After installing this tool /
    update on a Vista SP1 x86 installation I was able to download the > 90
    updates available. Please note that the fix took some time to complete and I
    rebooted the affected machine before downloading and installing the delta
    updates.



    Hope this is helpful!

    Richard A. Schwartz

    Sr. Consultant, Avanade Inc.
     
    Richard A. Schwartz - Avanade, Jun 30, 2010
    #73
  14. gene7851

    Spacy Mike Guest

    I have been having trouble with several computers at work with various
    versions of .net updates. I spent all day on one user's pc. I had to use
    software from a link on Microsoft's site to force some of the version of .net
    to uninstall. Then I had to reinstall each .net version, one at a time, and
    then install numersous .net updates. This took several reboots.

    I think Microsoft should provide a partial refund of the purchase price
    since they sold us a defective product, or a good product that they made
    defective. If I took my vehicle into the shop, and they accidentally break my
    windshield while changing oil, they are liable for windshield repairs.

    I can imagine how frustrating, or impossible, for most people to have to
    deal with this. I would assume that there are millions of computers out in
    the world that will never ever get updated because of this fatal flaw. Some
    of the other important updates won't install until this flawed uninstallable
    update is successfully installed.
     
    Spacy Mike, Jul 2, 2010
    #74

  15. Not everyone has the .NET Framework issue. I don't have it nor have any of
    the machines I manage had it. Something changed some things on the
    computers in question and if it was something from Microsoft that everyone
    would get then why isn't everyone in the same boat?

    I have had to help people fix this - but in the end - it isn't an 'across
    the board' issue. I even freshly installed a computer the other day
    (starting with Windows XP Home Edition with SP3) and patched it using the
    windowsupdate web page with over 125 post-SP3 patches in large batches just
    to see if I could recreate the issues people have with doing the updates
    (not just these, mind you - others as well.) It patched with everything no
    problem and is running strong.

    So - while I feel your pain - it is your pain. Something changed on the
    machine in question (agreed) - but I think you are throwing the bame around
    just to feel better about doing what is obviously part of your job (IT
    support). Microsoft did not force .NET Framework 2.x/3.x/4.x on you/your
    computers nor did they decide what else was to be installed on the computers
    or in what order or who used it or the other configuration settings, etc.

    Your example assumes the employees of the 'the shop' broke your window while
    changing your oil in the standard manner and no vehicle changes were made
    they were unaware of and no third party entity was involved. If some third
    party came by and shot up the shop for whatever reason - the shop is not
    liable for your broken window. If a freak storm blew limbs around while
    your car was there and a linb crashed into your window - not the shops
    fault. If you modified your car with some third party parts and did not
    notify the shop of the changes (or just did not think it should matter) and
    the new pressure of the type of oil you chose made some part shoot off and
    the part landed miraculously on your windshield and broke it - not the shops
    responsibility. Your example isn't bad - but it is incomplete. ;-)
     
    Shenan Stanley, Jul 2, 2010
    #75
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.