Trying.
You are apparently running your Manjaro system inside a virtual machine managed by virtualbox. mhwd might not work well in such an environment — we know that it doesn’t work from within a chroot, and a virtual machine isolates the target system even further.
Your problem appears to be one of badly configured mirrors. You should at least try to refresh your mirror list, and then use pacman.
Also, make sure that your virtual machine has full access to the internet — no blocked ports.
It looks similar, but no. 
the key you need is usually just under Esc on a full US keyboard - yours might be elsewhere - it looks like this: `
Installing a package should work, no? Through pacman etc. The mirror list is update (even a thousandfold, trying all of them, just continent, just geoip and so on … it doesn’t matter … all report the same so far). And of course it has full access.
Backquotes then:
https://imgur.com/Ba2gF9z
https://imgur.com/rt84Lz2
1 Like
Just rebooting after the install. Yet to perform the first system update and then switch to Testing.
Changing to the Testing branch and/or limiting the mirrors to your geolocation does not refresh your mirrors. You explicitly need to refresh them. 
sudo pacman-mirrors -f
I also gave you the command to download your files database…
sudo pacman -Fy
You may even use -Fyy in this case, because obviously there is something not right with your database.
The error messages you’re getting are all pointing at the package not being found on the mirrors.
Interesting. At this point, no mirrors will resolve. pacman-mirrors sorts the list but pacman -Syu fails to retrieve databases. On Stable at this point. Perhaps it’s an issue with VirtualBox on Windows (currently 7.2.0 r170228).
1 Like
@Voon, are you still there?
Is the computer you’re working from connected to Internet viia Cloudflare or any type of VPN?
Deactivating that allows pacman (via VirtualBox) to continue the update. In VirtualBox I have set it to NAT (which should ideally be the default in any case).
Fun fact. VMware has no issue with VPNs.
If the virtual machine does not have an nVidia GPU, Manjaro Settings Manager GUI or mhwd would not be able to install nVidia drivers
pacman-mirrors would confirm if the vm is using testing branch and mirrors are up to date
pamac info nvidia-utils to check version number is consistent with latest testing branch packages
Text from terminal commands should be posted as preformatted text using </> button in reply box or Ctrl+E on keyboard
At lunch will get back
Good point. I hadn’t thought of that. But isn’t that what the guest additions are for if the host machine has an Nvidia GPU or some other problematic hardware? 
The OP is not at home at the moment, and they have no access to their computer. They probably took those screenshots before they left for work. 
Oh, OK. Something light for me, thanks, maybe a sandwich. I don’t know what the others prefer.
Irrespective of Nvidia, the problem accessing mirrors was an issue in itself.
1 Like
1 Like
Summarizing a few answers to the comments here (also thank you very much for trying to help!):
-
I did run pacman-mirrors -f and pacman -Fy now. I did indeed not see that comment, sorry.
-
It did not help, I get exactly the same issue with pacman -Syu nvidia-utils (i.e. it wants to download 575, not 580)
-
I understand mhwd, being a video-made-easy supercommand, will not fully work, since I assume it tries to probe the devices and thus fails on VirtualBox. I assume pacman should work, though?
-
I am not aware of any VPN or anything in bewteen. Virtualbox runs fine, I can do anything internetrelated there (websurfing, any other command like all the pacman commands etc). The mirrors are also not unreachable, they just fail to download the wrong package I guess. I’m using NAT in VB settings for this virtual machine.
-
I can’t copy paste output, unless someone can tell me how to get bidirectional clipboards of VirtualBox working in arch/manjaro. hence my screenshots.
Hope this helps 
They have never worked well under any OS.
No - I mean yes, pacman will work, but - in a VM you do not have a NVIDIA card therefor the driver will not work.
Anyhow this is not the solution why you “see” the outdated driver in testing
2 Likes
VM screenshot of mhwd has a warning that no matching device was found
but mhwd failed to install nvidia-utinls=580.82.07 because it requires lib32-nvidia-utils
Branch compare - lib32-nvidia-utils
stable :575.64.05-1
testing :580.82.07-1
unstable :580.82.09-1
Sure, the NVIDIA driver won’t work in VirtualBox. I never intended that I only use VirtualBox to try and recreate the errors I have at home or to see if it behaves the same, so I can report that here … I don not expect VirtualBox to do anything with the nvidia driver.
Well, attempting to install nvidia-utils (but obviously not completing the process) produces the same result as the screenshot you posted earlier.
What comes to mind is that if nvidia-utils has only just reached Testing, and if the mirror used isn’t yet up to date, that could explain why we (both) see 575.64.05-1 offered.
You could check the actual mirror used against it’s current Mirror Status to see if that argument holds water, but even so, this isn’t definitive.
At this point all I can offer is