Much of what is happening here is because windows relies heavily on NTFS junction points/hardlinks for SxS, so many libraries and resources will have "disappeared" since FAT32 has no such support for reparse points.
0:23 EFI partitions should be readable and writeable by each operating system. There are other OS than Windows, for example: Linux, *BSD, Mac OS. They don't support NTFS by default or it's built-in support is limited. FAT32 is supported everywhere because it's primitive.
nolemretaW But what if you try: put a preinstalled version of win95 on the drive, and use a modern version of Microsoft's bootloader, and let the chaos ensue.
Since Windows Vista is the first to not allow fat32 when upgrading to it. You should try upgrading to Windows vista from Windows XP‚ but on the first restart (Or before using this trick) convert the partition to fat32. Just to see if Windows Vista actually could work on fat32
This video is very interesting, I believe that one of the reasons why the efi partitions are in the fat32 file system is that in this file system it is more difficult for files to become corrupted. Well, I heard some people say that the Ntfs file system has some advantages over fat32, but Ntfs is also known as a device killer, that is, devices last less using the Ntfs file system. Thanks for the video!
0:19 “Interestingly enough, EFI System partitions still use FAT32, not sure why” The (U)EFI has to read the contents of the system partition to load the next part of the boot process. The file system driver has to be in the system board firmware. The specification specifically mentions system partitions be FAT32 (with FAT12, and FAT16 for removable media, as appropriate for capacity). I’m sure the firmware could implement other file systems, but there is little motivation to do so (certainly on the PC platform).
@@WinTips531 The UEFI specification requires that FAT32 be supported as a lowest common denominator, but there's nothing to stop the firmware from implementing other file systems if the vendor chooses to.
Ok, so my mom bought me a computer guides for kids as my 9th birthday, but it was so...outdated. I opened the "What will you need" page and it said, "you need a multimedia computer with Windows 95 as your OS". And I am using WINDOWS 10. I tried all the guides from that book and then my computer crashed.
There's actually 4 variants of the File Allocation Table (AKA FAT) format, and it was created in 1977 for floppy disks, not hard drives. The original FAT, also known as FAT 8-bit, wasn't ever used with MS-DOS, but was used for other storage systems, with a max file size of 1MB, and no listed max volume size. FAT12 (12-bit) was the original used in MS-DOS and many other DOS-based systems, with a max volume size being either 2MB or 4MB, Depending on cluster size. Max file size is the same. FAT16 (16-bit), which MS-DOS updated to in 1987, and overcame the size shortfalls of FAT12, with a max of 512MB. Max file size is 1 less byte than 512MB. FAT32, or FAT 32-bit, is the final version of the original FAT format, being introduced in 1996 with the release of OSR2 of Windows 95. Max volume size is 2TB, max file size is also 512MB - 1B. exFAT, or Extended FAT, is a continuation of FAT32 created in 2006, with larger limits and being more optimized, max volume size is 16PB, with the max file size being the same. LEGEND: MB = Megabyte (1,000,000 Bytes) TB = Terabyte (1,000,000,000,000 Bytes) PB = Petabyte (1,000,000,000,000,000 Bytes)
I think the reason EFI partitions are FAT32 is because any operating system can read it natively. Same reason that flash drives are FAT32 when you buy them.
Because FAT32 is a """standard""" which is """easy to support and implement""". That's why. Ah, and lobbying by Microsoft on EFI sit-ins. And restoring from a snapshot means that Windows still thinks the partition is NTFS. Accessing a FAT partition with an NTFS driver is, as you can see, disastrous. Nice idea and nice effects!
Side effects: 1. There will be a blank option (right click) 2. Files will NOT open 3. Command Prompt will be blank 4. Blank app on the start bar that does not work 5. Files will pop up with an "Open with" dialog (some) 6. Running "logoff" from Run -> BSOD :(
Since you were able to make such an drastic change to the disk while the VM was off, then restore it, I wonder. What would happen if you somehow would change the Windows version for example from 10 1909 to 10 1507 while the VM is suspended and boot up that changed VM
First of all, FAT32 wasn't supported in Windows 95 (it used FAT16) until OSR2. Connecting the VM disk image to another VM isn't needed if it can be mounted on the host as a disk (yes, a disk that can be accessed directly, not just a volume). In fact, if you use VHD format for disk images (which unfortunately isn't supported in VMware, but it does so in VirtualBox (along with support for VMDK as well as its own disk image format, VDI)), you can directly mount it on Windows without any additional software.
Didn't know Windows 10 was that broken with FAT32. Does Windows 7 behave this way too? Side note: Windows 10 can read and write to FAT32, so I'm not sure what the problem is. Perhaps it's just the lack of NTFS features.
Generous sponsor: I WANT TO DESTROY GENERIC LIFTS Me: That "generous" sponsor must have been afraid these "generic lifts" are outdated and might fall without protection.
It's glitchy because the ram and system is expecting NTFS, not fat32. If you could reset it, it would work better. Try dropping in a fat32 driver, and making the system run with that, then disable driver signature reinforcement to let it boot. Might work!
Why EFI partition still use FAT32? Becuase EFI compatible system only can read/write FAT32 as a boot partition. (not using NTFS I think thats license or file system architecture problem) This is why some EFI compatible OS used a partition called ESP (EFI System Partition, FAT32), EFI System need a OS bootloader inside a ESP partition to boot.
Here is how you actually do it you go into windows 10 setup you open cmd with shift-f10 you open diskpart you make fat32 partition you exit diskpart you type the dism command that applies the image (manual install thru dism) you reboot
It's not possible, Windows 10 doesn't even support these two filesystems, let alone the fact that it can't access them. Chances are, the same thing as in the video will happen. Or, maybe Windows 10 won't even try and just crash upon restoring the snapshot, and then it will never boot back up.
@@AngryDavid808 Actually it's possible. There is custom bootloader for Windows that will let you boot Windows 10 from Btrfs partition. Of course stability is not that great but it's working.
Reason : fat32 files requies up to 4gb, white some files on windows 10 is maybe that over 4gb. Also FAT doesn't mean fat, it's mean File Allocation Table
Only now I noticed that PS3 read FAT32-based usb flash drive which you could place games (if it's modified) or other but files aren't going to be up to 4Gb... And the PS3 came off in 2005 Lol
I formated my Phones SD Card today in two Partitions, the first formated by the Phone itself into an App storage partition, and the second in fat32 using Apps2SDs adopting partition feature.
_"Class not registered"_
-Windows 10, 2020
You need zoom to register this online class *_said nobody_*
Windows 10
2015 - 2020 R.I.P
I saw it
Microsoft Teams lessons much
@@crushedkitkatz hi
"I am not going to sponsor anybody"
This Raid Shadow Legends is sponsored by Enderman
This Enderman has been sponsored by THE enderman
The enderman was sponsored by the ender dragon
@@Clyde6790pRUclips yeah
dude, stfu
@@Clyde6790pRUclips the dragon that spits out purple balls that damage you and stays at a place and its breath makes a damage force I gueds
I don't know why... There's just something oddly nostalgic to seeing Windows crashing.
h
uhm
*VISTA*
Both
I want the classic BSOD back.
Much of what is happening here is because windows relies heavily on NTFS junction points/hardlinks for SxS, so many libraries and resources will have "disappeared" since FAT32 has no such support for reparse points.
Hard linking is also possible on FAT32, but not junction points. However, Windows API will refuse to create new linked files.
Windows 10 with 98-tier characteristics.
*Yes*
Very True
Yes
Hello black hat.
Alternative title:
Ntfs: I see Photos
Fat32: I see app friendly
Me: *oh no* don't bsod on me fat32
Edit: Thanks For 100+ Likes!
i see blue
I see *no*
what
Maybe Even 152 Likes
Next video: installing windows xp in my car
This but unironically.
@@malwaretestingfan *Yes*
2012+ Nissans with the digital infotainment touchscreen run on windows CE lol
Installing A Car In Windows XP.
@@shiloranxxer "you wouldnt download a car"
0:23 EFI partitions should be readable and writeable by each operating system. There are other OS than Windows, for example: Linux, *BSD, Mac OS. They don't support NTFS by default or it's built-in support is limited. FAT32 is supported everywhere because it's primitive.
Now try Windows 95 on an NTFS drive
nolemretaW But what if you try: put a preinstalled version of win95 on the drive, and use a modern version of Microsoft's bootloader, and let the chaos ensue.
95 on FAT16?
@@SUPABROS uhh does FAT16 exist?
@@gdalex7132 thank you for a interesting fact
@@walkiacid9265 I think FAT16 stands for FAT File System for 16 bit computers
"What failed: vmmouse.sys"
Your mouse: Get dunked
LMFAO
YOU ACTUALLY GOT THE REFERENCE :D
@@andreanna2004 unndertailelsoso4ireker
LMAOOOOOOOOOOOOOO
This is a new Windows - Windows 11! 🤓
Developer preview 🤓
Lol
@kyshau dis comment english so stop
Bruh....
And u have to pay for extra filesystem xd
Indeed. Enderman made a video about MS Codename Uranus.
3:45
When your VMware Tools Mouse Driver tries to write to Read only memory.
Windows says no
Windows 10 (FAT32 ver)
VS
Virtual Machine mouse driver trying to write to read only memory
That BSOD screen and the insta-fade to black was super well timed with the song. 3:37
Since Windows Vista is the first to not allow fat32 when upgrading to it. You should try upgrading to Windows vista from Windows XP‚ but on the first restart (Or before using this trick) convert the partition to fat32. Just to see if Windows Vista actually could work on fat32
euh yes
2:15 "Windows 10.sys" stop working
PD: I like see Windows ruined x'D
Wtf is “Windows 10.sys?” Windows 10 is NOT a driver
@@Spoudey i just want to say a extension for the joke, i already know that :V
Just a joke
@@TheNochtgamer hola :v
Ntfs: I can open file instantly.
Fat32: No but i can delete script in CMD
Me: Stop that.
Bsod: Hello
Enderman : *doing his job on his broken VM*
VMware mouse driver : *I'M GONNA END THIS SESSION'S WHOLE CAREER*
he moved the mouse out of the vm window and the driver tried to do shit but it crashed windows
well I guess enderman is one of those crazy people who have the task bar on the top of the screen
I have it on the top too
I have no taskbar
MCOskar use Linux lmao
@signvelvety stop
I have taskbar on top too
Hell yeah, Enderman posted a new video right as i was messing with Win XP virtual machine :DDDD
0:34 the shutdown was perfectly in sync
0:20
Enderman: "You can install Windows 10 only on NTFS"
ReFS: Am I joke to you?
This video is very interesting, I believe that one of the reasons why the efi partitions are in the fat32 file system is that in this file system it is more difficult for files to become corrupted. Well, I heard some people say that the Ntfs file system has some advantages over fat32, but Ntfs is also known as a device killer, that is, devices last less using the Ntfs file system. Thanks for the video!
0:19 “Interestingly enough, EFI System partitions still use FAT32, not sure why”
The (U)EFI has to read the contents of the system partition to load the next part of the boot process. The file system driver has to be in the system board firmware. The specification specifically mentions system partitions be FAT32 (with FAT12, and FAT16 for removable media, as appropriate for capacity). I’m sure the firmware could implement other file systems, but there is little motivation to do so (certainly on the PC platform).
but some newer boards surpport ntfs boot
I believe Apple specifically coded in HFS+ and APFS support into their UEFI code
@@WinTips531 The UEFI specification requires that FAT32 be supported as a lowest common denominator, but there's nothing to stop the firmware from implementing other file systems if the vendor chooses to.
Did you try changing files' properties? (like read-only or hidden) It would be interesting to see since FAT32 doesn't support those.
FAT32 is still used on UEFI partitions because it's open and easy to implement, being supported by basically every modern OS
Techinally, the ESP uses its own file system (which is based on FAT).
Windows in NTFS: I Can Work Anytime.
Windows in FAT32: "Class Not Registered", BSOD
Windows must have eaten so much, it literally ran on FAT32.
Yeah no, I have no future as a comedian.
players in gd that recognise supernova is legendary
Yes
Yes
Windows is actually getting closer and closer to supporting ext4, we just gotta wait
by that point Windows 10 would be so unimaginably bloated that the simplest Win32 applications crash on 10GHz
Ok, so my mom bought me a computer guides for kids as my 9th birthday, but it was so...outdated. I opened the "What will you need" page and it said, "you need a multimedia computer with Windows 95 as your OS". And I am using WINDOWS 10. I tried all the guides from that book and then my computer crashed.
There's actually 4 variants of the File Allocation Table (AKA FAT) format, and it was created in 1977 for floppy disks, not hard drives.
The original FAT, also known as FAT 8-bit, wasn't ever used with MS-DOS, but was used for other storage systems, with a max file size of 1MB, and no listed max volume size.
FAT12 (12-bit) was the original used in MS-DOS and many other DOS-based systems, with a max volume size being either 2MB or 4MB, Depending on cluster size. Max file size is the same.
FAT16 (16-bit), which MS-DOS updated to in 1987, and overcame the size shortfalls of FAT12, with a max of 512MB. Max file size is 1 less byte than 512MB.
FAT32, or FAT 32-bit, is the final version of the original FAT format, being introduced in 1996 with the release of OSR2 of Windows 95. Max volume size is 2TB, max file size is also 512MB - 1B.
exFAT, or Extended FAT, is a continuation of FAT32 created in 2006, with larger limits and being more optimized, max volume size is 16PB, with the max file size being the same.
LEGEND:
MB = Megabyte (1,000,000 Bytes)
TB = Terabyte (1,000,000,000,000 Bytes)
PB = Petabyte (1,000,000,000,000,000 Bytes)
I think the reason EFI partitions are FAT32 is because any operating system can read it natively. Same reason that flash drives are FAT32 when you buy them.
The microsoft guy reading the crash report:
o-o
Because FAT32 is a """standard""" which is """easy to support and implement""". That's why. Ah, and lobbying by Microsoft on EFI sit-ins.
And restoring from a snapshot means that Windows still thinks the partition is NTFS. Accessing a FAT partition with an NTFS driver is, as you can see, disastrous. Nice idea and nice effects!
Side effects:
1. There will be a blank option (right click)
2. Files will NOT open
3. Command Prompt will be blank
4. Blank app on the start bar that does not work
5. Files will pop up with an "Open with" dialog (some)
6. Running "logoff" from Run -> BSOD :(
bsod is from vmware driver
@@alchemycraft yep
Windows 10:I can't bear this pressure.
The music went perfect with this experiment. Nice job man!
Enderman: * Switches NFTS to FAT32 *
Windows: *Your Trail of normal Windows has expired.*
Enderman: let's make a video
VMware: my time has came
0:32 that match so good
EFI partitions need to be FAT32 because that is what is outlined in the UEFI spec, and what many UEFIs will only support.
It has to support FAT32, but there is nothing wrong with supporting other file systems too.
Enderman : installs windows 10 on fat32
Me : *silent circles*
Now I'm intrigued to see macOS Mojave or Catalina running on HFS+.
In that folder named "another folder", you could have renamed "new bitmap image" to "newer bitmap image".
Since you were able to make such an drastic change to the disk while the VM was off, then restore it, I wonder. What would happen if you somehow would change the Windows version for example from 10 1909 to 10 1507 while the VM is suspended and boot up that changed VM
I remember trying to open a FAT32 USB drive and Windows just bluescreened.
First of all, FAT32 wasn't supported in Windows 95 (it used FAT16) until OSR2.
Connecting the VM disk image to another VM isn't needed if it can be mounted on the host as a disk (yes, a disk that can be accessed directly, not just a volume). In fact, if you use VHD format for disk images (which unfortunately isn't supported in VMware, but it does so in VirtualBox (along with support for VMDK as well as its own disk image format, VDI)), you can directly mount it on Windows without any additional software.
Finally after so long... Hope u r doing fine amid the corona crysis.. ♥️ frm INDIA 🙂🙂
crisis*
VisualBox hi
When he said: “Class not registered”
I really felt that
Actually I am totally amazed that AOMEI has an English version of NTFS to FAT32 converter.
Imagine being the guy at Microsoft reading the error message that someone ran Windows 10 on Fat32 lol
Next video: infecting Windows 10 with the coronavirus
**coughs on harddisk**
@@windestruct lol
@@windestruct xd
Didn't know Windows 10 was that broken with FAT32. Does Windows 7 behave this way too?
Side note: Windows 10 can read and write to FAT32, so I'm not sure what the problem is. Perhaps it's just the lack of NTFS features.
Ah i know you, the gamma64 guy!
@@haselnutz_L Irrelevant to the topic at hand.
@@iProgramInCpp alright, sorry
Windows 10 fat32 : HELP MEEEE windows xp fat32: IM HAVE UNLIMITED POWER
Enderman: We know our disk is in perfect condition
Windows: *BLUESCREENS*
Enderman: WHAT THE HELL
Enderman: I won’t sponsor anyone
Also Enderman: *This video is sponsored by Fat32 and VMWare*
Gonna be honest I didn't expect it to be this broken.
Windows 10 on.....
Alexis Godlewski doing Janiyah with gloves on.
What if you switch it back? FAT32 to NTFS?
Generous sponsor: I WANT TO DESTROY GENERIC LIFTS
Me: That "generous" sponsor must have been afraid these "generic lifts" are outdated and might fall without protection.
Ryan Pascual true
From now, the Windows 10 is *FAT*
Windows 10 has always been fat. C:\Windows can be as small as 16 GB, but it takes up ~40 GB whenever possible in the name of performance.
Software:location:c,Windows 10,Windowsupgrader
Adapter:search:Xbox series x/s ssd adapter to usb 3.1
this video should be named "HOW to SPEED UP your COMPUTER BY 200%!!"
It's glitchy because the ram and system is expecting NTFS, not fat32. If you could reset it, it would work better. Try dropping in a fat32 driver, and making the system run with that, then disable driver signature reinforcement to let it boot. Might work!
Windows on an USB disk?
No one talks about the stop code
The 32GB partition limit is fully bogus, and is arbitrary. The real limit of the partition type is 2TB.
3:34
Windows: Mr. Stark, I'm not feeling well...
Enderman: *tries to run regedit*
Computer: *bluescreens*
"I don't play GD"
-enderman 2020
And what?
Seems like the entire registry access just broke lol
User: runs regedit
Windows: bye bye
Enderman, a guy in my class used a usb to reset 10 laptops at school. The IT guy was helpless and confused it was hilarious.
How?
@@malwaretestingfan bootable media i think
"silent circles song" my geometry dash brain said immediately
Why EFI partition still use FAT32?
Becuase EFI compatible system only can read/write FAT32 as a boot partition. (not using NTFS I think thats license or file system architecture problem)
This is why some EFI compatible OS used a partition called ESP (EFI System Partition, FAT32), EFI System need a OS bootloader inside a ESP partition to boot.
Here is how you actually do it
you go into windows 10 setup
you open cmd with shift-f10
you open diskpart
you make fat32 partition
you exit diskpart
you type the dism command that applies the image (manual install thru dism)
you reboot
FAT32 is the lowest common denominator of file systems, it must be useable by many OSes thats why the EFI partition is FAT32.
Next try running Windows 10 on ext4 and on Btrfs, if it's possible.
It's not possible, Windows 10 doesn't even support these two filesystems, let alone the fact that it can't access them. Chances are, the same thing as in the video will happen. Or, maybe Windows 10 won't even try and just crash upon restoring the snapshot, and then it will never boot back up.
Windows don't use unix permission. It will die or just don't boot.
@@AngryDavid808 Actually it's possible. There is custom bootloader for Windows that will let you boot Windows 10 from Btrfs partition. Of course stability is not that great but it's working.
@@vvgr409 That's why I asked for Btrfs too.
@@GoogleDoesEvil That does not mean it can use ext4 as the main FS.
There is an 1016 (Origin DNS error).
Conclusion:
If you want a Fat32 disk, make it an external partition.
Next video: How to lose weight with Windows
Windows 10 in FAT32 wouldn't be possible, Windows 10 cannot handle all the fatness inside FAT32.
Reason : fat32 files requies up to 4gb, white some files on windows 10 is maybe that over 4gb.
Also FAT doesn't mean fat, it's mean File Allocation Table
File allocation table
@@GalaxinTM thanks.
Oh wow Enderman just found another way to destroy Windows 10
Only now I noticed that PS3 read FAT32-based usb flash drive which you could place games (if it's modified) or other but files aren't going to be up to 4Gb...
And the PS3 came off in 2005
Lol
I formated my Phones SD Card today in two Partitions, the first formated by the Phone itself into an App storage partition, and the second in fat32 using Apps2SDs adopting partition feature.
ESP uses FAT32 because it's easy to parse and deal with, and the patents on it have expired by now.
The music hearts my ears man but you are great
3:53 recovery screen
1: 19
That phrase my friends will explain why windows 7,8and 10 won’t run on FAT 32 extension
Because there are actually certain which are more than 4 GB
If you try to force update your Windows 98 to Windows 10
i have a usb stick which is fat32 (no im not joking)
Linux can be installed on more than 5 filesystems
so windows 10 can boot up on fat 32 but its buggy as hell even system crashes
maybe even more tell me if theres more bugs in fat 32 with windows
Windows, is a good day to be alive
*gets replaced on vm suspend*
*screaming* What the FAT?
Are you VM-addicted, Enderman?
(And Enderman is sponsored by HIMSELF)
EFI partitions use FAT32 due to the fact that they wouldn't be recognised by the firmware. just saying.
Fat32, the Windows 10 killer.
Really wonder why it happens.
Windows 10 Millenium Edition.