Is it just me or does this link to the download point to a site that tries to download anything but the installer or archive file? Now getting "Infected with virus, click here"
Please help, it's probably just me but I've tried all links I can find to files and mirrors for WMC-V8.8.1_x64_by_T-S.7z (preferred if I can get to it) and WMC_6.3.9600.16384_x64_v12.7z and, apart from being redirected to malware sites getting multiple attempts to install viruses, nothing seems to work. Can someone point me to a reliable link to download the archive files. Probably just being a total Luddite but I can't seem to get there. Many thanks
No, it isn't just you. People have been reporting the malware issues you mentioned for years and unfortunately, whoever was keeping everything together on page one seems to have moved on so we now have bits and pieces all over the place here, on The Green Button and on windowsmediacenter.fr. Version 12 won't install on Windows 10 after 1803 so I created V13 and information about that is available here: https://forums.mydigitallife.net/th...ible-alternatives.61061/page-469#post-1530669 and here: https://forums.mydigitallife.net/th...ible-alternatives.61061/page-469#post-1531053 Things have moved on a bit since then and details of known issues can be found in the installer. Versions 8.8.1 has been superseded by 8.8.2 and 8.8.3 and information about those are here: https://forums.mydigitallife.net/threads/discussion-patch-wmc-to-run-on-windows-10-final-possible-alternatives.61061/page-448#post-1470410and here: https://forums.mydigitallife.net/th...ible-alternatives.61061/page-458#post-1515101
ho spostato tutta la cartella scaricata in c. non mi da piu le scritte rosse ma quando avvio installler.cmd da amministratore non appare niente nel cmd. e poi appare la finestra vuota. uso winndows 1903 64 bit
please show a screenshot of the contents of the installer folders you have now. please also describe what happens if you run _testrights.cmd.
So having changed my server task to run as the logged on user it's pulling it's updates from SD reliably and when WMC isn't recording it also updates the client on that machine (and the clients on other machines pull their EPG from it nicely). However when it's recording it's unable to update the local client EPG -- or put it this way, your lovely icon on the splash page of WMC indicates it was updated the day before, haven't dived deep enough to determine whether the guide data itself has been updated and only the icon update is failing. Using the EPG123 Client and clicking Manual Update succeeds however, regardless of whether something is being recorded or not.
There had been a couple reports that importing the guide information may abort an active recording. EPG123 will pause importing the guide information until 1-minute after the latest end-time of any active recordings (or 1-hour later, whichever is soonest). If at that time, there is another active recording, it will pause until 1-minute after the latest end-time, or 1-hour, again. It will do this until you have exceed 5 hours from your original update time. If you check the trace.log file, you will see how the events unfolded. Personally, I was never able to duplicate the aborted recordings, but I put the protection in place anyway. If you want to force the update regardless of your recording status, you can add the -f switch to the epg123client task action. Reference page 15 of the installation guide. Note that this scenario is only for importing the guide listings into a WMC that is recording. The MXF file generation will still work and all your clients that are not recording will still update as scheduled. EDIT: I should mention that a manual import assumes the user wants to force the update. The user is in control of when the import happens and the client will perform the import without complaint.
Yeah, I was wondering about integrating that update with recording service, never occurred to me that you would automatically reschedule the update though, very nice. My Saturday recording schedule tends to be all day so I guess it'll eventually just time out some time in the day and if I'm antsy I can goose it manually like I have been. Knowing my luck I'll forget about the possible recording interruption and months from now I'll be all WTF when I screw a recording up.
As previously stated, the installer doesn't like spaces in the path Code: Preparations: - After you download the pack, make sure the .7z file is Unblocked to do so, right click on file, check properties general - click Unblock button if present - Extract the file to a directory with short spaceless path (example: C:\WMC) to avoid troubles - Make sure there are no pending servicing updates operations so please remove the space in 'new wmc-v13_64' and try again.
I notice that my EPG123 watermark is yellow with a bang in it today so was looking in the trace.log and see what I assume is the cause of the problem: [7/11/2019 8:27:03 AM] [WARNG] Program EP024543900206 is missing required content. [7/11/2019 8:27:03 AM] [WARNG] Did not cache program EP024543900206 due to missing Md5 hash. No big cause for concern I suppose, we'll see if it goes away tomorrow but it occurs to me should I be setting up some sort of logrotate on trace.log? I could see that thing getting real big after a while.
When the file gets to 1MB, EPG123 will put a timestamp on the filename and start a new log file. At most you will have two 1MB old files and the current active file. Older files will be deleted.
Is it possible to edit anything in the registry to adjust the timeout on the overlay in Windows Media Center? I'm talking about the one that shows on mouse movement, and has the play/pause, volume buttons, etc... It seems about 5-6 seconds for it to disappear, but I'd like it to be 1 sec. Thanks
Hey there, New to the forum, I stumbled across this from an internet search. I downloaded the X64 version, Got it installed and got my HD Connect tuners setup. DVR and Guide seem to work good so far. I haven't setup Emby on it yet. but plan to tonight. I was reading about the possibility of this being nixed by a future windows update. Is that still a possibility and if it is, what happens when it does. Thanks!