jefro which hackers, the Linux ones or Windows?

computersavvy, I checked in BIOS and I cant see any thing. I entered BIOS and checked security and advanced tabs and found nothing on TPM. afterwards I checked everywhere still found nothing.

The first command output indicates you have an EFI partition with efi files for windows, some debian version as well as kali. Did you copy/paste the command in a terminal? The output should be either EFI or Legacy. Another thing you can try is to see if you have that directory by running this command (ls /sys/firmware/efi) or simply navigating to that
directory in a file manager.

I see in an earlier post that you are using a Lenovo and I see "2012" in your post. Is this a new computer or was it purchased used. I asked that in an earlier post anddon't see a response?

If this is a newer computer with EFI, you should see a reference to TPM somewhere, probably under a Security tab if you have one.

It would also be useful for you to post information on the drive(s), are they GPT or msdos. Use sudo parted -l command to get that info. It will show partition table either gpt or msdos.

I don't understand your comments about booting and being given the option to go to Kali or the BIOS. You should on boot, have an option to go to one time boot option key or to another key to access the BIOS. Generally, a message showing these options will show on screen for a few seconds (doesn't always show though) before you get to the boot menu for Kali or whatever you are using.

One thing you wrote is confusing me.

I have never been able to get the bios after the os starts. Bios, Basic In Out Subsystem.

Could you please describe to me what you are doing, more details please.

Maybe I live in a wardrobe, but I can't remember seeing that.

I think that is the bios, not kali, what you see is part of the boot menu..., it may show usb file systems as well, if one was plugged in.

I'll check my live-kali memory stick. I hope this helps you.

Hi.
What you have is a kali "bios" boot version <edit> of the ISO </edit>.

The other popular boot is UEFI. Like for window$ security...

So, it's not the actual bios you are accessing.

You need to reboot whilst contiually tapping the key F1, F2, the key changes from make to make.

leave the usb stick untill you configure the bios, then you should have better progress.

I can invoke the bios boot menu with F8. If a bootable usb stick is recognised it will usually show up in the menu.

But what you are seeing is a "name" for boot type. BIOS/UEFI

I have a feeling that there's more you'll need to figure out, like secure-boot... and UEFI (I disable it completely, even on my laptop).

Well I decided to reset Bios. once I did that. This BSOD took precedence over everything else. Now its a full blown loop of poop. about 7 years ago I took out the hard drive from my Windows Millennium and replaced it with another drive from one of my sons computers and the first thing it did was update this windows 8.1 to windows 10. of course since it was out of its environment it developed a watermark and periodically I got messages stating I need to purchase the OS I had bought both computers new and was not about to comply with that. Ultimately I clean installed Peppermint on it. when a computer gets BSOD is this BSOD originating from some other device? It couldn't be BIOS that's ROM. has the culprit component installed something on the hard drive so that it is inherent so that if you took the drive out and put it in another machine turned it on and then voilà deja vu? Could removing and reformatting potentially resolve the loop? I'm not necessarily trying to resolve everything just trying to get out of the loop. and it looks like I'm going to have to get in the box to do that.

Your situation described in the above post with moving the hard drive from one computer to another with a windows OS is expected because the OS is tied to the specific hardware. The OS is licensed (basically rented) to be used on specific hardware. In some situations, such as hardware failure, it could be possible to use it on another machine but I believe the user would need to contact Microsoft to get permission to use it on another machine.

The above quote is what you posted in an earlier post and it means you still have remnants of windows on the EFI partition. That is why you see "Microsoft" as a directory in the EFI partition. Installing any Linux will create another directory on that partition which you can see as you have both debian and kali there. An EFI install will not (or should not) overwrite other directories on that partition. You could try removing the files from the EFI/Microsoft directory and then the Microsoft directory to see if anything changes.

The link below discusses reason for getting the windows error code you mention. It also, further down the page, gives some ways to try to repair. Not much point in reading that as you don't have windows and need it to do the repairs. Basically, the general problems are the hard drive not detected or corrupted BCD boot files.

https://www.easeus.com/resource/erro...0xc00000e.html

Some questions asked earlier which I see no answer to. Is this a new machine? Was it purchased with windows 11 as the pre-installed OS? Did you see that strange prompt prior to installing the Kali whoami software. One of the things it does is to change the hostname as mentioned at the link I posted earlier. I don't know if it makes a permanent change or if it regularly changes it??

That file resides on the windows system partition and would be an expected error when you select windows in the boot menu as you have overwritten the windows filesystem partition.

When you run the command below do you see GPT to the right of Partition Table?

