So I installed Windows 10 (works pretty well by the way), and one of the first things I did was spin up my VM’s again. That worked fine… Installed VB 5, started all the machines, yey!
Then I had to reboot… After the reboot VirtualBox told me the NIC was missing and it couldn’t select a network interface to bridge to, even though it worked fine before the reboot.
To fix this, open up the start menu, find Virtualbox and right click on the shortcut. Press Open file location. Once you’ve done that and the new window has opened up, right click on the Oracle VM VirtualBox shortcut and select Properties.
Go to the Compatibility tab.
Check off the box that says Run this program in compatibility mode for: and select Windows 8 from the drop-down.
Restart VirtualBox and check if your network interface is back
If the network interface does not show up after restarting VB, try rightclicking and choose Run as administrator from the menu.
So this other day I decided it was time to install Windows cause I had the need for some tools not running greatly under Wine, and with my SSD, dualbooting is a whole less hassle than it used to be. No more waiting 5 minutes for booting. After reading up on how to make this work, as Windows will for sure erase grub from the MBR (master boot record), it seemed pretty easy to get grub installed the right way again. So I installed Windows 7, took about an hour, then decided I would try to reinstall grub. I plugged in my live-USB and followed these simple steps:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair
This launched boot-repair which looks like this:
At first I tried the Recommended repair, but my setup is kinda awkward, I have one SSD disk with Ubuntu and Windows 7 on them, and one HDD for data, one ext2 partition and one NTFS partition.
So the Recommended repair didn’t work, so I clicked the Advanced options.
Here I just checked off the Place GRUB into option to sda (my SSD), and everything installed correctly. I rebooted, and now it all works as intended again.
By default, you’re not allowed to edit the hosts file (c:\windows\system32\etc\drivers\hosts) on Windows 7. It will give you an error message telling you you are not permitted to perform this action when you try to save the file after making changes. To make changes, click the startmenu, search for notepad (or notepad++ as I’m using here), and select Run as administrator. This will give you the permissions you need to save the file.
So, you need to reboot your remote desktop computer from work or some other place, and all that startmenu’s got for you is a damn Logout button. What do you do?
Well it’s actually quite simple.
Open up cmd.exe from the startmenu or via the run command.
Use the following commands to reboot or shut down:
- Shutdown: “shutdown -f”
- Reboot: “shutdown -r -f”
Ever been on a remote desktop session that suddenly gets windowed?
To get it back to full screen, use the shortcut Ctrl+Alt+Break