Problems running vbm on Windows 7

[awachens]

Hi guys I have Windows 7 and virtualbox 5.1 (I think, don’t remember now).
When I try to run an image of Windows server 2003 for example ... send me an error ... and don’t create a virtual machine on users/virtualbox machine ...
but if I use detachable option run ok...
Why I have this problem is really annoying...

Thx and regards !

[mpack]

Please report error messages precisely.

We'll also require a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[awachens]

Hi guy, good morning.

Sorry for the delay. I add the zip file to this post.

Regards !! And thx a lot !

[mpack]

Please report error messages precisely.

"Send me an error" doesn't cut it.

As a shot in the dark you may want to fix this:

00:00:00.399732 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes

[awachens]

Hi guy, sorry for this... I forgot paste the error.

I enable the VT-x mode in Bios and i keep having the same error.

Regards and thx !

[mpack]

I wish I had known the exact error sooner. What you have there is a hardening error, so you need to read the hardening FAQ: FAQ: Diagnosing VirtualBox Hardening Issues.

If you have further questions then I'd need the hardening log mentioned in the error messages (as a zip attachment please).

[awachens]

Hi guy, sorry for the delay.

I have this line in log of hardening:

LdrLoadDll: returns rcNt=0x0 hMod=000007fefbaf0000 'C:\Windows\system32\uxtheme.dll'
182c.11dc: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 822 ms, the end);
144c.15b4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1169 ms, the end);

So i think i have not problems with DLL, no ? In the guide it says: if you have error code 0 then you don't have a hardening problem at all.

Or maybe he refers to this:
ExitCode=0x1

Regards and thx a lot !!!

[socratis]

Did you read the instructions from mpack?

If you have further questions then I'd need the hardening log mentioned in the error messages (as a zip attachment please).

An "ExitCode=0x1" means that you *DO* have a problem.

[awachens]

Wow!! I add the zip !!! Don't know why isn't here...

It what i was asking... I don't know if the first line that contains the error or the exitcode too...

Now i know, i have an error... I try to upload again the zip with hardening log.

Thank you.

[mpack]

It looks like you may have a hacked Windows theme (uxtheme.dll). This was mentioned in the faq.

[awachens]

Hi guy, good morning.

Yes i read some think about uxtheme.dll at FAQ.

In the first two cases the fix is to exclude the DLL or replace it with one with a valid certificate. --> How can i exclude ?

Regards !

Edit: I saw this on internet:

Regsvr32 /u uxtheme.dll

But.. What's up when i do this ? What problem can i create ?

Edit 2:

When i try :
Regsvr32 /u uxtheme.dll

The uxtheme.dll module was loaded but the DIIUnregisterServer entry point was not found.

Make sure that uxtheme.dll is a valid DLL or OCX file and try again

[mpack]

You can't exclude uxtheme.dll, it's a system DLL. You must replace it with the original version, which is signed by Microsoft and not hacked since. Sometimes you can get away with placing a copy of the unhacked uxtheme.dll in the VirtualBox Program Files folder.

I don't know what on earth you're trying to do by unloading an important system component on the command line, but I suggest that you stop immediately. Thankfully the error message implies that it ignored you.

[awachens]

Hi good morning!

How can i fix this?
Sometimes you can get away with placing a copy of the unhacked uxtheme.dll in the VirtualBox Program Files folder. -> How can i do this ?

Yes he ignored me xD thankfully...

Regards !

[socratis]

@awachens
You already have the answer in Diagnosing VirtualBox Hardening Issues. Please read it! All of it! Don't simply keep repeating the questions if the questions have been answered!

Run "sfc /scannow" from an Administrator account.

[awachens]

Hi guy, i do this but dont solve the problem.

Regards ! And happy new year !


Edit:

Iniciando examen en el sistema. Este proceso tardará algún tiempo.

Iniciando la fase de comprobación del examen del sistema.
Se completó la comprobación de 100%.
Protección de recursos de Windows encontró archivos dañados y no consiguió
reparar algunos de ellos. Para obtener más detalles, consulte CBS.Log
windir\Logs\CBS\CBS.log. Por ejemplo, C:\Windows\Logs\CBS\CBS.log.

Los cambios en la reparación de archivos de sistema surtirá efecto en el siguien
te reinicio.