Win 10 not booting after upgrade

[nilsA]

Win 10 not starting after upgrade

Hi, I upgraded from Win 7 to Win 10 yesterday. Everything fine - except the startup screen said Win 7, not Win 10.

So, I took the first thing I remembered (Kubuntu has just worked for so long I tend to forget what I once knew) -

SUDO APT GET AUTOREMOVE

This gave me the option Win 10 Booloader,

but Win 10 will not start.

As Win 10 did work after the install, I guess the problem is on the Kubuntu side here?

Someone knowing what is going on here?

[jlittle]

...
SUDO APT GET AUTOREMOVE

That's nothing to do with your problem (as well as being wrong in that it needs to be lowercase, and the command is "apt-get").

I suspect you mean

sudo update-grub

Is that what you did?

Regards, John Little

[Qqmike]

Yeah, and we don't have much information, do we?
The computer -- is it fairly new or purchased before, say 2010?
BIOS or UEFI booting?
What was existing? Windows 7 and Kubuntu, dual-boot?
Then what? You simply updated 7 to 10?
It won't boot Windows 10? =>
That sounds like a problem with Windows and its bootloader, not Kubuntu.
(In fact, after installing Windows 10, you would think that Windows 10 would take over your computer's booting!)

One thing about it, if you can boot into Kubuntu, open Konsole, and issue two commands, it might fix this, and if it doesn't fix it, that would be puzzling:

At Konsole (in Kubuntu),
sudo grub-install
and then
sudo update-grub
and then re-boot.

Another tool (without knowing more about the problem) is Boot Repair,
https://help.ubuntu.com/community/Boot-Repair

[Teunis]

That's nothing to do with your problem (as well as being wrong in that it needs to be lowercase, and the command is "apt-get").

Regards, John Little

Since a while there is a new command 'apt', have a look at the man pages.

[Teunis]

jlittle was correct in that

sudo apt autoremove

has or had nothing to do with your problem.
Autoremove just removes unused packages that are only taking space.


I believe that in your 2nd post you said it was Win10 that booted, meaning only the label was wrong?

All what would have been needed is to update Grub from Kubuntu, Windows is too simple to fix it by itself.
The update grub command will check for any bootable OS's and place them in the boot screen.

At this point it looks like you need to repair grub as per Qqmike's post.

[jlittle]

Since a while there is a new command 'apt', have a look at the man pages.

Yes, I use it all the time, it's slightly friendlier than apt-get. The OP said he used "APT GET" though, there's no "get" argument to apt, and on my Vivid apt does not support "autoremove".


Regards, John Little

[Teunis]

Oops I overlooked that one, sorry John!