core 157 update only grub showing up help
i’ve upgraded from core 156 to 157 and now i’m stuck at

grub>

what can i do now?
it looks like the updater was running twice and wiped the kernel from your system.

you will find a backup in /var/ipfire/backup which you can restore after performing a fresh installation.
only thing i can think of is to maybe reflash the firmware. what to do::

docker exec -it gitlab /bin/bash

then

apt install update-manager-core

then

do-release-upgrade thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … re-flash bios using usb stick if you can get that far.
if not reset option and steps like clearing cmos and pins.?
new mobo or try manufacturer.. have you tried entering safe mode? Let us know if it is the same.



It could be corrupt files and not startup programs. hi mike, thanks for bringing this to our attention, i can confirm that i’m aware of this issue and a fix is in progress. i expect the latest version to be available the debian/rpm repositories in the coming days.

one short term work around would be to download the .deb or .rpm file directly from th… you need to change the boot order so it checks the HDD before the floppy, cdrom etc...



btw a new pc means you will have to reinstall windows if drivers are uptodate it will not show onto the list. else start the utility with 'run as administrator' option and see if it's working. maybe the boot disk partition be cleared. you can disable emmc in bios then install a pure windows in ssd. enable emmc after the windows installed. sometimes one or both of these patches help, especially if the system is showing high ram and/or cpu usage when checking updates:
https://support.microsoft.com/en-us/kb/3050265




https://support.microsoft.com/en-us/kb/3102810﻿﻿
﻿