[SOLVED] Error Code 800F0831 when installing KB8000850 on Server 2012 R2

Krypty123 · May 28, 2016

As title states, the error I'm getting on a machine of ours is proving to be quite the annoyance. sfc/dism/sfcfix have been run, but I end up in the same spot regardless.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-05-25 15:02:19.475
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-05-25 15:40:44.024
----------------------EOF-----------------------

CBS logs should be coming shortly... (I used the SFCFixScript.txt method at about 6:30pm CST)

Krypty123 · May 29, 2016

I didn't see the script auto-upload the CBS files, so I tried manually uploading them now since they are only 12MB in size. That said, when I use Firefox or IE, it doesn't seem to be actually uploading the files (nor even putting them in the window to drag/attach)

Krypty123 · May 30, 2016

Just realized my zip file was barely over the limit... anyway, I uploaded the CBS logs here: Mega File Upload - CBS.zip

BrianDrab · Jun 1, 2016

Hi and welcome to Sysnative. Please start with the following.

Code:

2016-05-30 11:36:27, Error                 CBS    Failed to resolve package 'Package_35_for_KB3060716~31bf3856ad364e35~amd64~~6.3.1.0' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]

Let's take a different approach. Please do the following.

Remove Update Manually
1. Right-click on the Start

button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
wusa /uninstall /KB:3060716

3. Let me know if it says it was successful or if there are any errors.

Krypty123 · Jun 1, 2016

