4 ms·

Not shocking. I'm writing this out of my Ubuntu partition and I'm running Windows 10, forced down my throat to begin with, and it just does what it wants when i

by native 10y ago

Not shocking. I'm writing this out of my Ubuntu partition and I'm running Windows 10, forced down my throat to begin with, and it just does what it wants when it wants to. I've had times when I've gone for a break and my laptop has rebooted and installing some updates I wasn't even aware of. And I'm running Windows out of sheer necessity for the time being because I need Illustrator, Photoshop, etc.. But Microsoft has really never cared for the user, more like you'll get what we give you and like it.

wlesieutre 10y ago
I was thinking of dual booting and relegating Windows to gaming, have you had any trouble with your setup? Especially with Windows updates messing up the boot settings or wiping partitions that they shouldn't? Seems particularly risky now that MS is pushing out regular "major updates" like the anniversary update, which get handled like a system reinstall.
- native 10y ago
  I haven't had any issues at all. The only minor inconvenience I have is needing to hit Esc immediately when my laptop is booting up so I can change what I want to boot into, the default being Windows. Now I'm running all this from an HP laptop that came with UEFI and not BIOS so I had to jump through a few hoops before it worked out.
- kaybe 10y ago
  The only issue I had so far was that Mint wouldn't boot because Windows didn't actually shut down as instructed but went into default quick-boot mode, which made the Windows partition unmountable, which by default causes the Mint boot to fail. No other problems so far. I had some issues with UEFI during install as well, but it worked out somehow. Also, it seems that you can still feed the Windows 10 installer a Windows 7 key. I wanted Windows 7 initially, but the computer wouldn't have it.
  - pritambaral 10y ago
    Did you set the Windows partition to automount in `/etc/fstab` in Mint? That would make Mint think that that mount is part of the system, and since the system isn't entirely available, the boot cannot proceed. I suggest you add `nofail` to the mount options, and `nobootwait` on older that Ubuntu-16.04-derived Mint (doesn't run systemd) and `x-systemd.device-timeout=1` on Ubuntu-16.04+-derived Mint (should run systemd)
    - deleted 10y ago
      [deleted]
dredmorbius 10y ago
VM with CoW and no commits. Reboot to your known good session, always.
- pritambaral 10y ago
  Until the known good session does a small check over the internet and re-downloads and force reboots. I wouldn't be surprised if Microsoft put in code in Win10 that silently waits for an external condition (say, an HTTP response) such that the system seems "good" until then, and upon the condition renders your system unusable (at least in the way you want it).

by native 10y ago

wlesieutre 10y ago

I was thinking of dual booting and relegating Windows to gaming, have you had any trouble with your setup? Especially with Windows updates messing up the boot settings or wiping partitions that they shouldn't? Seems particularly risky now that MS is pushing out regular "major updates" like the anniversary update, which get handled like a system reinstall.

native 10y ago
I haven't had any issues at all. The only minor inconvenience I have is needing to hit Esc immediately when my laptop is booting up so I can change what I want to boot into, the default being Windows. Now I'm running all this from an HP laptop that came with UEFI and not BIOS so I had to jump through a few hoops before it worked out.
kaybe 10y ago
The only issue I had so far was that Mint wouldn't boot because Windows didn't actually shut down as instructed but went into default quick-boot mode, which made the Windows partition unmountable, which by default causes the Mint boot to fail. No other problems so far. I had some issues with UEFI during install as well, but it worked out somehow. Also, it seems that you can still feed the Windows 10 installer a Windows 7 key. I wanted Windows 7 initially, but the computer wouldn't have it.
- pritambaral 10y ago
  Did you set the Windows partition to automount in `/etc/fstab` in Mint? That would make Mint think that that mount is part of the system, and since the system isn't entirely available, the boot cannot proceed. I suggest you add `nofail` to the mount options, and `nobootwait` on older that Ubuntu-16.04-derived Mint (doesn't run systemd) and `x-systemd.device-timeout=1` on Ubuntu-16.04+-derived Mint (should run systemd)
  - deleted 10y ago
    [deleted]

dredmorbius 10y ago

VM with CoW and no commits. Reboot to your known good session, always.

pritambaral 10y ago
Until the known good session does a small check over the internet and re-downloads and force reboots. I wouldn't be surprised if Microsoft put in code in Win10 that silently waits for an external condition (say, an HTTP response) such that the system seems "good" until then, and upon the condition renders your system unusable (at least in the way you want it).