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

Anonymous

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.

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

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.

0 comments

102 additional answers

Anonymous

2012-11-07T05:01:24+00:00

Same problems, same obstacles.

The entire Windows 8 experience has been terribly disappointing.

I can't believe that there has only been one reply here from Microsoft, with a suggested fix that has proven ineffective. Then radio silence.

But what I find absolutely appalling are the dozens of troubleshooting pages that provide countless instructions for the USER to waste his/her time trying to coax a lackluster system into doing its most fundamental jobs. Wipe your drivers, issue commands and download ineffectual "maybe" fix-it utilities, spend all day on the phone, spend all night on the internet... and do all these things in order to compensate for poor production and lazy or non-existent (or costly) technical support on the part of Microsoft. When a company's primary response in the face of their own poor performance is to shift the burden onto its end users, it signifies an irreversible breakdown, the center can't hold when the foundation disappears.

I have been using Macs at work for a decade, but have been a steadfast PC user at home for longer. I'm changing my mind.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-04T16:46:33+00:00

Tried these solutions, no luck. Even your tech support doesn't know what's going on. I thought you would have spent a fair amount of time testing 7 to 8 upgrades.

Any ideas besides scanhealth and restorehealth. I tried uninstalling my AV.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-04T16:01:41+00:00

o    DISM.exe /Online /Cleanup-image /Scanhealth

o    DISM.exe /Online /Cleanup-image /Restorehealth

No errors found.

DISM.LOG:

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

Checking System Update Readiness.

Summary:

Operation: Detect and Repair

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption:    0

    CBS Manifest Corruption:    0

    CBS Metadata Corruption:    0

    CSI Manifest Corruption:    0

    CSI Metadata Corruption:    0

    CSI Payload Corruption:    0

Total Repaired Corruption:    0

    CBS Manifest Repaired:    0

    CSI Manifest Repaired:    0

    CSI Payload Repaired:    0

    CSI Store Metadata refreshed:    True

Total Operation Time: 461 seconds.

After /restorehealth nothing changed KB2756872 fails at 32.9%, KB 2761094 fails at 31.1%.

DISM.LOG:

2012-11-04 22:41:20, Warning               DISM   DISM Provider Store: PID=6444 TID=2176 Failed to Load the provider: C:\Users\685F~1\AppData\Local\Temp\C1DF4766-A29B-4965-80CD-09B897E3B1EF\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2012-11-04 22:41:21, Warning               DISM   DISM Provider Store: PID=6444 TID=5420 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)

2012-11-04 22:41:21, Warning               DISM   DISM Provider Store: PID=6444 TID=5420 Failed to Load the provider: C:\Users\685F~1\AppData\Local\Temp\C1DF4766-A29B-4965-80CD-09B897E3B1EF\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

2012-11-04 22:41:21, Warning               DISM   DISM Provider Store: PID=6444 TID=5420 Failed to Load the provider: C:\Users\685F~1\AppData\Local\Temp\C1DF4766-A29B-4965-80CD-09B897E3B1EF\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2012-11-04 22:45:04, Error                 DISM   DISM Package Manager: PID=6444 TID=32 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2012-11-04 22:45:04, Error                 DISM   DISM Package Manager: PID=6444 TID=32 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2012-11-04 22:45:04, Error                 DISM   DISM Package Manager: PID=6444 TID=32 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f081f)

2012-11-04 22:45:04, Error                 DISM   DISM Package Manager: PID=6444 TID=32 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2012-11-04 22:45:15, Error                 DISM   DISM Package Manager: PID=6444 TID=32 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2012-11-04 22:45:15, Error                 DISM   DISM Package Manager: PID=6444 TID=32 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2012-11-04 22:45:15, Error                 DISM   DISM Package Manager: PID=6444 TID=32 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f081f)

2012-11-04 22:45:15, Error                 DISM   DISM Package Manager: PID=6444 TID=32 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2012-11-04 22:45:15, Error                 DISM   DISM Package Manager: PID=6444 TID=32 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

CBS.LOG:

2012-11-04 22:44:50, Error                 CSI    0000001b (F) STATUS_OBJECT_NAME_NOT_FOUND #7897696# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0xdb4ee5ea80->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[102]"??\C:\Windows\CbsTemp\30259874_3602525248\Package_4_for_KB2756872~31bf3856ad364e35~amd64~~6.2.1.0.cat"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xdb4ee5eb20, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)

[gle=0xd0000034]

2012-11-04 22:44:50, Error                 CSI    0000001c@2012/11/4:15:44:50.796 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2155): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)

[gle=0x80004005]

I can upload full CBS.LOG somewhere if needed. It's pretty huge.
Was this answer helpful?

0 comments No comments
Anonymous

2012-11-04T12:25:09+00:00

Hello,

I followed the steps mentioned, but with no success. I still get the same two error codes on trying to install Windows updates:

800F081F

8007078A

See command line output of DISM tool below. Looks like the responses of the tool contradict each other...

Any further suggestions?

Thanks...

Tool zur Imageverwaltung für die Bereitstellung

Version: 6.2.9200.16384

Abbildversion: 6.2.9200.16384

[==========================100.0%==========================]

Es wurde keine Komponentenspeicherbeschädigung erkannt.

Der Vorgang wurde erfolgreich beendet.

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

Tool zur Imageverwaltung für die Bereitstellung

Version: 6.2.9200.16384

Abbildversion: 6.2.9200.16384

[==========================100.0%==========================]

Der Wiederherstellungsvorgang wurde abgeschlossen. Die Beschädigung des Komponen

tenspeichers wurde repariert.

Der Vorgang wurde erfolgreich beendet.
Was this answer helpful?

0 comments No comments