Tech Support Forum banner
Status
Not open for further replies.
1 - 7 of 7 Posts

·
Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
I am working on a client's laptop, and have been unable to update to Service Pack 1. Stand-alone manual installer results in error 0x800f081e

I have also run the System Update Readiness Tool, and this is the most recent log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-12-23 17:24

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS Registry Error 0x80070002 Package_for_KB2695962_SP1~31bf3856ad364e35~amd64~~6.1.1.0 failed to get Visibility

Checking Component Store

Summary:
Seconds executed: 531
Found 1 errors
CBS Registry Error Total count: 1

 

·
Global Moderator
Joined
·
42,339 Posts
Go to Start/Search and type appwiz.cpl and press enter. On the Left Panel, click on View Installed Updates. To see what updates you have installed. Sp1 requires .Net Framework 3.5 Be installed first.
Check to make sure you have done all of your Windows Updates, including the Optional ones.
 

·
Registered
Joined
·
4 Posts
Discussion Starter · #3 ·
The .NET 3.5 installer keeps crashing on me for some reason. I did a little digging and components of 3.5.1 (already installed) had been turned off. I went into Turn Windows On or Off and made sure it was turned on.

However, my Windows Update is now showing the same updates that have already been installed. There are two important updates. One is SP1, obviously. The other is KB3004469 (Update for Windows 7 for 64-bit Systems).

Everytime the update runs, it says it gets installed successfully. But when I check for updates again, 3004469 shows up again.
 

·
Registered
Joined
·
4 Posts
Discussion Starter · #5 ·
Windows Update Troubleshooter results with:

Windows Update error 0x80070057 (2016-12-24-T-05_42_43P) - Not Fixed
Problems installing recent updates - Not Fixed
 

·
Registered
Joined
·
4 Posts
Discussion Starter · #7 ·
Yes, I did. And ran WU Troubleshooter afterwards as well. Troubleshooter resulted in the above error not being fixed.
 
1 - 7 of 7 Posts
Status
Not open for further replies.
Top