KALI FOR THE LOVE OF GOD CAN YOU NOT BREAK YOUR BOOT PACKAGE FOR 24 FUCKING HOURS

the initrd isn't at all valid and the vmlinuz package is 0 bytes.

In 2019.
And there are some users here who ASSURED me that this doesn’t happen on linux anymore.
Jokes on them.
It NEVER happened to me with windows since 1995.

That's not a bug, but a feature. Kali is meant only for people who can solve this problem within less than a second by hacking in a metric shitton of commands.

@NoToJavaScript I think this is a Kali specific thing as I've has it once or twice on there but never on any other distro (for about 10 years)

@NoToJavaScript But then, @Fast-Nop's comment is quite true in this case 😄 I'd probably be able to solve this but I know I might encounter this kinda stuff with this specific distro!

Why are you using it anyway?

@dontbeevil Linux has absolutely nothing to do with blatantly incompetent maintainers.

@-pthread kernel's updated further than standard Debian, which is what it originally was.

@Fast-Nop the vmlinuz image is 0 BYTES. How are you fixing that with commands???

@dontbeevil i'm not even a fanboy, all 3 of the major OSes have a place.

it's just recently that all the distros i've tried are trash...

@dontbeevil I haven't made comments like that, but alright.

@dontbeevil As for your last comment, I don't get how anyone could claim that that would be a windows problem when you run something on Linux...

And for the record, I've ran the Office suite (the Microsoft one) on Linux under wine successfully!

@Parzi No idea how to fix that with commands. Then again, I would just install the Kali desktop wallpaper on Ubuntu and call it a day.

@Fast-Nop ubuntu's too full of bloat and likes to be outdated

@Parzi Well yeah, their bloat starts at their vmlinuz which probably has more than 0 bytes.

@Fast-Nop savage

@Fast-Nop Ubuntu's release model is "Why should users have to install packages? Let's just pack them all in on install!!!"

that's bloat

@dontbeevil Sure, I'd blame Microsoft for this and that would be a quite valid blaming thing.

Yes, I said Microsoft, NOT windows. Because you can validly blame the software vendor in this case (although, this might be questionable since the office suite (the Microsoft one) is not officially released for Linux) but not Windows, since this has absolutely nothing to do with this situation.

@Parzi kernel compile from source exist.

@-pthread yeah but it's more complicated to do, and also grub didn't like the output since i couldn't find the shit i had to put in it to make my laptop do what grub wanted

@dontbeevil The thing is, Windows and Office aren't open source, while Linux and bash are. Hence, the reason they don't work on the other platform properly is usually that Microsoft neither standardize their shit, nor allow anyone else to do so.
Why I think the issue is on MS side? Fist, it's the side we can't check. Second, if you have a degree in this shit, your windows instance can run up to six months without reboot. Linux can run practically forever. Tells much about MS's expertise in OS design.

@Lor-inc controversial opinion: power off PCs and laptops when not in use. Extends hardware life and makes some problems almost moot. Sure, bootup time, but also defragmentation is a thing, and (despite popular opinion) helps.

I agree with everything else, just not that part (and this is a "could, not should" disagreement)