Can't do any Windows 8 update (error code 800F081F)

Anonymous
2012-10-27T09:23:06+00:00

I just update my Windows 7 laptop to windows 8 pro and found that I couldn't install any update due to this error 800F081F. It seems that MS had a solution, "System Update Readiness Tool", for all other windows version from vista to server 2008; but anyone know any solution for windows 8?

Some attemps I did:

I've tried troubleshooting to fix Windows update automatically but it doesn't help (Funny thing is that when troubleshooting has complete it actually tells me "Potential Windows Update Database error detected 0x800f081f -- fixed");

I've tried a MS tool called "Fix it" but the problem is still there;

I even uninstalled my anti-virus software and use Windows Defender instead; I also tried to restart Windows Update services several times.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-11-19T01:36:18+00:00

Just wanted to share with anyone else who was having this issue what it was that I did to resolve it. First off some quick background, this is a brand new HP laptop so was no update over windows 7.

I first had issue updating due to a device issue with an installed HP codec that conflicted with a Windows Codec update, I resolved that and manually updated that single update. Then Windows update failed again. I tried doing the DSIM w/ Restorehealth option as suggested previously in this post, but to no avail.

Some more research led me to the following folder "C:\Windows\servicing\Packages" in this folder I did a quick search for some of the failing updates KB numbers.. (KB2727528 for example) and sure enough found the following...

Package_for_KB2727528~<blahblah>~6.2.1.0 cat and mum files

Package_1_for_KB2727528~<blahblah>~6.2.1.0 cat and mum files

Package_for_KB2727528_RTM~<blahblah>~6.2.1.0 cat and mum files

Using the following command (note that trying to remove the _1_ or _RTM results in a package not found!):

dism /online /NoRestart /remove-package /packagename:Package_for_KB2727528~<blahblah>~6.2.1.0

and recieved a 100% package removed! No way! Installed just that update and booyaah success, restarting it seemed to stall at 15% but then kept going after a few mins and success.

I then wrote out a batch file to execute the above command for any found package namefor anything that had a KB code in the the Windows Update list and viola all were removed. Windows update then completed successfully!

As my wife pointed out.. what do people who don't know computers/software as well as me do, and I told her they probably take them back for a refund, and she replied this is why people use Macs LOL! Probably true. I hope this helps someone else.

After 20+ years you'd think MS would've finally stopped releasing broken Windows software *sigh*

Doc.

Was this answer helpful?

7 people found this answer helpful.
0 comments

102 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-11-29T03:48:21+00:00

    A batch file is a .bat file that can be executed within a Command Prompt window. 

    I wrote one to do the work, here are the steps to create it.

    1. Create a new Text File on your windows desktop.
    2. Rename the Text File to MSUpdateCleanup.BAT, click YES when the dialog warns you that changing the file name could make the file unusable.
    3. Right click on the BAT File (you should notice that it's icon changed!) and select EDIT.
    4. Paste in the following lines:

    SET ARG=%1

    FOR /F "usebackq delims=" %%A IN (dir /B C:\Windows\servicing\packages\Package_for_%ARG%~*.cat) do SET FOUNDPKG=%%A

    SET PKGNAME=%FOUNDPKG:~0,-4%

    DISM /online /NoRestart /remove-package /packagename:%PKGNAME%

    1. Save the File and Copy and Paste it into C:\
    2. Put mouse in right hand corner and click on the Search Icon (not sure what this bar is called)
    3. Type in COMMAND, you'll see a Command Prompt icon as the result.
    4. Right click the Command Icon and at the bottom select RUN as ADMINISTRATOR.
    5. In the Command Prompt type in C: and hit Enter
    6. In the Command Prompt type in CD \ and hit Enter
    7. Type in MSUpdateCleanup <And whatever KB###### that is failing> and hit Enter
    8. Repeat step 11 for the KB numbers for each Windows Update.
    9. Do the Windows Update.

    Hope that helps you and anyone else who want's an easier way to do this ;)

    Doc

    It worked!!!!  Thank you so much.  I feel like I should send you some cash after all the different things I tried.  I was about to give up until I stumbled upon your post.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-11-28T23:14:41+00:00

    Doc,

    You're a saint!

    It worked on my win7 upgrade as well.

    You turned a dark, frustrating day (and a half) completely around.

    Thank you, thank you, thank you for sharing.

    And the batch file is a great idea.

    If I need it.

    Did I say if ??

    Who am I kidding? I'm upgrading 2 dozen machines. 

    The batch file is going onto a thumbdrive now, to be edited and run as needed. 

    Thanks again, so very much!

    g

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-11-28T15:50:28+00:00

    You sir, are a genius, 

    2 days trying to update from 8 to 8Pro

    Thanks!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-27T10:13:19+00:00

    I've noticed that all of the failed updates which this method from DocSlax fixes (thank you btw!) have "amd64" in the filename while my machine is an Intel machine I built. Maybe the reason it fails is related to this?

    I doubt it, I believe Microsoft have now adopted the convention, like many other software companies, of using 'amd64' to describe the generic amd64/Intel-64 (i.e. compatible with both) code that they used to describe as x64 (as distinct from x86 (IA-32) and IA-64). Strictly speaking I suppose they should label it amd64_Intel64 but they seem to have settled on amd64 which to me seems as wrong as x64 was. x64 described neither company's architecture and amd64 describes just one of them.

    Was this answer helpful?

    0 comments