When you run: sudo efibootmgr -v, do you get output showing various entries for efi boot? You should still see entries for windows as well as whichever Debian derivative you previously installed.

If you want to try Kali and Kali only on the drive and have nothing on it you want to save, format the EFI partition to overwrite data, then reinstall Kali and you should then have only the Kali directory in the EFI partition and the OS / on another partition.

1 members found this post helpful.

OK, I know as much about peppermint, but the blue screen is just a very small file from your dirty harddrive.

A clean install means reformat thye entire harddrive.

If you don't do this you will need to download a UEFI version of kali.

The kali I have was from an "install" iso, not LIVE-iso.

I think you will need to check the bios for fastboot, and other M$ propriety JUNK.

IMO, I would use dd to remove any thing from the boot record MFT/MBR like this...
some more easy to find info on dd...
I know it feels risky, but if you dabble in hacker stuff hackers will be attracted to you, you're going to find it.

Just get a desktop OS for your computer.

All the best.

When you get through all that... you will need to format the disk during installation.

Make a separate partition for /home, so if you have to re-install an OS your files may be kept.

Make sure you install grub to the / of you install... not the memory stick, or /boot/

Cheers.

GlennsPref when I was installing Kali I entered into bios to set boot priority and the bios looked just like the bios you're talking about and it was your letter that got me thinking about using the keyboard to access BIOS I had entered BIOS many times before, that's how I installed these two Linux OS's as well* as Ubuntu, Mint, and Peppermint years ago. The computer that I put*Kali on was an estate sales purchase and prior to putting Kali on it. I installed a password for the Bios which remained there even after the Kali install. so when I started the computer up I had to enter the BIOS password and then came up a box where I would enter my name and password for Kali and then I would be presented the option of going to either Kali or Bios. I never went to BIOS on this OS install until I came on board this* forum and it was mentioned and the option was right there on the initial boot up so I took it. never once thinking I might need to try another route to see if the two* are the same.* I realized they were not the same through Kali* I got BSOD and through F! & F12 I got BIOS.* I'm wondering* if the option to go to bios or Os would be something not available to virtual or live os? I have a BIOS boot version of Kali. Could I have installed it using UEFI? How would you do one vs the other? I thought they were sort of integrated. Right now it is 21:40 central time. Several minutes ago I turned on my Kali computer and put in my BIOS password. wherein the screen goes black and i have a white box with the following message. "secure Boot Violation Invalid signature detected. check secure boot policy in set up" and after that message an "ok" button at the bottom which doesn't do anything: ok already ok ok ok! after a while it responds and then I finally get to the classic all time favorite BSOD. I won, I won I won weeeeee! I look online for counsel on how to deal with BSOD. So far everything I see addresses the issue* from the standpoint that I was in the BSOD but now I'm not. Wherein reality I'm still in BSOD therefore I can't do the things they're telling me to do. prop wash

yancek this machine is an all in one 2012 so its 11 - 12 years old. It was bought at an estate sale and it came with windows 10 on it.* It has about a TB of memory. I bought one similar to it at an estate sale also right around a TB but this one was given to a grandma who never used it. It was still Windows 8 and that was last year.* I tried to upgrade it to 8.1. I just got my butt kicked, made absolutely no headway,* finally microsoft stepped in and asked If I would like to go to 8.1 so microsoft took me to 8.1* and from there I brought it into 10 where it stays today. my mother was on it tonight when I called her.* When we reach 10's eol If it's still working I'll move it to a Linux distro. So I want to clarify shortly after I got the computer that I put Kali on, before I put Kali on it, I put passwords on it, mind you this was while it was windows 10 I even gave it a BIOS password which stayed with the machine even when I clean installed Kali so when it was working* I would boot it up.the* first thing I would have to do is put my BIOS password in, after that a box would come up for Kali. I would put my name in and my password then I would be presented with the choice of entering BIOS or Kali and I always went to Kali until I realized through this forum that my problems may be originating from BIOS. since the option to enter BIOS was available from the newly installed OS I used it instead of going via F1 etc. When GlennsPref suggested using the keys instead the thought crossed my mind that's trouble shooting making sure that both routes reach the same destination. smart thinking. when I entered BIOS from OS I got BSOD when I came in via F1 I got BIOS I thought to myself this thing ain't real so I reset BIOS on the machine and now the BSOD is here. Now I can't get to the OS. BSOD has finally arrived. earlier today I turned on my Kali computer and put in my BIOS password. wherein the screen goes black and i have a white box with the following message. "secure Boot Violation Invalid signature detected. check secure boot policy in set up" and after that message an "ok" button at the bottom which doesn't do anything: so I keep pressing it after a while it responds and then I finally get to the classic all time favorite BSOD. you got a love it.

