Fix GRUB dual boot issues after upgrading Kali Linux

To fix GRUB dual boot issues after upgrading Kali Linux, you can either use the command line to update GRUB or use a tool like Boot-Repair. If you encounter GRUB Rescue, you'll need to identify your partitions and set the root accordingly before loading modules. Disabling Secure Boot in the BIOS can also help if you're having trouble with the boot process. 

Updating GRUB via Command Line

Boot into Kali Linux: If you can't boot into Kali directly, use a live USB or CD to access a live environment. 

Open a terminal: Navigate to the terminal application. 

Identify Windows partition: Use sudo space- proper to find the partition where Windows is installed. 

Update GRUB: Execute sudo update-grub. 

If Windows is not detected: If Windows is not listed, edit the GRUB configuration file:


    Open /etc/default/grub with sudo nano /etc/default/grub. 


Add or uncomment the line GRUB_DISABLE_OS_PROBER=false. 

Save the file (Ctrl + X, then Y, then Enter). 

Run sudo update-grub again. 


Reboot: Restart your computer to see if the changes have taken effect. 


Enable case sensitivity on NTFS formatted disks

NTFS case sensitivity can be enabled on a per-directory basis, and this setting is inherited by newly created sub-directories within that directory.

To enable case sensitivity for a directory and its future sub-directories:

Open an elevated Command Prompt or PowerShell:

Right-click the Start button and select "Windows Terminal (Admin)", "Command Prompt (Admin)", or "Windows PowerShell (Admin)".

Execute the fsutil command:

Use the following command, replacing <path> with the full path to the directory you want to make case-sensitive:

Code

fsutil.exe file setCaseSensitiveInfo <path> enable

For example, to enable case sensitivity for a directory named C:\Projects\MyProject:

Code

fsutil.exe file setCaseSensitiveInfo C:\Projects\MyProject enable

Clone succeeds but checkout fails due to longer file name issue

After cloning complete repository checkout fails, core reason is Windows MAX_PATH Limitation (260 characters. Older Windows versions (pre-Windows 10, version 1607) and default configurations in newer versions impose a 260-character limit on file paths.

Solution:

Enable Win32 long paths in Group Policy:

Open gpedit.msc (Local Group Policy Editor).

Navigate to Computer Configuration > Administrative Templates > System > Filesystem.

Enable the "Enable Win32 long paths" setting.

Configure Git to use long paths:

Open Git Bash or Command Prompt as Administrator.

Run the command: git config --system core.longpaths true


Note:

Before running the command "git config --system core.longpaths true" you have to run terminal as administrator. To do that press win key + x and click the Windows terminal(Admin) option

Fix GRUB dual boot issues after upgrading Kali Linux

To fix GRUB dual boot issues after upgrading Kali Linux, you can either use the command line to update GRUB or use a tool like Boot-Repair. ...