virtualbox.org

You beat me to it. I've also just entered a link from that thread

I guess this is what happens when there are no volunteer moderators to link/merge related issues.

There are further reports of the same/similar issue here: viewtopic.php?t=112323

I have linked to this thread from viewtopic.php?t=112320 where similar issues have already been reported

Also seeing same problem after installing 7.1.0, i.e. loss of Guests' internet access. Returning to the 7.1.0 BETA 2 restores internet access. (Presumably re-installing 7.0.20 or whichever previous version was used will do the same).

The first Intel dual-core Pentium CPU wasn't released until 2006 so it doesn't make much sense allocating 2 Cores to a Windows 2000 VM. I would try change that setting. My basic settings on a Working Windows 2000 VM are: CPUs: 1 RAM: 512MB VRAM: 64MB I normally stick with memory/disk sizes etc. that...

Yes, you can download 'old' VirtualBox Builds using this link https://download.virtualbox.org/virtualbox/

SaltyCoffee wrote: ↑9. Sep 2024, 07:50 So now my question is, how do I kill bluetoothd?

That's not really a VirtualBox question. The information needs to come from Apple (or a trustworthy third-party specialist source) e.g. https://support.apple.com/en-gb/guide/m ... th1008/mac

Providing the Oracle guidance on applying security permissions and disabling directory inheritance are correctly input for the 'new' parent folder(s) on the alternative Drive, there shouldn't be any impact on other folders that may sit alongside that top level structure, but I would always create a ...

Microsoft/Windows 10/11 Security restrictions no longer make what you want to do straightforward, but there is guidance in the VirtualBox User Manual Section 3.1.2 on how to create an alternative installation location for VirtualBox with the required permissions. Alternatively you could consider mov...

Please see the VirtualBox User Manual 7.0.20 Section 5.4.1 for details of the D'n'D supported formats. They don't appear to include your scenario, unless I'm not following your explanation of the 'problem' correctly.

The message indicates that the "Win.iso" file is not recognisable as a Windows installation ISO, i.e. There's something something 'wrong' with with the file.

The greyed out entries suggest that the VM is/was running when you attempted to change the settings. If that's correct, then VMs have to be shut down (not running, or save state) to be able to change settings.

See https://kb.parallels.com/129918 - The second Part is for Intel Mac VM's

@Tid

Did you have Parallels Tools installed when the VM was running on that platform? If "Yes" did you remove the "Tools" installation before attaching the hdd file to a VirtualBox VM?

What do you mean by "I removed the VDI"?

The vdi file is the VM's 'hard disk' so it is certainly not going to be able to run if it can't find it. Put it back and try again.

If you don't still have the original vdi file, or a full backup of the VM Folder then the VM is 'dead'.