Status of compatibility with patched UXtheme.dll?
Status of compatibility with patched UXtheme.dll?
For a long time now, I've had to unpatch my uxtheme.dll to get VirtualBox to run. It's really irritating, especially since I reported the problem a year or so ago and was told it's being worked on. The last version that worked was 4.3.12, and here we are at 5.0.16 and it's still the same. Are there plans to ever allow VirtualBox to run with patched system files again? Or is there some unofficial work-around I can do?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Status of compatibility with patched UXtheme.dll?
There are plans to never do either, according to dev statements in the past. Since "never" still includes now, I'd guess that position hasn't changed.Weboh wrote:Are there plans to ever allow VirtualBox to run with patched system files again? Or is there some unofficial work-around I can do?
Patching isn't the problem. The problem is that it gets added to the VirtualBox process space, and it is unsigned. If you want it to work then get it signed. Even self signing has been suggested.
Re: Status of compatibility with patched UXtheme.dll?
Well, that explains why it hasn't been fixed by now. I got the info that it was going to be from another thread I posted on here, but I guess that guy didn't know what he was talking about. :/ How can self-sign it?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Status of compatibility with patched UXtheme.dll?
I suggest that you ask Google that (non VirtualBox) question. Note also that I didn't say it would work, only that it has been suggested. I've never had need to try it myself.Weboh wrote:How can self-sign it?