Windows 10 Anniversary Update ate my WMC!

[a4x4kiwi]

The anniversary update uninstalled WMC!

Looks like that is the end of that. Time to go back to Win7!
WMC was the best media centre PVR IMHO.

Or MythTV, but that can't schedule recordings from Ice, so it might the end of IceTV for me.

I couldn't find a solution last night, and a reinstall failed. See below output.

Does anyone have any suggestions?

Code: [Select]

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

Processing 1 of 1 - Adding package Microsoft-Windows-MediaCenter-Package~31bf385
6ad364e35~amd64~~6.3.9600.16384
[==========================100.0%==========================]
An error occurred - Microsoft-Windows-MediaCenter-Package Error: 0x800f0922

Error: 0x800f0922

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


Installing package failed, reverting...

You may reboot and try again
refer to C:\Windows\Logs\CBS\CBS.log to find error details

Press any key to exit.


[Dave at IceTV]

IMHO Windows 7 is better than Windows 10 so I can't understand why anyone with a Media Center PC would want to upgrade to Windows 10.

Error: 0x800f0922 when installing a Windows update in Windows 10 is apparently very common. It can be caused by 3 issues:

1. Low System Reserved partition space. When there is no enough free space for the system reserved partition, the computer will not be able to load new Windows 10 installation files without an error code such as 0x800F0922.

2. Failed to connect to Microsoft Windows Update server. VPN connection or Firewall settings etc.

3. The .Net framework installation portion of the Windows 10 update faieds. This seems to be the most common cause talked about on the web.

DISM errors (Deployment Image Serving and Management) are also a common theme. In fact the version of the Media Center Pack you are trying to reinstall specifically mentions DISM errors being fixed.

There is a nice troubleshooting page for Error 0x800f0922 here:
http://www.todo-backup.com/backup-resource/system-backup/windows-10-update-with-error-code-0x800f0922-issue.html

If it was me, I'd go back to Windows 7 and never have to worry about Microsoft's updates breaking Media Center or Windows.

[Dave at IceTV]

PS The clever people at the mydigitallife forum have created an updated version of the last Win10 Media Pack that does not use the DISM installer. This version is specifically for people getting DISM errors when trying to install the Win10 Media pack v12 which uses the DISM based installer.

v8.8.1 is based on v8 but with all the bug fixes and improvements from v12. See the following post on the mydigitalife forum:
https://forums.mydigitallife.info/threads/61061-DISCUSSION-Patch-WMC-to-run-on-Windows-10-final-amp-possible-alternatives/page532?p=1244333&viewfull=1#post1244333

The download link as at the end of that mydigitallife forum post. On the page that the link takes you to make sure that
before clicking on the Download button you click on the tiny grey shield next to "Download with Secured Download manager" otherwise you may download something you don't want! If you look closely the shield has a tick inside it and when you click on it the tick vanishes. You want the tick to be gone before you click on the Download button.

PPS The download link from that forum post only has a x64 version so you may be out of luck if your Windows 10 is 32bit and you cannot install the normal v12 media pack.

[raymondjpg]

If it was me, I'd go back to Windows 7 and never have to worry about Microsoft's updates breaking Media Center or Windows.

Well, at least until 2020. I share your preference for Windows 7 over Windows 10 but it comes, increasingly, with transaction costs in the form of less attention paid to Windows 7 support in favour of Windows 10. Not just from Microsoft who would like to be rid of the troublesome OS because it is a nuisance to maintain but from other software and hardware vendors. For example Skylake that Microsoft was determined not to support with anything other than their newer products but had to because folk were just as determined to keep using Windows 7. Personally I live in hope that MS will come to a realisation that Windows 10 as it stands is not a worthy successor to Windows 7 and that it would be to their commercial advantage to develop and eventually provide one.

[raymondjpg]

The anniversary update uninstalled WMC!

It also ate my classic shell. If anything was designed to put people off using Windows 10 this is a prime example. MS are not doing themselves any favours here.

[Dave]

It ate my WMC also.
Previously I could only get the WMC v11 running on my Windows 10.
The new WMC 8.1.1 installs and works first time and all looks good.
With version 11 I found that WMC would lock up and if it was in Full Screen mode I had to hard boot the box.
Let's see if version 8.1.1 is better.
Dave.

[raymondjpg]

The new WMC 8.1.1 installs and works first time and all looks good.

Was that the 64 bit version? I am waiting on a 32 bit version.

[csutak40]

The anniversary update uninstalled WMC!

It also ate my classic shell. If anything was designed to put people off using Windows 10 this is a prime example. MS are not doing themselves any favours here.

Oh!  Is that what happened to it :-)  Funny thing is - I have two computers running with Win10 and it only ate it on one of them!  I only just noticed and was asking myself if I had forgotten to install it on that one.  Now I know what happened :-)

[raymondjpg]

Oh!  Is that what happened to it :-)  Funny thing is - I have two computers running with Win10 and it only ate it on one of them!  I only just noticed and was asking myself if I had forgotten to install it on that one.  Now I know what happened :-)

I may have jumped the gun. The update could have just switched the user interface back to the Windows 10 tiles. Classic Shell re-installed without any problems.

[csutak40]

Oh!  Is that what happened to it :-)  Funny thing is - I have two computers running with Win10 and it only ate it on one of them!  I only just noticed and was asking myself if I had forgotten to install it on that one.  Now I know what happened :-)

I may have jumped the gun. The update could have just switched the user interface back to the Windows 10 tiles. Classic Shell re-installed without any problems.

Yeah, it did re-install, but it still ate it    It had to be re-installed