Windows 8.1 Media Center Pack installer insists on installing rollup update KB3000850 even though it is already installed

Using "Add Feature" I paid for and downloaded Media Center pack on Windows 8.1 Pro x64.

It goes through the upgrade process after reboot but fails after reaching 96% then rolls back the upgrade. Looking in the event viewer I see this message:

"Installation Failure: Windows failed to install the following update with error 0x800F0922: Update for Windows 8.1 for x64-based Systems (KB3000850)."

Why is this feature installation process attempts to install an update that I already have?

Note that the stated update was integrated into the Windows 8.1 Pro install ISO. The update history shows that it was installed 

This Windows 8.1 pro has this install/upgrade history:

1. Started with Windows 7 Ultimate on which Media Center was configured and functional.

2. I upgraded to Windows 8 Pro selecting the option to keep applications and personal data.

3. Immediately after the upgrade is complete, I upgraded to Windows 8.1 pro using MSDN ISO "en_windows_8_1_pro_vl_x64_dvd_2971948.iso" that has rollup update 1 slipstreamed into it.

4. Installed all Windows 8.1 updates available as of last week.

5. Selected "Add features to Windows 8.1" and went through the process of paying for and downloading Media Center Pack.

6. System rebooted to apply the update/upgrade but it fails as I described above.

I searched through the community posts as well as other forums and could not find anything specific to this.

I already went through the following steps but still could not resolve this issue. Any help would be greatly appreciated.

Method 1:

Step 1: Repair .Net Framework

The error code 0x800f0922 is related to issues with .net framework. It is possible that this issue could be a result of corrupt .net framework. Lets try to repair this using the following article:


Microsoft .NET Framework Repair Tool

<link to tool removed>

Proceed with step 2


Step 2: DISM Tool

DISM tool can be used to repair the windows files which may be a possible cause of this issue. This will also help in resolving other issues which we found in the log file of SFC scan. Please use the steps below to run DISM tool.

  1. Press Windows key + X.
  2. Click Command prompt (admin).
  3. Run the following commands:
    "DISM.exe /Online /Cleanup-image /Scanhealth"
    "DISM.exe /Online /Cleanup-image /Restorehealth
  4. Run the SFC scan again using the steps provided earlier.
  5. Try Enabling WMC features now.

If your Issue is still not resolved, please try Method 2.

Method 2

  1. Please visit the following links and download these updates from the Microsoft download center:
    <links to download IDs 43919 and 43926>
  1. Press Windows key + R.
  2. Type appwiz.cpl and hit Enter.
  3. On the left pane, click View installed updates.
  4. Locate and uninstall KB2966826 and KB2966828. These updates are security updates for .Net Framework which could be blocking your WMC features.
  5. Enable .Net Framework (if disabled) and then the WMC features.
  6. If this resolves the issue, reinstall the KB2966826 and KB2966828 which was downloaded during step 1.

June 18th, 2015 3:03am

Hi

KB3000850 belongs to November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 and it might be prerequisite updates for many newer update package. update package corruption might cause this kind of symptoms.

Please try following instructions as mentioned below

You receive a 0x800f0922 or 0x80070005 error message when you try to install this update

Symptoms

Assume that you have either of the following configurations

You have a Windows Server 2012 R2 server/Windows 8.1 that is running on hardware that has UEFI that has Secure Boot enabled.

You have a Hyper-V host that is running, and you are running a Generation 2 virtual machine guest that uses UEFI firmware support and that has the Secure Boot option enabled.

In these configurations, update 3000850 may not be installed, and you receive a 0x800f0922 or 0x80070005 error message.

Solution

To resolve this problem, follow these steps: 1.Install the updated servicing stack update 2975061, and then restart the computer.

https://support.microsoft.com/en-us/kb/3000850

 

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
June 21st, 2015 10:38pm

Thanks D. Wu for your reply.

I am not trying to install KB3000850 update. Rather, it is already installed when I upgraded from 8.0 to 8.1.

The installation DVD already had that update rolled into it. What I need help with is how to get WMC installed?
It keeps failing and rolls back the installation. Looking through the logs, it appears that it insists on installing that update even though it is already installed.

June 22nd, 2015 1:32am

Hi,

Yes, I understand your issue, as mentioned in my last reply, KB3000850 belongs to November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 and it might be prerequisite updates for many newer update/package. If Windows think this update have not been installed. It will download and install it for installation of newer package. Update package corruption might cause this kind of symptoms. You need repair this update or remove/install it again then check the issue.

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 5:56am

