Moving to Linux From Windows: 6 Costly Mistakes to Avoid

Moving to Linux from Windows usually goes wrong in the boring places, not in the installer. Picking a distribution and clicking through the setup takes an afternoon. What costs time later are the habits and files you bring with you: scripts saved in Notepad, a FAT32 USB stick, file names that only differ in case, and a Windows disk that Linux will only open read-only. I reproduced each of these on Debian 13 with real files and disk images, so the errors below are the ones you will actually see.

Moving to Linux from Windows: CRLF script error, FAT32 4 GiB limit, case-sensitive names and reading an NTFS image
Real lab output: four Windows habits that fail after moving to Linux.

Before moving to Linux: try it without risk

Before moving to Linux for good, start with a live USB or a virtual machine and use it for real work for a week: your browser, your editor, your printer, your VPN. Write down every program you open on Windows and find the Linux version or a web alternative before you wipe anything. Pick a mainstream distribution with a long support period (Ubuntu LTS, Fedora Workstation, Debian or Linux Mint) so that guides and forum answers match your system.

If you plan to dual-boot, read the next section first. It is the one part of moving to Linux where a mistake can make Windows lose changes.

Dual boot: turn off Windows fast startup

The ntfs-3g manual is direct about this: on a dual-boot computer "Windows has to be fully shut down before booting into Linux", otherwise "changes made by Linux may be ignored by Windows". Hibernation and the fast restart feature both leave the NTFS volume half-open. The manual gives the fix, run as Administrator in Windows:

powercfg /h off

It disables both hibernation and fast restarting. If either is still on, ntfs-3g mounts internal NTFS partitions read-only, which is the usual cause of "I can see my Windows files but cannot save to them".

The second dual-boot surprise is the clock. Windows keeps the hardware clock in local time, Linux expects UTC, so the time jumps by your UTC offset after each switch. timedatectl set-local-rtc 1 makes Linux follow Windows, but the timedatectl manual warns that local-time RTC "is not fully supported and will create various problems with time zone changes and daylight saving adjustments. If at all possible, keep the RTC in UTC mode." The cleaner fix is on the Windows side, so that both systems use UTC.

Scripts from Windows: CRLF line endings

Scripts are the first thing that breaks when moving to Linux. A shell script written in Notepad ends every line with CR+LF. I created one and ran it the normal way:

$ file backup.sh
backup.sh: Bourne-Again shell script, ASCII text executable, with CRLF line terminators

$ ./backup.sh
main: line 4: ./backup.sh: cannot execute: required file not found

$ cat -A backup.sh
#!/bin/bash^M$
echo "backup started"^M$

The message is misleading: the file is right there. What is missing is /bin/bash\r, the interpreter name including the invisible carriage return (^M in cat -A). Running bash backup.sh printed "backup started", which hides the problem until the script is run directly or from cron. The fix:

$ dos2unix backup.sh && file backup.sh && ./backup.sh
dos2unix: converting file backup.sh to Unix format...
backup.sh: Bourne-Again shell script, ASCII text executable
backup started

Set your editor to LF line endings for anything that will run on Linux, and set core.autocrlf deliberately in Git instead of accepting whatever the Windows installer chose.

File names are case-sensitive after moving to Linux

On Windows, Report.docx and report.docx are the same file. On Linux they are two files that can sit side by side, and the wrong case is simply "not found":

$ ls
Report.docx
backup.sh
report.docx

$ cat REPORT.DOCX
cat: REPORT.DOCX: No such file or directory

The trouble starts when you copy such a folder back to a Windows-formatted drive. In the next test only one of the two reports made it onto the stick.

USB sticks: FAT32 limits and silent failures

USB sticks are how most people carry files when moving to Linux, and most come formatted as FAT32 so that every system can read them. I made a 6 GB FAT32 image and copied files to it with mcopy, which writes to the image without mounting it. A 4 GiB file (4294967296 bytes) was refused:

$ mcopy -i usb.img video.mkv ::/
File "video.mkv" too big
[exit 0]

Note the exit code. mcopy printed the error and still returned 0, so a backup script that only checks $? would report success. FAT32 cannot store a file of 4 GiB or more; use exFAT or ext4 for large files, and verify copies by listing the target.

Two more files failed in the same run. meeting: notes?.txt, a valid Linux name, contains characters FAT does not allow; mcopy exited 1 and copied nothing (the lab gave it no terminal for its interactive prompt). report.docx clashed with Report.docx already on the stick and also exited 1. The directory listing afterwards showed one file:

REPORT~1 DOC         2 2026-11-17  13:34  Report.docx
        1 file                    2 bytes

Permissions do not survive either. backup.sh was -rwxr-xr-x; the copy that came back from the stick was -rw-r--r--. Moving to Linux with your scripts on a FAT32 stick means running chmod +x again, or carrying them in a tar archive, which keeps permissions.

Getting files off the old Windows disk

After moving to Linux, you do not have to boot Windows again to rescue a forgotten file. The ntfs-3g package includes tools that read an NTFS partition or image directly. I created an NTFS image, put a file on it with ntfscp, and read it back:

$ ntfsls -l win.img
       9 Nov 17 13:34 2026 Tax.txt

$ ntfscat win.img Tax.txt
tax 2026

$ ntfscat win.img tax.txt
ERROR: Couldn't open inode: No such file or directory

Even on an NTFS volume, these Linux tools want the exact case. ntfsfix -n checks a volume without changing it ("NTFS partition win.img was processed successfully."). On a desktop you would normally just mount the partition; the tools are useful when a mount is refused because Windows was hibernated.

A short plan for moving to Linux

  1. Back up everything to a drive formatted exFAT or ext4, not FAT32, and check the copied file list.
  2. Test a live USB for a week with your real tasks and printers.
  3. For dual boot, run powercfg /h off in Windows and decide how both systems handle the clock.
  4. Convert scripts with dos2unix and fix the execute bit.
  5. Rename files that differ only in case before copying them to any Windows drive.
  6. Keep the old disk unchanged until you have opened every important file on Linux.

For the first weeks on the command line, the Linux survival guide covers the beginner errors that come next. If you script in PowerShell today, PowerShell on Linux vs Windows shows what changes. And if you are still deciding whether to switch, read can the Linux desktop beat Windows.

Comments

Popular posts from this blog

How to Play Minecraft Bedrock Edition on Linux: A Comprehensive Guide for Tech Professionals

Linux desktop frozen? My 5 go-to tricks to try - before forcing a hard reboot

The Ultimate Guide: How to Set Up DXVK in Wine on Linux for Enhanced Gaming Performance