Windows Update fails (KB2705219, KB2786400, KB2773072)

hsint · 11 Feb 2013

Let's see.

I printed your instructions & followed them. Found the hstaa folder at D drive and performed the XCOPY without errors (4 files copied)

After reboot I did a SFC /SCANNOW > Log attached (CBS.zip)

Then the interesting bit. Windows updates. Checking for updates shows the KB2705219 available. Trying to install it fails with the usual error. Running the MSU gives the same result.

I saw the CBS.log got a lot larger after running Windows Update (30MB instead of 600kB), so I zipped that and attached again (CBS2.zip)

I hope these logs tell you something cause they're abracadabra to me

NoelDP · 11 Feb 2013

The CBS log post-fix is clean :)
The one after Windows Update shows the following error....

Code:

 Line 3848: 2013-02-11 20:59:42, Error                 CBS    Failed to resolve package 'Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1' [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
 Line 3855: 2013-02-11 20:59:42, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

- again/still!

I wonder if perhaps the problem is that the control files are present, but the 'working files' are not?

Please open an Elevated Command Prompt, and run the following commands...

Code:

 
TAKEOWN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum
ICACLS C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum /grant Administrators:(F)
REN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum.old
TAKEOWN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat
ICACLS C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat /grant Administrators:(F)
REN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat.old

Then reboot and attempt installation using the msu file.

hsint · 11 Feb 2013

Hi Noel,

When I try to execute the first command I get

C:\Windows\system32>TAKEOWN C:\Windows\Servicing\Packages\Package_2_for_KB270521
9~31bf3856ad364e35~amd64~~6.1.1.1.mum
ERROR: Invalid argument/option - 'C:\Windows\Servicing\Packages\Package_2_for_KB
2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum'.
Type "TAKEOWN /?" for usage.

Maybe you missed the /F before the filename?

NoelDP · 11 Feb 2013

Well spotted! It's a common mistake of mine

Code:

TAKEOWN /f C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum /A
ICACLS C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum /grant Administrators:(F)
REN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum.old
TAKEOWN /f C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat /A
ICACLS C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat /grant Administrators:(F)
REN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat.old

hsint · 11 Feb 2013

Hehe don't think I spotted it before running the command

I only know cause I ran takeown /? after the error

I did first two commands, but when I do the rename I get Access is denied.

I think I understand what you are trying to do and the first two passed without error message. See below the

Code:

C:\Windows\system32>TAKEOWN /f C:\Windows\Servicing\Packages\Package_2_for_KB270
5219~31bf3856ad364e35~amd64~~6.1.1.1.mum /A

SUCCESS: The file (or folder): "C:\Windows\Servicing\Packages\Package_2_for_KB27
05219~31bf3856ad364e35~amd64~~6.1.1.1.mum" now owned by the administrators group
.

C:\Windows\system32>ICACLS C:\Windows\Servicing\Packages\Package_2_for_KB2705219
~31bf3856ad364e35~amd64~~6.1.1.1.mum /grant Administrators:(F)
processed file: C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31bf3856ad
364e35~amd64~~6.1.1.1.mum
Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>REN C:\Windows\Servicing\Packages\Package_2_for_KB2705219~31
bf3856ad364e35~amd64~~6.1.1.1.mum Package_2_for_KB2705219~31bf3856ad364e35~amd64
~~6.1.1.1.mum.old
Access is denied.

C:\Windows\system32>

Btw I think you made a mistake in the 2nd rename, as you are first taking ownership of the CAT file, and then renaming the MUM file to .cat.old. I Did not run lines 4-6 yet.

NoelDP · 11 Feb 2013

I thought I'd changed the extension! - oh well :)

I think the problem is that we don't have ownership of the Winsxs folder, and don't have permissions to add files to it (which is what we effectively are doing with the rename command) -

It doesn't actually matter - I've been doing some research on the error, and the conventional cure is a repair install (!) because the problem lies in the registry.

If you're willing (and have backups, in case things go wrong) then we can try and repair the registry.

If so, please run the following command, and compress and upload the resulting file.

Code:

 
REG EXPORT "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" %userprofile%\desktop\regnp.log

hsint · 11 Feb 2013

Sure. I run daily backups to my NAS, fully automatic, and I know from experience that these cover everything (because I needed them when my HD died in the computer before this one).

See attached logfile

NoelDP · 11 Feb 2013

The problem Key is (I think)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.2.0

However, because of the way installs work, we have to at least delete all the related subkeys in the registry

That means that we need to delete the following keys....

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_3_for_KB2705219~31bf3856ad364e35~amd64~~6.1.2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2705219_SP1~31bf3856ad364e35~amd64~~6.1.2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2705219~31bf3856ad364e35~amd64~~6.1.2.0

The problem is getting permissions on the keys to allow deletions.
I was hoping to use Subinacl - but it doesn't work in x64 systems

Unless you have a better option, then that means that we're reduced to manually editing the registry (which I always try to avoid!)

You'll need to find each of those subkeys, and then take ownership (right-click on the entry and select Permissions, then Owner) and then allow Full permissions to the Administrators group.
You can then delete the subkey itself.

Once done, reboot, and try using the msu to install the update.

hsint · 14 Feb 2013

Hi Noel,

Sorry for being silent so long. I was away from home for a few days on a business trip. Now back home so I'll try your instructions now. Manually editing registry files. Nice, back to my childhood

hsint · 14 Feb 2013

Well I tried to follow your instructions but either I do something wrong or ...

I looked up the first key you listed. Check
I made a backup of the key to delete by Exporting it.
I went to Permissions... > Advanced > Ownership and set the Administrators as owner.
Next I went to Permissions ... and checked the "Full control"checkbox for Administrators
Next I go to delete, but then I get an error message. See screenshot attached.

I hope this helps you spot what I did wrong.