Delete linux and grub

boot up with windows 7 installation media and try fixboot and fixmbr from command line.

>>222055
I did the same thing 2 days ago. For fix it, turn off ur pc and turn on and press F8 or F10 (depend of your pc) for go to the bios menu and choose wich OS u want to turn on first

>>222056
So reinstall kali to get into windows create boot usb then run repair then delete kali and grub? Or reinstall into windows, create boot usb, delete kali+grub then run repair?

>>222252
I have reinstalled kali gone into windows created repair disk,deleted kali linux from external drive and used easybcd, booted into recovery it finds windows but on my d drive(program) storage not the c drive, if i select it anyway and goto command and type "fixmbr" or "fixboot" its not recognised. Start up repair doesnt do anything either

>please help

>>222264
Fixed it was me being stupid in blind panic forgot bootrec

>>222055
You wrote the MBR to the wrong disk, or your BIOS is booting the wrong disk.

The only thing that would say "grub is missing" is grub. So clearly you failed to overwrite it.

Booting a Windows installer, pressing shift-f10 for a terminal, and using bootrec to fix the MBR will sort this out.

Also make sure to use diskpart to mark the partition with BOOTMGR on it as active, because the Windows MBR doesn't scan for it, and just runs the volume boot record on whatever partition is marked active.

>>222072
That only works with EFI, which OP is not using. Legacy mode always boots an MBR, which is a ~300 byte program whose job is to hunt down the real boot menu and try to load it.