Interestingly enough (or maybe you're potentially expecting this?) - it says KB3060716 is not installed. Should I download/install that next?

BrianDrab · Jun 1, 2016

I thought that might be the case. Sure go ahead and try to download/install from the link below. Likely won't work but let me know.

Download Security Update for Windows Server 212 R2 (KB3

716) from Official Microsoft Download Center

Krypty123 · Jun 1, 2016

Downloaded the file, attempted the install, but it comes back that "The update is not applicable to your computer."

BrianDrab · Jun 1, 2016

Yup. Dealt with this many times. This could be an issue with the files related to this or more likely the registry which is much harder to fix but doable. Let's first check the files.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Krypty123 · Jun 1, 2016

As requested:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-01 20:19:17.472
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\krypty123\Desktop\SFCScript.txt [0]

FileScan:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-06-01 20:19:53.829
Script hash: d/aA4N0YKvLovljuA4D1l1YqD/gxl0WtrOyfbQEVeic=
----------------------EOF-----------------------

BrianDrab · Jun 1, 2016

Registry it is. We need to clean some remnants out that don't belong there. Easiest way is for you to send me your COMPONENTS hive. Please do the following. Since this is a server and you may not be able to reboot, if you can't retrieve the COMPONENTS hive using the 1st option below then go to the 2nd option.

Retrieve Components Hive - 1st option
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.

Retrieve Components Hive - 2nd option

Please download the Freeware RegBak from here: Acelogix Software - Download products
You will find it at the bottom of the page that the link brings you to.
Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
Click the New Backup button. Accept the defaults and simply click Start.
When it says Finished successfully, click the Close button.
This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
Now right click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
You can close any open windows you have as well as the RegBack program now.

Krypty123 · Jun 1, 2016

Luckily I can reboot this server at will since we've got some redundancy built in out network, so here's the file as requested: Download COMPONENTS.zip from Sendspace.com - send big files the easy way

BrianDrab · Jun 1, 2016

Excellent. Let's start with the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Krypty123 · Jun 1, 2016

Thanks for the quick responses by the way! As requested:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-01 20:55:28.283
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\richard.loughran\Desktop\SFCScript.txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0dbab7b2346..bef87f27460_31bf3856ad364e35_6.3.9600.17933_9ed7850f9a44fd12.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1454d3a1312..47600cc7be8_31bf3856ad364e35_6.3.9600.17933_bada6baabef4806c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3061c090799..f37cb50db00_31bf3856ad364e35_6.3.9600.17933_e9b8c6f045d202e4.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\40528e437fa..ea7d381079c_31bf3856ad364e35_6.3.9600.17933_13c5ab187eb46cf2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\51a1f867dc0..d6727e5ec35_31bf3856ad364e35_6.3.9600.17933_6d830f029d67c007.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\65c1db6ef2e..a048d4b664c_31bf3856ad364e35_6.3.9600.17933_7800d1d8b1a8e5a8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\80c69390cb9..5915f756619_31bf3856ad364e35_6.3.9600.17933_43535aca5d2bcdd7.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8773001a2a5..87192626030_31bf3856ad364e35_6.3.9600.17933_d489baf7d167a600.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9dbd4a8d8fe..51122eb5628_31bf3856ad364e35_6.3.9600.17933_b7e95502da67eddb.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a2321bbc2fe..4555dda18e3_31bf3856ad364e35_6.3.9600.17933_a1be438e209c32e6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\aa30e492941..d148b2e24a7_31bf3856ad364e35_6.3.9600.17933_145cae04fe2f0d44.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ee0ede29638..c664fd77850_31bf3856ad364e35_6.3.9600.17933_b3fc47c3fc9be757.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0dbab7b2346..bef87f27460_31bf3856ad364e35_6.3.9600.17933_9ed7850f9a44fd12.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1454d3a1312..47600cc7be8_31bf3856ad364e35_6.3.9600.17933_bada6baabef4806c.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3061c090799..f37cb50db00_31bf3856ad364e35_6.3.9600.17933_e9b8c6f045d202e4.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\40528e437fa..ea7d381079c_31bf3856ad364e35_6.3.9600.17933_13c5ab187eb46cf2.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\51a1f867dc0..d6727e5ec35_31bf3856ad364e35_6.3.9600.17933_6d830f029d67c007.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\65c1db6ef2e..a048d4b664c_31bf3856ad364e35_6.3.9600.17933_7800d1d8b1a8e5a8.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\80c69390cb9..5915f756619_31bf3856ad364e35_6.3.9600.17933_43535aca5d2bcdd7.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8773001a2a5..87192626030_31bf3856ad364e35_6.3.9600.17933_d489baf7d167a600.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9dbd4a8d8fe..51122eb5628_31bf3856ad364e35_6.3.9600.17933_b7e95502da67eddb.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a2321bbc2fe..4555dda18e3_31bf3856ad364e35_6.3.9600.17933_a1be438e209c32e6.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\aa30e492941..d148b2e24a7_31bf3856ad364e35_6.3.9600.17933_145cae04fe2f0d44.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ee0ede29638..c664fd77850_31bf3856ad364e35_6.3.9600.17933_b3fc47c3fc9be757.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0dbab7b2346..bef87f27460_31bf3856ad364e35_6.3.9600.17933_9ed7850f9a44fd12 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1454d3a1312..47600cc7be8_31bf3856ad364e35_6.3.9600.17933_bada6baabef4806c with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3061c090799..f37cb50db00_31bf3856ad364e35_6.3.9600.17933_e9b8c6f045d202e4 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\40528e437fa..ea7d381079c_31bf3856ad364e35_6.3.9600.17933_13c5ab187eb46cf2 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\51a1f867dc0..d6727e5ec35_31bf3856ad364e35_6.3.9600.17933_6d830f029d67c007 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\65c1db6ef2e..a048d4b664c_31bf3856ad364e35_6.3.9600.17933_7800d1d8b1a8e5a8 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\80c69390cb9..5915f756619_31bf3856ad364e35_6.3.9600.17933_43535aca5d2bcdd7 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8773001a2a5..87192626030_31bf3856ad364e35_6.3.9600.17933_d489baf7d167a600 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9dbd4a8d8fe..51122eb5628_31bf3856ad364e35_6.3.9600.17933_b7e95502da67eddb with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a2321bbc2fe..4555dda18e3_31bf3856ad364e35_6.3.9600.17933_a1be438e209c32e6 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\aa30e492941..d148b2e24a7_31bf3856ad364e35_6.3.9600.17933_145cae04fe2f0d44 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ee0ede29638..c664fd77850_31bf3856ad364e35_6.3.9600.17933_b3fc47c3fc9be757 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2016-06-01 20:55:29.314
Script hash: nPgvl92RpO5qiLU7Sz/ymvZ6r4a2CniAGuQVf+ZAZFc=
----------------------EOF-----------------------

BrianDrab · Jun 1, 2016

No problem. It likely won't work yet but please attempt to install the update that has been failing. If it fails to install, please zip up and attach the c:\windows\logs\cbs\cbs.log

I'm going to turn in for the night and will pick this back up tomorrow.

Krypty123 · Jun 1, 2016

No worries sir! With your tremendous help, the update has installed. I'll be looking at donating when I get into the office tomorrow.

Thank you!

BrianDrab · Jun 2, 2016

Excellent news. Thanks for letting me know.

Search

Search

[SOLVED] Error Code 800F0831 when installing KB8000850 on Server 2012 R2

Krypty123

Member

Krypty123

Member

Krypty123

Member

BrianDrab

Emeritus

Krypty123

Member

BrianDrab

Emeritus

Krypty123

Member

BrianDrab

Emeritus

Attachments

Krypty123

Member

BrianDrab

Emeritus

Krypty123

Member

BrianDrab

Emeritus

Attachments

Krypty123

Member

BrianDrab

Emeritus

Krypty123

Member

BrianDrab

Emeritus