Little (big?) error

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Pandora's_Element
Posts: 3
Joined: 16. Jan 2016, 12:21
Primary OS: MS Windows 7
VBox Version: OSE Debian
Guest OSses: Linux

Little (big?) error

Post by Pandora's_Element »

So I may or may not be new to the forums (hint,new)
I used to use virtualbox like 4 years ago or so and i recently decided to retry virtualbox for the hell of it since i'm bored.
Well... I looked up this error I keep getting when I try to boot up my Debian VM on Win 7

Code: Select all

Failed to open a session for the virtual machine Debian.

Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=1790 (VERR_UNRESOLVED_ERROR).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I found the Locked sticky topic about a similar issue and attempted to do this;
Petr Vones wrote:
The log says you very likely use modified unsigned vesion of uxtheme.dll to get useable UI in Windows 7. VirtualBox no longer allows this, you are no longer owner of your system, you must use signed DLLs only :D Try to copy original unmodified Microsoft uxtheme.dll (presuming you have its backup) into the virtualbox directory where virtualbox.exe resides. This should satisfy the malware check and VirtualBox UI will look ugly but it should not affect other applications look as you probably wanted. If it does not work you have to revert back to the original uxtheme.dll in windows system directory but you will lose the Windows UI customization at all, for all applications.
but alas; it didn't work or i'm just plain stupid.

Anyone mind helping me out?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Little (big?) error

Post by socratis »

The error could be due to several things, don't assume it's the uxtheme.dll (although that is definitely a source of the problem). In the folder the you have your logs, there should be a VBoxHardening.log. Zip it and attach it, along with zipped VBox.log.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Pandora's_Element
Posts: 3
Joined: 16. Jan 2016, 12:21
Primary OS: MS Windows 7
VBox Version: OSE Debian
Guest OSses: Linux

Re: Little (big?) error

Post by Pandora's_Element »

I'll guess you mean only the text files and not the .log.1(2,3)

Anyone?
Attachments
Logs.rar
(25.49 KiB) Downloaded 14 times
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: Little (big?) error

Post by mpack »

Pandora's_Element wrote:I'll guess you mean only the text files and not the .log.1(2,3)
Hmm. My own guess is that when he said "VBoxHardening.log", he meant "VBoxHardening.log" and nothing else.

Tip: go into Folder Options and turn off the feature "Hide extensions for known file types". It is confusing you. For example, when you see the file "VBoxHardening" you are confused into thinking that is the actual filename.


As to the problem: certainly the log shows uxtheme.dll being rejected, but I wouldn't assume that is the problem, or indeed that the problem is hardening related at all. I would start by reinstalling VirtualBox for the correct user (i.e. not "Admin"), using "Run as administrator". If that fails then I'd test what happens if AV is disabled. I'd test what happens if an unhacked but correct version of uxtheme.dll is placed in the VirtualBox Program Files folder.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Little (big?) error

Post by socratis »

Actually mpack I just had a look at the logs, and the VBoxHardening.log is there, as well as the VBox.log, so we're good.

@Pandora's_Element
You mentioned in your first post that you tried to undo the "uxtheme.dll", but from the log:

Code: Select all

3218.331c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\uxtheme.dll: Not signed.
'\Device\HarddiskVolume2\Windows\System32\uxtheme.dll' is most likely modified.
Try running "sfc /scannow" to see if that fixes the issue.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
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: Little (big?) error

Post by mpack »

Do not run sfc /scannow unless you want to mess up the theme. If you do want to do that then you should uninstall it in the normal way - all Windows theme patchers I've come across have a proper installer, and therefore can do a proper cleanup (not just restore system DLLs). Before any of that I would start by trying the things I mentioned above.
Pandora's_Element
Posts: 3
Joined: 16. Jan 2016, 12:21
Primary OS: MS Windows 7
VBox Version: OSE Debian
Guest OSses: Linux

Re: Little (big?) error

Post by Pandora's_Element »

Id rather not mess up my theme ty :3

How would i get a registered .dll, just google and dl?
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: Little (big?) error

Post by mpack »

Registered DLL? You mean the original unhacked one? Ask whoever made the theme patcher. Typically they have a backup folder somewhere where they store the original DLL before hacking it.
Post Reply