This batch should resolve localization issue: Code: for /f "usebackq delims=" %%x in (`powershell "(New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-544')).Translate([System.Security.Principal.NTAccount]).Value.Split([IO.Path]::DirectorySeparatorChar)[1]"`) do set admins=%%x for /f "usebackq delims=" %%x in (`powershell "(New-Object System.Security.Principal.SecurityIdentifier('S-1-5-20')).Translate([System.Security.Principal.NTAccount]).Value"`) do set netsvc=%%x net localgroup %admins% "%netsvc%" /add
I upgraded from Win 7 Pro X 64 to Win 10 Pro. I downloaded the file from "Download WindowsMediaCenter 6.3.9600.0 x64 v2.rar" , unzipped it, and followed instructions and when the installer finished went to Windows/ehome but there is no 'eshell;.exe. What did I do wrong?? I use WMC as my DVR.
Frankly I don't think that the file permissions are critical like the registry ones. All my first working versions were done just copying manually files and directories straight from the original ISOs using 7zip.
I just downloaded the v5 installer. When I run both the _TestRights.cmd file and Windows Media Center after installation, I keep getting Windows SmartScreen warning that it prevented an unknown application - possibly because the publisher is listed as "Unknown Publisher." Is this normal?
Sorry, I need help again. For some reason, when I try to do live TV, I have a flashing black screen. After a few minutes I can see it flash "Video error". Have a feeling it has nothing to do with WMC. Removed the AMD Radeon Hd6530D display adapter driver which put it back to MS driver. My monitor then works with no flashing. But I do not have HDMI which I use for my TV. Reinstalled the display adapter and back to flashing. Have no clue what is causing this problem. Any help would be greatly appreciated. Really want to get WMC working before the Fall TV season starts. DeWayne
I had the same issue. After you downloaded the installer file, right-click on it and select Property and then click "Unblock". All files extracted from the installer should no longer be blocked. Files without certification and downloaded from the Internet are blocked by default. The extracted files also inherits the blocks.
Hi guys. I am one of the authors of serverwmc and I just want to say how much I appreciate this project. It's enabling me to upgrade my development machine to win10 while continuing to use it to develop for serverwmc. You guys rock.
Yes, the copy command is universal, as long as the files and directories are similar to real install location (as in wim) i actually included it in x86 version (KB3087918: ehshell.dll) had this messege myself, but the process complete successfully, so no reboot required and the messege can be ignored x64 system with UAC is very protective sometimes
Thanks to you for your great application. I think It's time to take w10 in account on new ServerWMC installations I mean w/o having to tweak the .config files.
The properties on Installer does have an unblock? Properties on the "_testrights.cmd" does. Tried to do unblock on ehshell.exe and receive - "an assertion error has occurred"??? Nevermind - went back to a previous version of WMC that does not have the problem.
? I used the serverwmc installer in win10 with v3 last night and didn't have to change the config file. But I'd be happy to change it if need be. I'll look into it again.
I meant the zip files that contain the installation files. All that I did was unblock that file first before unzipping the contents. Doing so also unblock all files within the zip file. I don't know if it's a Windows 10 thing since I don't remember having this issue with Windows 8.
in yours x32 pack there is 6.3.9600.18015 x32 ehshell.dll... OK and in dejong12's x64 pack there is: ehshell.dll... 6.3.9600.16384 (unpatched) and x32 bit one too... why 32bit DLL in 64 bit pack? )) (OK, there x32 dll in x64 MSU patch too) but still time to make v6
It looks like everything is running great now including the guide. However, I must launch WMC with administrative rights. I get two errors in the Event Viewer when trying to launch as a standard user (no admin). Note that no UI ever appears, and the errors are logged silently in the Event Viewer. It works fine other than the run as admin is required. This is somewhat important because the computer is shared at home, and I don't want to pass out the admin PIN to run it. .NET Runtime Code: Application: ehshell.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.UnauthorizedAccessException Stack: at System.IO.__Error.WinIOError(Int32, System.String) at System.IO.Directory.InternalCreateDirectory(System.String, System.String, System.Object, Boolean) at System.IO.Directory.InternalCreateDirectoryHelper(System.String, Boolean) at Microsoft.MediaCenter.Store.SharedMemory.ConstructSharedMemoryFilename(System.String, System.String) at Microsoft.MediaCenter.Store.SharedMemory..ctor(System.String, System.String, Int32, Boolean) at Microsoft.MediaCenter.Store.SharedMemoryManager..ctor(System.String) at Microsoft.MediaCenter.Store.StoredObjectRegistry..ctor(System.String) at Microsoft.MediaCenter.Store.StoredObjectRegistry.GetRegistryForStore(System.String) at Microsoft.MediaCenter.Store.ObjectStore.BeforeOpen(System.String) at MediaCenter.Store.SqlLite.ObjectStore.Open(System.String) at MediaCenter.Store.SqlLite.ObjectStoreManager.Open(System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, System.Reflection.Assembly, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.AddObjectStoreReference() at Microsoft.MediaCenter.Store.ObjectStore.get_DefaultSingleton() at ServiceBus.UIFramework.UserControlPoint.Launch(System.String) Followed by: Application Error Code: Faulting application name: ehshell.exe, version: 6.3.9600.16384, time stamp: 0x5215efc2 Faulting module name: KERNELBASE.dll, version: 10.0.10532.0, time stamp: 0x55d90461 Exception code: 0xe0434352 Fault offset: 0x000000000000d1a8 Faulting process id: 0xfd4 Faulting application start time: 0x01d0ed858ace3542 Faulting application path: C:\WINDOWS\ehome\ehshell.exe Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll Report Id: c9c7fd22-b1d7-4f34-888f-e19082be26da Faulting package full name: Faulting package-relative application ID: I tried taking ownership from TrustedInstaller to Users for ehshell.exe and changed to Full Control, and now I get a different errors. .NET Runtime Code: Application: ehshell.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException Stack: at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, System.Reflection.Assembly, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.Open(System.String, System.String, System.String, Boolean) at Microsoft.MediaCenter.Store.ObjectStore.AddObjectStoreReference() at Microsoft.MediaCenter.Store.ObjectStore.get_DefaultSingleton() at ServiceBus.UIFramework.UserControlPoint.Launch(System.String) Followed by Application Error: Code: Faulting application name: ehshell.exe, version: 6.3.9600.16384, time stamp: 0x5215efc2 Faulting module name: KERNELBASE.dll, version: 10.0.10532.0, time stamp: 0x55d90461 Exception code: 0xe0434352 Fault offset: 0x000000000000d1a8 Faulting process id: 0x1278 Faulting application start time: 0x01d0ed8d48e77335 Faulting application path: C:\Windows\ehome\ehshell.exe Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll Report Id: 331768aa-16ad-4501-937c-11795d4fd251 Faulting package full name: Faulting package-relative application ID:
Indeed it works perfectly if ran over an 8.1 based installation (like the latest builds posted here) but it fails on W10 based ones unless you change the lines <bindingRedirect oldVersion="0.0.0.0-6.3.0.0" newVersion="6.3.0.0"/> to <bindingRedirect oldVersion="0.0.0.0-6.3.0.0" newVersion="10.0.0.0"/> in .config files So not a biggie, but someone may want to use the w10 based for various reasons.