Thanks again for your response Deason!

I am unable to remove this update. When I select it, there is no "uninstall" or "repair" options available.

I attempted to insert a screenshot here but I get an error that I cannot do that until my email address has been verified.

Could this be due to the fact that I did not install this update manually and it was included with the Windows 8.1 installation medium?

Thanks.

June 26th, 2015 1:30am

Hi,

According to your decryption. This update should be imaged to your system so when system installed, it is already there, if this package imaged right, it is no different from installing it manually. In the other hand, if the system image is corrupted, the issue occurs, also registry cleaner software might also cause this kind of issue.

Try the Windows update reset steps as mentioned here, I already checked the registry edit file and it is safe to run.

http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to back up/restore it if a problem occurs.

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 9:37pm

Hello Darsh,

When you add Media Center to the installation , you are adding files to Windows.

Some of those files would have been updated when KB3000850 update was applied.

Since the media center files were not present the updated files from KB3000850 were not installed at that time.

Now that you are installing Media Center the updated files are needed so you are prompted to install KB3000850 again to get the files that need updating so your media center files are in sync with the rest of the OS.

June 29th, 2015 10:07pm

Unfortunately, this still did not help. I tried all 3 approaches but I still get the same outcome.

I think I will have to wait for Windows 10 to be released and then attempt this after upgrading.

Free Windows Admin Tool Kit Click here and download it now
July 9th, 2015 12:14pm

Thanks Darrell! This makes perfect sense. However, I am still unable to proceed as the attempt to install the needed files still fails. I would like to post some of my logs here but I am unable to do so since my forum account is new and I keep getting an error that my email address has not been verified yet. Can someone help me get my account validated?
July 9th, 2015 12:16pm

Why is this feature installation process attempts to install an update that I already have?

I had the same symptom with an earlier "cumulative update" (June) even after KB3000850 had been successfully installed.  However, I also had a firmware update which apparently had been doing the same thing month after month.  I finally called Surface Support who made the suggestion to allow full Automatic updating.  I had only been allowing automatic downloading and notification.  When I did that the flood gates opened:  turned out that there were many other updates which were "pending completion" and not fully installed (even though there had definitely been reboots when requested).  Since then I have left automatic updates on and tried to remember to check periodically if the same thing is happening.  It's really too much of a pain to try to figure out for sure but I think it may actually be helping avoid the symptom.

Free Windows Admin Tool Kit Click here and download it now
July 10th, 2015 12:14pm

Are you getting the reverting changes when you restart your machine after the updates?
July 11th, 2015 4:26pm

Yes, I am after it reaches 100% applying changes/upgrade.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2015 4:59pm

I tried that but still no improvement.
July 11th, 2015 5:01pm

Resolution 1

  1. Turn off secure boot
  2. Re run updates see if they go thru
  3. Turn on secureboot

Resolution 2

             

  1. Check to see if these .inf files exist in c:\windows\inf  folder

wiaek002.inf
prnekcl2.inf

2. If they do - Create the following two folders:
C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b
C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20
Find the two files below in the \Windows\inf folder and copy them to their respective folders above

3. Run the updates

Resolution 3

             

  1. Check the following directories exist

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessibility
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools

If they do not exist create them.

2. Re run updates

             




  • Proposed as answer by aw00t 10 hours 22 minutes ago
  • Unproposed as answer by aw00t 10 hours 22 minutes ago
  • Edited by aw00t 10 hours 20 minutes ago
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2015 5:02pm

I tried that but still no improvement.

This in response to my post?
July 11th, 2015 6:18pm

No, that was for an earlier post. I haven't tried your suggestions yet.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2015 6:40pm

Yes, I am after it reaches 100% applying changes/upgrade.
  • Edited by Darsh in USA Saturday, July 11, 2015 8:59 PM Typo
July 11th, 2015 8:56pm

Resolution 1

  1. Turn off secure boot
  2. Re run updates see if they go thru
  3. Turn on secureboot

Resolution 2

             

  1. Check to see if these .inf files exist in c:\windows\inf  folder

wiaek002.inf
prnekcl2.inf

2. If they do - Create the following two folders:
C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b
C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20
Find the two files below in the \Windows\inf folder and copy them to their respective folders above

3. Run the updates

Resolution 3

             

  1. Check the following directories exist

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessibility
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools

If they do not exist create them.

2. Re run updates

             




  • Proposed as answer by aw00t Saturday, July 11, 2015 8:59 PM
  • Unproposed as answer by aw00t Saturday, July 11, 2015 8:59 PM
  • Edited by aw00t Saturday, July 11, 2015 9:01 PM
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2015 8:59pm

