[Intro]
Windows 11 in FAT32
Windows 11 understands both NTFS and FAT32 disk partitions. System can safely read from these partitions of the disk and write any data.
Previously, the system could be easily installed on FAT16/32 and NTFS partitions. But with the release of Windows Vista (2006), the NTFS format partition became mandatory.
And then I thought: why not remake the partition that has Windows 11 from NTFS to FAT32? Therefore, today in the video we will consider this :)
Yes, this is all done in a virtual machine. First, we need to create a snapshot of the Windows 11 virtual machine.
Next, we go to the second virtual machine, to which we will connect the "drive" with Windows 11.
We indicate the path to our disk. Yes, because of the snapshots, we have files of the VM hard disk with numbers at the end - we do not touch them
The drives are connected successfully. Now you can convert. Standard software will not be able to do this, so you have to use a third-party one :(
And it is called AOMEI Partition Assistant. Select our drive and click "NTFS to FAT32 Converter"
The FAT32 file system has some limitations: you cannot store files larger than 4 GB; you cannot create a partition larger than 32 GB and "NTFS Compression" is not supported. NTFS itself does not have such restrictions.
After the conversion is complete, you can restore the virtual machine.
At first, there are no bugs, everything works well. But suddenly the system starts to slow down slightly
And after some time, Windows begins to inform us about errors on the disk and offers to urgently fix them.
Folders can be created, but files are not. The system speaks about the impossibility of reading them.
UWP apps like "Photos" and the like stop working And why is not said.
The system starts to slow down more and more and eventually...
The system gives us BSOD.
And after that comes troubleshooting, which simply doesn't work. (behind the scenes, I waited about 30 minutes for the verification to complete and no results)
I didn't think the system would crash so quickly. Ok, this was the first try.
I didn't think the system would crash so quickly. Attempt №2
All the same disk errors, the system also slows down. But there is no load on the disk 0_0
Attempts to view various folders on the system end up as follows.
Attempt №3
Some programs cannot be opened through the command line. But I can navigate through folders
But as it is worth making a request to view a folder (for example, making a command to select a file to open), then Windows instantly crashes
Last attempt. Attempt №4
I think there is simply no point in further checking. The system crashes into BSOD by itself: at first it starts to slow down, and then stops working
That's all I wanted to show! Hope it was interesting. Until next time!
Subscribe. The names of all musical compositions are indicated in the description!