After ejecting C:, the system will run somewhat stable by surviving on the data loaded into memory. While it can survive for a while on ram, some programs or drivers may try and load more data from the disk into memory, but it can't access that data. Over time the system will destabilize as more and more programs try and load inaccessible data into memory. Eventually the system will freeze or BSOD.
Huh, I would have thought unmounting C: would cause a blue screen. It definitely does if the disk stops responding or is disconnected suddenly. But this is a much more interesting result. Thanks for the video!
it doesn't bsod because the bsod code/files are in the c drive and windows is like "oh well I can't do anything because user:Andrew ejected the c drive"
What would be more deadly is ejecting the S: drive . It’s a hidden drive that holds all the efi folders for booting up. So you won’t be able to recover the system
lots of things to say here. first all the drives needed are mounted on boot so unmounting/ejecting the "S" drive woulndt do anything. also the "S:" drive doesent have a drive letter, its a partition named "system reserved" and if you want to access it you have to assign a drive letter to it first., also lets say you were able to completly delete the "system reserved" partition. you could just boot to a external medium and get all your data back off the c:\ drive
@@TheOriginalMacOS or just these commands (from wpe) diskpart sel dis 0 cre par efi size=500 form fs=fat32 quick assign letter w exit bcdboot C:\Windows /s W: wpeutil reboot
this actually tells you a lot about the memory management in windows because the system obviously can't read anything from the C: drive while said drive is ejected, yet somethings remain working. It seems that that what is cached in memory (preloaded in memory for future faster access) are the core graphics of the system, the windows API and some core programs like the file explorer and windows logon, yet that what is declared in the resource files of those programs (like the program specific graphics and text messages) remain unloaded. Interesting...
@@pcuser80 I just tried. The linux system has some pretty strict security measures and simply refuses to eject when a file is busy being read. So it is pretty difficult to accomplish. The furthest I got was un unmounting root with the -l option which already unmounts lots of the "virtual" filesystems. The thing about a unix architecture is that it heavily depends on "virtual files" in order to keeps its system API as simple as possible, that is because, on a unix one can control a lot of the internals by just writing bytes to these files so you only need a simple set of IO kernel calls to control lot of your Linux. For ejecting the CD tray for instance, one has to write a byte to the file /dev/sr0. On my system (a Debian), there are about 418 and that is enough to control the entire system. For a Windows system, there are thousands of possible calls with several undocumented. Without the virtual proc and dev filesystems, doing these calls and controlling these devices pretty much becomes impossible and your system will slowly start to break down. The only thing you can still do is write files to your regular filesystem since that will be the only thing accessible since that filesystem is always busy and won't be unmounted until you shutdown the computer.
@@beedslolkuntus2070 internet will be attacked by indians they will take over the world by using internet and bitch lasagna, also known like T(urd)-Series.
When you remove the hard drive from a running computer, it still works, but when you try to access anything, it freezes, goes black, then BSODs. (inaccurate results, other computers may not do the same)
This is because most computers put the current running data on ram and when you attempt to access something on a now inaccessible device, it just crashes because it doesn't know what to do.
What happens if You eject this UA-cam video?
Alto Bluedot THE UTUNE WILL PLAY AND UA-cam WILL DIEEE AHHHHHHHH
UA-cam will delete System32
@@techienator NO!! NOT SYSTEM32!!
Error 202: Comment not found. Displaying as:
aN!! NaN ErrorNaN!!
@@ChloekabanOfficial found comment aN!! NaN ErrorNaN!!
Windows XP Textless Edition
Buy now!
xD :D
X Dedede
X Dedede
How much do YOU think this advanced operating system is worth?
@@eper9866 $399
Enderman: *releases video*
Windows Development Team: look how he murdered my boy.
true
My Computer [X]
(X)
*_ok then windows_*
"Thank you for the (X) Windows" -Endermanch
My Computer [X]
----------------
(X)
----------------
________
| ok |
--------
2:16
@Marcela Oliveira what?
1:05 This reminds me of "Mii Channel Corruptions" video.
Nice video!
Ы!
Mountvol c: /d - и это круто?
Вы смотрите Enderman? Если да, то Лайк комменту. Я ваш подписчик
After ejecting C:, the system will run somewhat stable by surviving on the data loaded into memory. While it can survive for a while on ram, some programs or drivers may try and load more data from the disk into memory, but it can't access that data. Over time the system will destabilize as more and more programs try and load inaccessible data into memory. Eventually the system will freeze or BSOD.
0:43
The task bar was hungry for some captions.
Huh, I would have thought unmounting C: would cause a blue screen. It definitely does if the disk stops responding or is disconnected suddenly. But this is a much more interesting result. Thanks for the video!
it doesn't bsod because the bsod code/files are in the c drive and windows is like "oh well I can't do anything because user:Andrew ejected the c drive"
@@qwke dyk where is the bsod code located?
@@finishedpessi idk man, maybe it's stored in memory, but the code for it is definetly on the hard drive
@@qwke it's all in memory already, after all, anything that triggers a bugcheck is in the kernel, which is in memory.
@@qwke more like "oh well I can't do anything because user:undefined ejected the c drive"
Gotta love them UA-cam notifications "always" being on time.
What would be more deadly is ejecting the S: drive . It’s a hidden drive that holds all the efi folders for booting up. So you won’t be able to recover the system
lots of things to say here. first all the drives needed are mounted on boot so unmounting/ejecting the "S" drive woulndt do anything. also the "S:" drive doesent have a drive letter, its a partition named "system reserved" and if you want to access it you have to assign a drive letter to it first., also lets say you were able to completly delete the "system reserved" partition. you could just boot to a external medium and get all your data back off the c:\ drive
@@TheOriginalMacOS or just these commands (from wpe)
diskpart
sel dis 0
cre par efi size=500
form fs=fat32 quick
assign letter w
exit
bcdboot C:\Windows /s W:
wpeutil reboot
@@Spoudey well that works too, its more effective but when i was typing the comment i was on a phone and dint feel like typing all those commands
@@Spoudey I'm disappointed that you know all those abbreviations within diskpart, but not the most glorious of all: 'ass' (for 'assign'). 🤭
@@whohan779 i forgot 😔 although ive had it not work sometimes
Enderman: Ejects C drive
Me an intellectual: Rips the fucking drive out of the computer while it's still on
0:43 rip system32 1995 - 2018
C: drive: *doesn't exist*
all of the windows: *_THICC_*
this actually tells you a lot about the memory management in windows because the system obviously can't read anything from the C: drive while said drive is ejected, yet somethings remain working. It seems that that what is cached in memory (preloaded in memory for future faster access) are the core graphics of the system, the windows API and some core programs like the file explorer and windows logon, yet that what is declared in the resource files of those programs (like the program specific graphics and text messages) remain unloaded. Interesting...
How will Linux react when you unmount / (root)?
@@pcuser80 I just tried. The linux system has some pretty strict security measures and simply refuses to eject when a file is busy being read. So it is pretty difficult to accomplish. The furthest I got was un unmounting root with the -l option which already unmounts lots of the "virtual" filesystems. The thing about a unix architecture is that it heavily depends on "virtual files" in order to keeps its system API as simple as possible, that is because, on a unix one can control a lot of the internals by just writing bytes to these files so you only need a simple set of IO kernel calls to control lot of your Linux. For ejecting the CD tray for instance, one has to write a byte to the file /dev/sr0. On my system (a Debian), there are about 418 and that is enough to control the entire system. For a Windows system, there are thousands of possible calls with several undocumented. Without the virtual proc and dev filesystems, doing these calls and controlling these devices pretty much becomes impossible and your system will slowly start to break down. The only thing you can still do is write files to your regular filesystem since that will be the only thing accessible since that filesystem is always busy and won't be unmounted until you shutdown the computer.
Yes, that's normal.
Classwork: Good!
Homework: My brain: 2:15
2:20 Yes, that is very informative actually. An imageres/shell32 icon speaks 2,000 words.
0:43 try to get da taskbar
Everybody gangster till the Windows 3.1 font shows up
You always find creative ways to mess up with Windows
Interesting! I wasn’t expecting Windows to keep clinging on to life like that.
MacOS did a similar thing when my hard drive broke.
Idk why but these video give me goosebumps sometimes.
Enderman: **ejects c: drive**
Windows: *HAHA NO TEXT FOR YOU*
Windows:
Everyone: Man that's informative
"We're gonna interrupt the user setup"
The Windows login screen: *no why did that dum black command box have to interrupt me*
i thought windows would just vanish and nothing else, but this is much more interesting
If windows 10 does not have C: then it will give a bsod
Or if you deleted it... With cmd
(dont use it on your pc use a vm plz)
1.Type in this:cd C:\Windows\system32
2.type in this:del *
You will get this:Are you sure? Y/N
Press Y and boom
And if task manager is open try typing Explorer.exe if it gives an error you did it right abd reboot
@@blueboi_taipei101 no shit
man i wanna hug you for great times, i frickin love you and your videos ❤️
bro
i cannot believe you only have 67,2k subs (16.4.2020), you deserve atleast 200k
Basically if you eject C: the system tries to survive only with what was in RAM, but it fails.
creating ramdisk
NO RAMDISK.SYS FOUND
Mom, can you give me cmd.exe for programming?
- For programming?
Yeeees
- Actually ejects C: drive like a boss
CRASHING TIME
Congratulations, Enderman, you have just made Windows eat a neutron star.
I know I am 1 year late but windows'es Mouth is way too *B E E G*
In 2030: what happens when you eject the ram out of a running machine
Love it! Definitely very interesting how Windows reacted! Nice!
What happens if You eject T-Series from the life?
PewDiePie is Happy!
@Servine LOl
What happens if we eject pewdiepie from our life
@@beedslolkuntus2070 shit happens
@@beedslolkuntus2070 internet will be attacked by indians they will take over the world by using internet and bitch lasagna, also known like T(urd)-Series.
Windows 8 for some reason gives you the option to "eject" C drive, but it wont do anything
Windows fail even at destroying itself.
2:14 last that popped up in school
2:10 wait... isn't that a windows 7 ISO icon?
It is.
Yea, it's the installer for Windows 7
Awesome premiere! I love your videos, they're so awesome!
1:25 what is shortcut to change logon screen?
Wow, I didn't expect that the final would come out like that, it was terrific by ejecting the C: drive 😁
2:15 сильное заявление
Проверять я его конечно же не буду
опа Русский найс
someone translate this stuff
Enderman: *eject*
Microsoft: im a joke for u?
Ejecting C Drive means u deleted System32 and made PC faster (Note: that is a meme so don’t actually delete System32)
0:42 slow it down to 0.25 speed then you’ll see the Windows XP’s taskbar
Thx you. All of your contents are so fun
2:15: My brain when I start doing my homework belike:
next: unplug c: drive while the computer is running
The obvious happens. Your computer freezes up
Ejecting C:
Windows To Go : *Eject External Hard Drive (C)*
Ejecting c: drive just like removing your liver
hey, your youtube channel has actually made me learn a LOT about computers.
'
thank you ;)
You can Install on SATA and actually eject the drive while running!
CMD:...
C:\user\ CD %windir%
C:\Windows\
am I right?
Not
2:22 code for this in vbscript is "X=MsgBox("",0+16,"My Computer")"
who asked
@@_kitaes_ nerds like us
I want to see more stuff like this now.
Good job on.... breaking windows?
What happens if you eject the C: drive? Absolute chaos.
Next video idea:What happens if u format the C: drive?
*huge thanks for breaking my intro*
Watching this on 2 different Devices and my 2nd one is going crazy
Shrek vs Thanos: despacito battle
Jesus i really like your intro sometimes i just click on your videos to see it lol
Thanks for doing it Endermen i like when you do it
So basically, you disconnect brain
It is a happy face C:
What is the song in 0:10
Next: What if you delete cmd?
What happens if you eject the DVD drive?
world blows up
what if you install Android to iPhone?
@@net6406 then the world blows up again
@@nave5462 what if world blows up twice at the same time?
@@Квант-н5ф you blow up
Congrats, you broke Windows!
Windows: Expert mode edition
TERRARIA REFERENCE???
Wow, Windows is still running from memory even when the disk is dismounted!
Thanks, now I know what they are storing at RAM
I remember a virus did this as its payload
Awesome! İ've always tried to found videos like this
This is the best Subscribe/View ratio i have seen damn
When you delete all on disk C: and computer can restart...
C: is also a face so that’s why i love the C: drive lol
Can never unsee lol
D: is too lol
what happens if you eject your house?
the world ejects
It will go to space
Dank memes
it gives you a few error messages and becomes really laggy.
Ez ur c/: drive pops out
Ikr duh 😂
This Is not destroyed after a reboot windows will Continue to work Perfectly
hi im new on your chanell! :)
When you remove the hard drive from a running computer, it still works, but when you try to access anything, it freezes, goes black, then BSODs. (inaccurate results, other computers may not do the same)
This is because most computers put the current running data on ram and when you attempt to access something on a now inaccessible device, it just crashes because it doesn't know what to do.
How do you get the command prompt to open right when you are logging in.
Sometimes...Windows are so scary :P
*is
Very nice find !!
woah this is the earliest ive been for here 8 hours
____________________
[My Computer___❎]
|(❌) |
L___________[ok]___|
*_yea man I miss her too_*
What happen when you dislike tiat video?
Enderman comes and steal the floor under your feet
I have done this experiment in my real computer WAY BACK LIKE 2 years ago
The computer works very bad without C: drive.
2:15 *My computer* ❎
❎
*OK*
*BLANK ERROR*
No shit Sherlock
just one shot from command prompt and the text is GONE
My windows are on D: so if I will repeat this I will get this too?
*If you Eject your PHONE it might be gone*
That how Ejecting PC look like
I write this comment on a ejectet C: drive with Windows 10
i can eject C: drive anytime, it appears in the usb eject tab as well as other hdds
Windows XP: *Eject PC* edition
The face of computer is now :C
Not C:
Is there a way to fix it?(opposite of ejecting c:)?
If u eject the c drive, ur runnig windows will flush itself down the toilet