yancek this machine is an all in one 2012 so its 11 - 12 years old. It was bought at an estate sale and it came with windows 10 on it.* It has about a TB of memory. I bought one similar to it at an estate sale also right around a TB but this one was given to a grandma who never used it. It was still Windows 8 and that was last year.* I tried to upgrade it to 8.1. I just got my butt kicked, made absolutely no headway,* finally microsoft stepped in and asked If I would like to go to 8.1 so microsoft took me to 8.1* and from there I brought it into 10 where it stays today. my mother was on it tonight when I called her.* When we reach 10's eol If it's still working I'll move it to a Linux distro. So I want to clarify shortly after I got the computer that I put Kali on, before I put Kali on it, I put passwords on it, mind you this was while it was windows 10 I even gave it a BIOS password which stayed with the machine even when I clean installed Kali so when it was working* I would boot it up.the* first thing I would have to do is put my BIOS password in, after that a box would come up for Kali. I would put my name in and my password then I would be presented with the choice of entering BIOS or Kali and I always went to Kali until I realized through this forum that my problems may be originating from BIOS. since the option to enter BIOS was available from the newly installed OS I used it instead of going via F1 etc. When GlennsPref suggested using the keys instead the thought crossed my mind that's trouble shooting making sure that both routes reach the same destination. smart thinking. when I entered BIOS from OS I got BSOD when I came in via F1 I got BIOS I thought to myself this thing ain't real so I reset BIOS on the machine and now the BSOD is here. Now I can't get to the OS. BSOD has finally arrived. earlier today I turned on my Kali computer and put in my BIOS password. wherein the screen goes black and i have a white box with the following message. "secure Boot Violation Invalid signature detected. check secure boot policy in set up" and after that message an "ok" button at the bottom which doesn't do anything: so I keep pressing it after a while it responds and then I finally get to the classic all time favorite BSOD. you got a love it.

A BIOS password will stay with the machine regardless of which or how many operating systems you have, install or remove from the machine. You need it to make changes to the BIOS such as changing the boot order to boot from a usb device to do an install. If you don't need to make any such changes, you won't need the password. This information is stored on the system board and doesn't change with different operating systems. So there should be no need to do what you describe, entering your BIOS password every time you boot and I've never seen the behavior you describe on any Linux:

The question I would have, has this been the behavior you have seen since the first install of Kali?
Another thing which may help someone to help you, could you post the actual exact name of the Kali iso you used?
The date of the manufacture (2012) is about the time UEFI began being used by Microsoft and your earlier output indicates an EFI partition. When you access the BIOS, do you see references to UEFI, mostly under Boot or Boot options?

If you reset the BIOS, it was reset to factory defaults. Doing this should not delete any data on the drives but since the computer came with windows 8 originally and you installed Kali afterword, neither will be accessible with factory defaults. Did you do research on what a factory reset would do?

My suggestion is (if you still have it) to use the Kali usb (or another Linux if you have one) to boot it and once booted from it (I'm not sure if you will still need your BIOS password?) open a terminal and post the output of sudo fdisk -l. Does it show your partitions? If it shows your Linux partitions, you may be able to reinstall it or reinstall Grub. If you are unsure about how to do this, post the output here and you should get help.

When in the BIOS after the reset, do you see an option to turn off Secure Boot or is it the message you quoted above and no options? Seems a bit off to me after just resetting the BIOS but?? So, if I understand your current situation, you can now NOT boot anything and cannot access anything in the BIOS, is that correct?

1 members found this post helpful.

Hi,
The bios is on the mainboard.
The system stops and gives you the option, do you want to proceed with the boot-order? Or, do you want to enter bios setup?
Perfectly normal. You may get complaints from the bios at boot, but after that you should be able to access the bios when no-drives are connected. If you have a bootable drive inside the machine, the bios should see it and try to boot from it.

I have little experience with boot passwords, with bios or grub. (if your not careful you'll spend all your time typing passwords)
The bios is there on the mainboard, it comes first. That's how you can use the "Enter" key, or any keys, because the bios knows how to use your peripherals (keys, monitor... etc. but BASIC (bios). Any and all data drives connect to the mainboard... all data drives are mapped, and include any new drives (for that boot). A virtual machine requires a Host OS, so it comes after the OS init.


if it bios or uefi, try the different ones over time.

...turn off Secure-Boot in the bios may help get past that error.

GlennsPref I was able to get into BIOS and removed the password and then entered into a UEFI Kali install and once it was done entered restart and as of now I have no BSOD. Kali's back.

1 members found this post helpful.