Installing Windows as dual boot on Linux computer

I am currently having my Dell XPS13 with Ubuntu 18.04.2LTS installed, and I am very happy with it (mostly doing dev stuff). Right now I am using a Windows VM whenever I need to use Windows application.

However the amount of applications without Linux support I have to use is growing so I decided to set up a dual boot system.
I installed a dual boot setup based on a Windows machine before and I read that this is the recommended way is to:

  1. Install Windows
  2. Add Ubuntu

So I was wondering what the best way is to realize this setup while keeping everything from my Ubuntu system (files, applications, …).

My thought is that I’d have to completely clone the system and create an .iso and use this one to install Ubuntu instead of the default one.

I just wanna know if any of you have done this before and what your process looked like (before I completely mess up my system).


Or at least I will create a backup so I can restore my Linux enviroment at any time.

Unable to ping to or rdp to KVM windows 7 guest but able to ping to other linux guest centos

Unable to ping to only Windows guest. able to ping to other guest.

HOST os Ubuntu 18.4.2

What i did so far- Tried to change device to virtio,rtl8329,e1000

Internet is working on guest.

Windows 7 guest firewall disabled.

installed virtio driver for windows from -https://launchpad.net/kvm-guest-drivers-windows/+download

https://ubuntuforums.org/showthread.php?t=2308987

from host able to ping to centos guest in same network and host.

Here is network configuration of host.

root@hp-e840-g1:/var/lib/libvirt/dnsmasq# ifconfig  br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet6 fe80::3832:b6ff:fed3:b592  prefixlen 64  scopeid 0x20<link>         ether 3a:32:b6:d3:b5:92  txqueuelen 1000  (Ethernet)         RX packets 0  bytes 0 (0.0 B)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 1272  bytes 213475 (213.4 KB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  br0:avahi: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 169.254.10.198  netmask 255.255.0.0  broadcast 169.254.255.255         ether 3a:32:b6:d3:b5:92  txqueuelen 1000  (Ethernet)  enp0s25: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500         ether d0:bf:9c:1f:6d:7b  txqueuelen 1000  (Ethernet)         RX packets 0  bytes 0 (0.0 B)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 0  bytes 0 (0.0 B)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0         device interrupt 20  memory 0xd0700000-d0720000    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536         inet 127.0.0.1  netmask 255.0.0.0         inet6 ::1  prefixlen 128  scopeid 0x10<host>         loop  txqueuelen 1000  (Local Loopback)         RX packets 18229  bytes 1627449 (1.6 MB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 18229  bytes 1627449 (1.6 MB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255         ether 52:54:00:f6:8c:87  txqueuelen 1000  (Ethernet)         RX packets 27291  bytes 1676922 (1.6 MB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 21479  bytes 53057319 (53.0 MB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet6 fe80::fc54:ff:fe63:38bc  prefixlen 64  scopeid 0x20<link>         ether fe:54:00:63:38:bc  txqueuelen 1000  (Ethernet)         RX packets 404  bytes 44813 (44.8 KB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 358  bytes 23713 (23.7 KB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet6 fe80::fc54:ff:fe05:1413  prefixlen 64  scopeid 0x20<link>         ether fe:54:00:05:14:13  txqueuelen 1000  (Ethernet)         RX packets 634  bytes 50098 (50.0 KB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 8973  bytes 667052 (667.0 KB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 172.20.10.5  netmask 255.255.255.240  broadcast 172.20.10.15         inet6 fe80::2064:887d:4812:fd7d  prefixlen 64  scopeid 0x20<link>         ether ac:fd:ce:00:c4:6d  txqueuelen 1000  (Ethernet)         RX packets 105684  bytes 110034160 (110.0 MB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 70214  bytes 9358661 (9.3 MB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 

any help really appreciated! Thanks

Dual Boot: Windows or Ubuntu Default

I installed Ubuntu 18.04.1 LTS along side Windows 10 with a dual boot which works perfectly. But the grub menu defaults to Ubuntu. Since I’m new with Ubuntu I’d rather have it default to Windows. I’ve searched this forum for two days and can’t find how to do that – assuming it’s even possible. If the question has been answered a link to it would be helpful.

After installing Ubuntu 18 alongside Windows 10, all Windows GRUB options result in Windows starting recovery mode

thank you for your time. I have installed ubuntu on my hard drive while Windows lives on my SSD. After installing Ubuntu (which works flawlessly), using one of the (many) windows options in GRUB results in Windows starting recovery mode or failing an automatic repair. I tried using the BootRepair tool from within ubuntu with the recommended settings but that didn’t help. Its output is in https://paste.ubuntu.com/p/zsqpgBC9tP/ (although my Windows version is definietly 10, not 8). Reading the output, choosing /dev/sda3 at boot should result in Windows starting, but it doesn’t. I am new to personal linux (have worked on servers before) and am not sure what to try next. Thank you again for your help

Does the filesystem windows is installed on have an effect on the time zone settings of windows registry timestamps?

As far as I know Windows Registry timestamps are stored as UTC timestamps when Windows is installed on an NTFS filesystem. Does this change when Windows is installed on a FAT Filesystem (e.g. FAT32)? Are timestamps stored as local time instead or are they still in UTC?

Question could have also been simplified: Are Windows Registry timestamps always UTC timestamps?