[DISCUSSION] Patch WMC to run on Windows 10 final & possible alternatives

Device manager? Firewall?

 

Remote Desktop Connection on Windows 7 with KB3108669

@crash2009

I managed to get Media Center to work on a fresh Windows 7 SP1 without installing any update (approx. 200 since SP1). The only one I installed is KB3108669 for Media Center. My other updated Windows 7 SP1 VM has an issue.

So here is the patched bytes in order to get Remote Desktop Connection to a Windows 7 box -- which will hopefully work on WHS-2011.

Microsoft.MediaCenter.UI.dll (6.1.7601.17514)

Code:

6ebfa     20 00 10 00 00 28 C5 28 00 06 16 FE 01 16 FE 01
          16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ehshell.dll (6.1.7601.19061)

Code:

182038    28 C7 1B 00 0A 2C 0A 28 29 63 00 06 16 FE 01
          16 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code:

18dc6b    02 7B 14 34 00 04 7B 9A 34 00 04 2D
          16 00 00 00 00 00 00 00 00 00 00 2C

Tip #1: use fsutil hardlink list <file> to get all hard-linked copies of a given file.

Tip #2: use subst Z: C:\Windows\assembly to mount assemblies cache on Z drive in order to view actual files and folders, and temporarily rename them to prevent access (keep in mind you must use ngen to perform appropriate file image regeneration). Use subst Z: /d to unmount.

 

Odd that it crashes on RDP, Did you run setup first ? Never tried to run "first run" in a RDC session.


View attachment 39670


I have a perfectly clean Windows 7 SP1 Ultimate trying to test cable by connection to see what can disable the above volume control. Spent about 3-5 hours yesterday trying things. A few more tests today. Really annoying bug for me.

I'll try to test the RDP thing.

 

I've used just WIN+R C:\Windows\assembly , It works

 

No I didn't, but on last clean Windows 7 SP1 with KB3108669 only, it doesn't crash.

Volume control also appears when you swap to remote desktop client and click on Media Center window. I guess it appear whenever audio device is changed/reset.

 

The volume popup appears also whenever "something" changes the main volume.

Could be even a spurious remote control input (say a flickering CCFL lamp misinterpreted by the remote receiver), or another external tool that sends unwanted commands

The eventghost log windows can help to exclude that possibility or to understand it's origin.

 

I understand now...

Line 1 is the query.
Line 2, 3, 4, is the answer.

Run this in Win7 and the location of files that need to be copied over with the patch version will be revealed.

 

You need to login to view this posts content.

 

I'm having some fun playing with RestoreHealth and this is mentioned I the logs, is this due to this package?

2016-02-14 17:29:18, Info CSI 00000008 CSI Store 2110423767472 (0x000001eb5f0f19b0) initialized
2016-02-14 17:29:18, Info CSI 00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]"10.0.10586.0 (th2_release.151029-1700)".
2016-02-14 17:29:18, Info CSI 0000000a@2016/2/14:17:29:18.940 Starting corruption detection (InnerFlags=5)
2016-02-14 17:30:36, Info CSI 0000000b@2016/2/14:17:30:36.576 Corruption detection complete. numCorruptions = 0, Disp = 1.
2016-02-14 17:30:36, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2016-02-14 17:30:36, Info CBS Repr: CSI Store check completes
2016-02-14 17:30:36, Info CBS Exec: Not able to find Microsoft-Windows-MediaCenter-Package-avcore~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find Servicing\Packages\Microsoft-Windows-MediaCenter-Package-avcore~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find update.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find Servicing\Packages\update.mum from directory local source
2016-02-14 17:30:36, Info CBS Repr: Not able to find replacement manifests for package Microsoft-Windows-MediaCenter-Package-avcore~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384 from any local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find Servicing\Packages\Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find update.mum from directory local source
2016-02-14 17:30:36, Info CBS Exec: Not able to find Servicing\Packages\update.mum from directory local source
2016-02-14 17:30:36, Info CBS Repr: Not able to find replacement manifests for package Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384 from any local source
2016-02-14 17:30:36, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2016-02-14 17:30:36, Info CBS Exec: Clients specified using local source only.
2016-02-14 17:30:36, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.
2016-02-14 17:30:36, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2016-02-14 17:30:36, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2016-02-14 17:30:36, Info CBS Ensure WCP corruption flag is clear
2016-02-14 17:30:36, Info CBS
=================================
Checking System Update Readiness.

(p)CBS Catalog MissingMicrosoft-Windows-MediaCenter-Package-avcore~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384
(p)CBS Catalog MissingMicrosoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384

 

Not sure but that is possibly wanted.

If it was able to get the files from WU it would replace the patched files with the original ones, making WMC useless.

 

Only problem I have is When I start WMC, it shows up, and when every I play or stop a video it shows up. My OCD is driving me nuts with it on 7....sigh. I am looking how to completely disable that display in WMC 7...

 

If that's the case, would I ever be able to have a 100% valid clean image

 

You need to login to view this posts content.

 

This registry value allow exploring assembly as regular folder

Code:

reg add HKLM\SOFTWARE\Microsoft\Fusion /v DisableCacheViewer /t REG_DWORD /d 1 /f

 

You need to login to view this posts content.

 

Suppress volume popup on Windows 7

To suppress volume popup (mute will still be displayed), patch ehshell.dll (version 6.1.7601.19061, x64) the following way:

Code:

0x1829d6   0x17  -->  0x16

To also suppress mute popup:

Code:

0x1829dd   0x17  -->  0x16

 

You can still be able to use the V8 which isn't DISM based, possibly replacing its files with the latest taken from V12

 

Your a god, no other way to put it. I know there was a combo of hardware that caused this (directly from Microsoft), and over the last 3-4 weeks, I have been trying every way possible to get this to work (easy 25+ hours in this).

Anyone got any tips for me to apply this ? Never edited code like this before...

 

You need to login to view this posts content.

 

Added the one click installer for W10 back on msg #3657