Can't login anymore

[Perryg]

The lock usually means that you have not ejected the guest additions after you installed and are trying to change it. Several ways to get around this but probably the easiest way is to shut the guest down ( not saved state ) and use the remove media from the storage section of the guest settings. Be careful to use the remove media and not delete the virtual drive. Then use the device tab to insert the new one and install manually if need be.

[socratis]

It is already installed, so when I try to install it I have an error.

If it is not the error that you described, please explain in full what the error is. And being already installed doesn't mean that you can't update them. In fact you have to update them in your case to solve your original problem.

I tried to install it --> Nothing happened. I think he mounted it and do nothing because it is already installed.

No, what you did is to insert the Guest Additions CD in the virtual drive. After that you'll have to do the installation. If not prompted for the autorun feature, you navigate to the CD and run "VBoxLinuxAdditions.run".

Code: Select all

$ cd /run/media/socratis/VBOXADDITIONS_5.1.15_113104/
$ sudo ./VBoxLinuxAdditions.run 

[tagadac]

I am reinstalling the guests addition following this website : https://www.if-not-true-then-false.com/ ... -hat-rhel/
I tell you if it works.

[tagadac]

It is already installed, so when I try to install it I have an error.

If it is not the error that you described, please explain in full what the error is. And being already installed doesn't mean that you can't update them. In fact you have to update them in your case to solve your original problem.

I tried to install it --> Nothing happened. I think he mounted it and do nothing because it is already installed.

No, what you did is to insert the Guest Additions CD in the virtual drive. After that you'll have to do the installation. If not prompted for the autorun feature, you navigate to the CD and run "VBoxLinuxAdditions.run".

Code: Select all

$ cd /run/media/socratis/VBOXADDITIONS_5.1.15_113104/
$ sudo ./VBoxLinuxAdditions.run 

Yes sorry, I noticed that I had only mounted the Guest Additions CD... I have updated it and I still have the same issue and I can only start the GUI in root with startx. With the common session it's not working.

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[tagadac]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Do you want all the logs ? VBox.log, VBoxHardening.log etc. ?

If so see the zip attached.

Thanks for helping me !

[Perryg]

Code: Select all

00:00:04.322437 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_9d43288bdbeaa52f\nvinitx.dll: WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_9d43288bdbeaa52f\nvinitx.dll'
00:00:04.322606 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_9d43288bdbeaa52f\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_9d43288bdbeaa52f\nvinitx.dll): rcNt=0xc0000190

This error seems to point to a certificate being out of date or something has tied onto the file that is not supposed to. Virus software is really big at doing this, but is not the only culprit. I would see if there is a new driver for you hosts GPU and it might not hurt to check for a virus. Also sfc /scannow might help.

[tagadac]

Also sfc /scannow might help.

It looks like I maybe have a problem, when I do so it reaches 100% and then told me that Windows couldn't do anything. I also launched a sort off scan during the boot and it couldn't do anything too... Strange.

[Perryg]

I am not much on windows so I will need to let someone that is continue. Good luck.

[tagadac]

Thank you very much for your help ! Hope I found out ! It could be help-full for future users !

[socratis]

Just out of curiosity, try to 1) increase the display RAM to at least 64 MB if not 128 MB, and 2) toggle the 3D acceleration setting.

[Perryg]

I see this asked a lot these days but I have not chimed in. It is very rare that a Linux guest would need more than 16MB of vRAM and 32MB would probably be overkill. I agree that testing with 3D off would tell you something. Probably that the log was correct because it is rejecting a file from the hosts GPU. I do use nVidia and there were some issues with older versions of it but I have no idea how that effects Windows and its hardening. Linux has always been hardened but it does not use the stupid registry stuff, or virus software ( for the most ).

[Perryg]

I did notice something that has me scratching my head though. The log says it is not allowing the nVidia driver, but it is loading an Intel GPU driver.

Code: Select all

supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf
...
00:00:04.744197 OpenGL Info: Render SPU: GL_VENDOR:   Intel
00:00:04.744211 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 5500
00:00:04.744216 OpenGL Info: Render SPU: GL_VERSION:  4.4.0 - Build 20.19.15.4454

Does the host have a dual graphics adapter ( like low power mode ), and if so is it set to use the right one? Even so the rejection needs to be corrected.

[tagadac]

Just out of curiosity, try to 1) increase the display RAM to at least 64 MB if not 128 MB, and 2) toggle the 3D acceleration setting.

I tried, same issue...

Does the host have a dual graphics adapter ( like low power mode ), and if so is it set to use the right one? Even so the rejection needs to be corrected.

I am working on a laptop and inside I have a Nvidia graphic card and an Intel video chipset when 3D rendering is not used (some sort of low power mode). I have updated all my drivers.

[ScoobyDoop]

It doesn't look like this issue was ever solved. The exact same thing just happened to me, and I got it working, so below is the sequence of events. Please bear in mind that I have almost no idea what I'm doing.

I have a fresh installation of Linux Mint 19 running on VBox 6.0.4 r128413 running on Win10 64 bit. I was fooling around with the settings, and attempted to add a "Shared Folder". I set this to "auto mount". Of course, it did nothing since I didn't have Guest Additions installed.

I finally realized I had to install Guest Additions 6.0.4, and did this, and then rebooted the Guest. After this I couldn't login, exactly as described above by tagadac: it would accept my password, then briefly blank the screen, and then just kick me back into the login screen. I tried many things to get this working (and eventually found this thread).

Well, looks like I got it working by sheer luck. I figured it had something to do with the Guest Additions, so I deleted the "Shared Folder" entry that I had put in previously. That's all it took, now I can log in normally. By the way, there were a number of things screwed up about this particular Shared Folder entry, like the mount point specified did not exist in the Guest filesystem (or was it that I specified my home folder as the mount point ?? can't remember...).