Option 1:
I don't have UEFI BIOS and "safe boot" is not an option available in the system BIOS.

Option 2
listed directories did not exist. I created them and copied each inf file to its corresponding directory. However, attempt to install the feature (WMC) still fails in the same fashion as before. i.e. Feature installation reaches 100% then I get "update failure" then backs out the changes.

Option 3:
Creating the 3 proposed directories via the Windows Explorer just returns without errors but the directories do not show in the listing. Using the command line (Admin), I am able to see the directories. which already contain files. I noticed that in Windows Explorer, all 3 directories are listed under the "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Accessory" directory.

Is "Windows Accessories" a symlink to "Accessories?

Anyhow, I attempted to install the feature but still got the same errors.

I think if I can provide the CBS.log and DISM.log you may be able to see the actual failure mode. However, I am unable to do that since my account on this forum has not  been verified yet. Who can help me get my account verified?

Thank you all for your attempts to help me!

July 11th, 2015 11:09pm

I think if I can provide the CBS.log and DISM.log you may be able to see the actual failure mode.

You could upload it to your OneDrive in a publicly accessible folder and then post the URL (not as a link if necessary).

BTW I made some notes about my related symptom with the June cumulative update.  WindowsUpdate.log had wrapped for me otherwise it could have provided clues about why the update was being reoffered.  Unfortunately, when we request verbose logging it wraps quite quickly.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/kb2962409-june-rollup-offered-again-while-november/0d7caab1-fb08-4cc9-b8ed-8baef331c2e3?page=1

Free Windows Admin Tool Kit Click here and download it now
July 11th, 2015 11:51pm

I tried that but still no improvement.


This in response to my post?

@ aw00t

Are you not using the Threaded view too?   <eg>

I just realized that this was actually a reply to me (I think).  Note that we can use View Source to find the "tried that" and then use the "parent" MessageId to go back to find out what is the probable message being replied to (and try to infer what "that" might mean).

Things would be so much easier if there was just a simple toggle from Unthreaded to Threaded.  Otherwise, I won't go into My Settings as long as there is still a risk of losing the HTML in my "signature". 

July 12th, 2015 12:04am

Thank you all again.

I posted a zip file that includes:
CBS.log
DISM.log
WindowsUpdate.log

at:
http ://1drv.ms/1K1t68u

