I originally asked for suggestion to my problem as there is no mention of it on this thread and no mention of a workaround in the readme file, no one responded. A month later I asked again, you respondeded and suggested I look at your post before my question with a suggeston. I did read your post and it didnt seem relevant to my problem, even though you gave a suggestion you didnt go into detail. I didnt know what nsudo does or superuser64 and read up on it and found out about TI "trusted installer". I have never used it, or had to and not heard about anyone else having to. I then asked if you could elaborate please, you replied and explained about TI and nsudo 8 and what to do, ok. I then ask if there might be something wrong with my win 11 install, I quoted the ver I am using in my original question, although it is fully updated, it is not at the latest version and wont update anymore. if there was a problem and it has been fixed, fine, there has been no further updates since WMC-V8.10.0 that I have seen and no other mention of my problem to suggest a fix has been made. of course I want a working program, I am curious as to whats causing it and wondering if its my "build" of win 11 I use ver 8.8.5 on win 10 22H2 build 19045.3803 with no problems I have a spare ssd with win 11 on, that I wanted to test and give feedback on. Have I said or done anything wrong, or to offend?
No one has ever used something before using it for the first time, perhaps If you ever installed any WMC package from me, abbodi and and variation from other users, you have already used. I patiently explained what they are and I explained patiently how to overcome the problem you are facing. For everything else duckduck is your friend So I still dont understand what prevents you from following the suggestions that i provided using a bit of my free time. And I think my free time is, at least, as valuable as yours. Yea that's a scoop. Don't you think that if there was a ready made meal for you, it was easier for me to provide a link to the updated file? Abbodi decided to don't take actions, And I didn't asked further given there isn't any practical impact. Overcoming the problem is deadly simple and takes something like 10 seconds, so again I still can't see where your big problem is. Follow my instructions or use an older package. That's all
In my experience Nsudo 8 is more universal and less buggy than other solutions, but if Nsudo 9 or something else works for you, there isn't a compelling reason to replace it.
FWIW, I also hit the same issue with a single-user Hyper-V VM (with enhanced session, so much likely involving some RDP magic too). It's not terribly complicated to tweak the script to use NSudo8 instead of SuperUser for an advanced user, but it makes the user experience for everyone else a bit... suboptimal. IMHO, that would be nice if @abbodi1406 considered replacing SU by the battle proven NSudo8 (Happy New Year everyone!)
Well given the elevation script is separate from the installer script, Is probably just matter of copying nsudo.exe in the bin folder and overwriting the elevation script with an older copy Not getting that, what changes for the end user if the elevation exe is X.exe over Y.exe (assuming they are both working)? To you !
Yup, just add NSudoC.exe in the bin folder and replace 'superUser64.exe Install.cmd' by 'NSudoC.exe -U:T -P:E "\"\"%~dp0bin\Install.cmd"' and it fixes the issue. Well, the scenario you describe (i.e having a dedicated Windows user for WMC with autologon) is likely quite common, so we're probably not the only ones who'll hit this weird behavior when using the 8.10 package. The user experience would be much better if it worked without tweaking the installation script, as the 8.8.x branch did
@Kévin Chalet Ok I got your sentence wrongly I thought that "suboptimal" was referred to a version with superuser replaced with nsudo 8, so I did wonder how a fix could make the experience suboptimal... So to address what you really meant, frankly I'm bored about "normal" users that dont think twice when using the work of many people who spent months or even years (like in the WMC case) perfecting a program, but are unable even to "add water and stir", because it's too complicate. There are users here that follow this thread since 2015, and after a decade got NOTHING from a decade of development, suggestions, fixes and so on. This is not incompetence, this is laziness.
I believe it has a lot to do with the fact WMC has always been regarded by many users as a "turnkey" Media Center option: it used to be installed by default on most high-end Windows versions and configuring it was only a matter of answering a few questions (thanks to its amazing wizards). Sadly, it's no longer true today and there are lots of roadblocks: it's no longer officially supported, CableCARD no longer works on recent versions of Windows 10, the fullscreen mode is buggy on Intel's 11th+ iGPUs, many countries moved to HEVC/AC4 which isn't supported by WMC, etc. If we're honest, it takes a lot of dedication to keep using WMC in 2024... and not everyone has the skills (or patience) required to deal with all that stuff. @abbodi1406 any objection if I publish a 8.10.1 version of your package with NSudo8 instead of SuperUser?
Speaking of that, I finally took the time to give Patchou's Media Center Themer a try during the holidays (I've always been a huge Media Center Studio fan) and OMG, what a wonderful piece of software it is! It makes authoring and deploying WMC themes a whole lot easier. Not sure why I haven't tried it sooner...
Unfortunately, the x86 console version of NSudo 8.2 is flagged as a malware by Windows Defender, so it's not ideal (surprisingly, neither the x86 graphical tool nor the x64 CLI/GUI are flagged ) I tried with gsudo and it seems to work on my Hyper-V VM machine (it's a signed executable, so it probably helps not being flagged). Do you guys have any experience (or concerns) with it?
Sure, but those people can use W7/W8/W8.1 with the official WMC or LTSC2015 + the old package w/o any major drawback. My personal idea is that if someone has the curiosity and the will to try WMC on "unsupported OSes" has very likely enough skill to launch a TI prompt and to type install.cmd Well at least for win11 the problem is already solved in the worst possible way, there isn't any public 32 bit version No, sorry. I didn't investigate a lot on alternate exe after I figured out that 8.2 worked practically everywhere. But maybe is worth to take a look to runasTI by bau / aveyo that requires no external exe at all. P.S. I didn't play a lot with the latest version from @abbodi1406, except for 9200 version. But I think there is a regression over the 8.8.1 I use since the stone age... looks like is not possible to set the miniguide to 3/4/5 rows (using epg123) something that I always do and that always worked since w7. Given you are experimenting right now, can you check if it behaves the same for you? P.S2 About nsudo graphical, likely it can be used in a batch using the start command
Yes TrustedInstaller ACLs on files and directories is superfluous it should only be set on real CBS package
@abbodi1406 okay, thanks. What about the symlinks (well, hard links to be exact): was it deliberate too?
You can say so i don't think hardlinks are useful without WinSxS and the new copy is more appropiate for proper NGEN operation
I disagree here. If nothing else hardlinks avoid a waste of space. Back on I time decided to make 8.7/8.8.x purposely to replace the duplicated files with proper hard links, and I never had a problem with them
Well, it sadly breaks important scenarios like the one @acer-5100 mentioned. I just double-checked and as I expected, the GACed assemblies were hard links on the original Windows 7 version. Regarding NGEN, I'd expect native images to be invalidated (and recreated) when the associated managed assembly is updated.
It's hardlinked because It's CBS do you see .NET Framework 4.x files/GAC hardlinked? what's the problem exactly with "non hardlink" scenario?