Member Avatar for Nanci252

I am struggling with a Gateway laptop running Windows Vista Home Premium, SP1. I have tried to fix the problem of Windows Update error 80070490 - with the System readiness tool, the Windows Update Fix-it tool, done all the requested restarts and retries, and nothing is working.
Right now I am doing a backup so that I can try to restore from the factory partition (no Vista cd w/ laptop) and see if re-doing the OS helps.
Fully cleaned and free of virus', had been running Norton Anti-virus as full time protection with firewall, and other security center items all in the On mode.
this problem appears to have begun in 2011 on a patch tuesday, but customer only recently brought it to me for virus removal.
Help ? any further ideas, or tricks I might have missed.

  • 3 Contributors
  • 3 Replies
  • 494 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Nanci252

Dani AI

Generated

A short, practical add-on to the thread: ’s machine was ultimately restored with the factory recovery option, which is a valid last-resort fix once user data is safely backed up. For technicians who want non‑destructive steps to try first, and to help anyone landing here later, a compact checklist and safe commands are provided below.

Common non‑destructive checks and fixes (in roughly the order to try)

  • Confirm the system clock is synchronized with an Internet time source (simple, common cause noted by ).
  • Inspect the update logs (WindowsUpdate.log and the CBS logs) for specific error entries as suggested by ; those logs guide targeted fixes.
  • Ensure key services are running: Windows Update, Background Intelligent Transfer Service (BITS), Cryptographic Services and Windows Installer.
  • Run System File Checker to catch corrupted system files: sfc /scannow.
  • Reset the Update cache and catalog folders safely by stopping services, renaming the folders, then restarting services. Example commands (run from an elevated command prompt):
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Additional notes and cautions

  • Create a full backup or system image and export any registry keys before making registry changes. Editing the registry without a backup is risky.
  • If the non‑destructive steps fail, the recovery partition (used successfully in this thread) is a reasonable next step when time is limited — but prefer a full image backup first so a repeatable, restorable baseline exists.
  • After recovery or repair, make a system image and enable a regular update/check routine so a single failure does not require full rework.

Recommended Answers

All 3 Replies

Member Avatar for PhilliePhan

Hi Nanci,

What did the log say after you ran the System Readiness Tool?
-- C:\Logs\CBS

If that doesn't give you a lead on why the fix failed, I'd just go ahead with the Recovery Partition option - a repair install may not fix the issue and, since you've backed up the customer's data, you may as well save more headaches and just go with the destructive recovery.

Just my $.02

Cheers :)
PP

Edited by PhilliePhan
Member Avatar for fobos

I had the same problem and it turned out that the computers time was not in sync with the server time. After it my computer synced with microsoft's time, windows update worked.

Member Avatar for Nanci252

Close this post, I found out the Recovery partition with 'save user data' worked miracles. It was a corrupt area in the software distribution key in registry. Got everything back and working and all updates running smoothly now.
Thank you.

ps. the system readiness tool reported No problems, as did the WU 'fix it' center tool. She's running fine now.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.