OpenSUSE Tumbleweed hangs on reboot after installation

[Davidtatu222]

At the end of my installation, it said “The system will reboot” and I clicked ok, but the system hangs on this screen.
This has happened on about 3 separate installs now, all from different ISOs.
I have verified the checksum and gpg.
First used Ventoy, then realised it can cause issues, so switched to Impression.
On my previous installs, when presented with this screen, I would just force reset with the power button, and the system would boot into the OS now problem. However, it still refused to reboot no matter what I did, getting stuck on [ok] reached target system reboot when i pressed esc.
Tried both with the GUI reboot button and sudo reboot.
Sometimes after [ok] reached target systemd reboot it would say: [104.213516][ T767] systemd-journald[767]: Failed to send WATCHDOG=1 notification message: Connection refused
[224.213558][ T767] systemd-journald[767]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
None of the above or messing around with grub configurations did anything. However, there was one exception:
When I added reboot=hard to the grub configuration, it rebooted once - I could never repeat that again.
Also had some trouble with Wifi, but this is more important at the moment.
This is really frustrating, and I really have tried everything, so I would like to get this quickly fixed or I will give up on OpenSUSE. Any help is greatly appreciated.

[OrsoBruno]

Welcome to the openSUSE Forums!
Maybe the system is trying to boot the installer on the USB again?
You may try to shutoff the system, remove the installer USB and power on again.
Or boot the installer again, there should be an option to “Boot installed system” and see if that finds a Linux system (hopefully openSUSE) on your system.
If you get at least the boot screen with a count down, you may hit “E” for edit, scroll down to the line beginning with “linux”, append a 3 at the end, hit F10 to boot and see if you at least get to a terminal login prompt; that would mean a graphics problem that might be solved by some configuration.

Knowing what make / model the system is, or at least some basic hardware description might help us understand what is going on.