virtualbox.org

---

[ModEdit, related ticket #17082: No more elevated rights after install of Guest Additions 5.1.28 on Windows]

---

After installing VirtualBox 5.1.28 and 5.1.28 Guest Additions in Windows 10 v1703, anything needing administrator rights results in: "extended attributes are inconsistent" The only way I've been able to fix this, is to uninstall Guest Additions and then I can get admin again.

This happens on both Windows 10 VMs hosted in Mac and Windows environments.

There is already a ticket open for this, you're not the only one seeing it.
#17082: No more elevated rights after install of Guest Additions 5.1.28 on Windows.

Ahh thanks! Spent 1/2 a day trying to fix busted VM, reverted, and finally tested on 2nd machine.

I'm testing different VirtualBox Additions, and 5.2.0beta2 & 5.1.27 gives the same results: extended attributes are inconsistent.

Grabbing older Additions from: download[.]virtualbox[.]org/virtualbox and grabbing 5.1.24 for example, everything is working normal again.

I do a full uninstall, reboot, install 5.1.24, reboot, and then Administrator works again.

Please: next time choose the correct forum for the discussion! This should have been a post in the "Discuss the 5.1.28 Release" topic. Failing that it should have been a post in "Windows Guests". It has no business being a post in "Windows Hosts"!

Moving this to "Windows Guests".

There are reports that switchong off 3D acceleration stops this error from occuring. See the ticket #17082 mentioned above.

This bug scared the living daylights out of me since it coincided with the Nyetya Trojan infiltration of CCleaner that I had running on that guest. Thankfully, Malwarebytes detected it early and prevented it from doing any damage. The only thing that spared me from having a heart attack is the fact that I have multiple real and guest Windows systems and by applying simple logic I came to a conclusion that it must be a VB related issue. I expect this to be on the top of the list of bugs that should be squashed as soon as possible, LIKE BY YESTERDAY!

Thanks!

Franc Drobnič wrote:There are reports that switching off 3D acceleration stops this error from occuring. See the ticket #17082 mentioned above.

I just used this suggestion and it did in fact stop the error in VBox 5.1.28 Win 10 PRO x64 1703. Thanks for the band-aid will monitor ticket for permanent solution

People are commenting that 5.1.29 fixes their problem, but that is not the case for me. Disabling 3D acceleration fixes the problem for me.

Disabling 3D acceleration also works as a temp fix for me with my Win10x64 VMs.
I've now downgraded to guest additions 5.1.26, re-enabled 3D acceleration and now am back to normal operations.