(please remove the space before the colon above as I am not allowed to post URLs.

To reduce log noise, I collected these logs after a failed attempt. I had renamed CBS and DISM logs prior to the latest failed attempt. I truncated WindowsUpdate.log file prior to the first event generated by the latest failed attempt.

Thanks again!

Free Windows Admin Tool Kit Click here and download it now
July 12th, 2015 1:17am

I tried that but still no improvement.


This in response to my post?

@ aw00t

Are you not using the Threaded view too?   <eg>

I just realized that this was actually a reply to me (I think).  Note that we can use View Source to find the "tried that" and then use the "parent" MessageId to go back to find out what is the probable message being replied to (and try to infer what "that" might mean).

Things would be so much easier if there was just a simple toggle from Unthreaded to Threaded.  Otherwise, I won't go into My Settings as long as there is still a risk of losing the HTML in my "signature".

July 12th, 2015 1:28am

zip file that includes:
CBS.log
DISM.log
WindowsUpdate.log

The WindowsUpdate.log may show a problem.  Do you have any recollection about this event?   Start at line 250.

2015-07-11	21:39:22:470	1144	2224	Shutdwn	user declined update at shutdown

That could be the same kind of symptom that I must have been getting while I had Automatic Updates set to Download and Notify but then apparently was not getting enough finalizing of them done during a reboot.

Unfortunately, the CBS.log starts after that (at 21:42).  I think it may be showing problems too but for a different symptom.  I don't know what they would mean.  I would be running ProcMon to supplement them.

However, also at that time there is another clue in the WU log

2015-07-11	21:42:21:233	1168	dd8	Agent	  * Found 1 persisted download calls to restore

Looks like a loop?   <eg>

Free Windows Admin Tool Kit Click here and download it now
July 12th, 2015 12:10pm

Thanks Robert!

I was not doing anything at that time. As for the "Found 1 persisted .." message, I always see it in all attempts.
Could it be referring to the WMC download that I am trying to install?

I have Logmein agent running on this system which I noticed logs to WindowsUpdate.log when it tries to check for updates. I disabled it and repeated the process. It still failed in the same fashion.

I posted the latest set of logs including CBS (persisted log) which shows more details from the same period of time. The logs are zipped into "logs2.zip" which I placed at http ://1drv.ms/1K1t68u

I hope it has more helpful details.

July 12th, 2015 4:42pm

3. Immediately after the upgrade is complete, I upgraded to Windows 8.1 pro using MSDN ISO "en_windows_8_1_pro_vl_x64_dvd_2971948.iso" that has rollup update 1 slipstreamed into it.

I wonder what would have happened if you had started from this instead:

File Name: en_windows_8.1_enterprise_with_update_x64_dvd_6054382.iso

("Includes November 2014 update roll up")

<eg>

Also, what is the consequence of that "_VL_" in the one that you used?

BTW nothing is jumping out at me in your latest doc's but I may have another look at them

Free Windows Admin Tool Kit Click here and download it now
July 13th, 2015 6:45pm

To check if I have Volume License, I ran:

Slmgr.vbs /dli

which returned:

Name: Windows, Professional edition
Description: Windows Operating System, RETAIL channel
License Status: Licensed

This means that I am not using Volume License.

July 14th, 2015 12:02am

not using Volume License.

The CBS Persist log has something interesting in it at line 20536 (found while searching for the WMC  "session Id")

2015-07-12 12:49:24, Info                  CBS    Exec: Client forces reboot on session: 30457051_2904789849
2015-07-12 12:49:24, Info                  CBS    Exec: Not trying hotpatching because root package is not hotpatch-aware: Microsoft-Windows-ProfessionalWMCEdition~31bf3856ad364e35~amd64~~6.3.9600.16384

Then all the more reason to use an ISO which already has KB3000850 in it (which was my main point, as well as wondering what other differences there would be between the two ISO packages.)

In any case, after creating a Restore Point this happens (at 23695)

2015-07-12 12:49:35, Info                  CBS    Exec: End: nested restore point - complete.
2015-07-12 12:49:37, Info                  CBS    Exec: Processing complete.  Session: 30457051_2904789849, Package: Microsoft-Windows-ProfessionalWMCEdition~31bf3856ad364e35~amd64~~6.3.9600.16384 [HRESULT = 0x00000000 - S_OK]
2015-07-12 12:49:37, Info                  CBS    Session: 30457051_2904789849 finalized. Reboot required: yes [HRESULT = 0x00000000 - S_OK]
2015-07-12 12:49:40, Info                  CBS    Session: 30457051_3827705371 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:48, Info                  CBS    Session: 30457051_3909022164 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3919335977 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:49, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3919335978 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:49, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3919492246 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:49, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3919492247 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:49, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3919492248 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:49, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:49, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:49, Info                  CBS    Session: 30457051_3921054736 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3922929741 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:50, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3922929742 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:50, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3922929743 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:50, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3922929744 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3923242242 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:50, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:50, Info                  CBS    Session: 30457051_3923242243 initialized by client WindowsUpdateAgent.
2015-07-12 12:49:50, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2015-07-12 12:49:50, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2015-07-12 12:49:54, Info                  CBS    Session: 30457051_3969750980 initialized by client WindowsUpdateAgent.
2015-07-12 12:50:13, Info                  CBS    mapping index is not updated.


But not having access to source or support documentation I have no idea what it means. (I'm not even perfectly clear on which messages pair with which of the preceding or following messages when an error is reported.)  So that's why I would be using ProcMon to supplement and clarify messages such as these.  ProcMon's timestamp has much finer resolution than the second that we get in this log and besides there would be other trace events which would give them clearer context.

It kept trying to continue.  Why?  To try to provide a complete inventory of problems before aborting or to only abort when something really unrecoverable was found?  Who knows?

Then I think (hope) we can skip down to 497915

2015-07-12 13:05:41, Info                  CBS    Perf: Entering stage: Resolving

Hmm...  Looks like there is a break in continuity.  This file ends at the time shown (a few thousand lines further on) but the CBS.log starts at 13:09.   And your WindowsUpdate.log shows that all kinds of stuff was happening in that interval.

Since there are such huge numbers of events which ProcMon would have to trace it may not be practical to use that tool in the usual way.  E.g. normally it traces everything and its trace "file" is in RAM.  So, I imagine you would have to be selective about what events you would keep and where.

Supposedly there are alternative traces that we could invoke using netsh trace but I haven't tried that to say how or how useful it might be.

 

HTH

Free Windows Admin Tool Kit Click here and download it now
July 14th, 2015 10:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics