What If You Delete ALL the Drivers in Windows 11?

preview_player
Показать описание

▼ Time Stamps: ▼
0:00 - Intro
1:39 - Drivers Crash Course
4:20 - Doing the Deleting
10:54 - Trying One Last Thing

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Рекомендации по теме
Комментарии
Автор

Thanks to Privacy.com for sponsoring another video!

ThioJoe
Автор

Imagine you're the computer and someone starts deleting your drives. It will be like removing your -nerves and muscles- memories one by one ☠️

srivatsavm
Автор

Adding a RESTART after each series of file deletes would probably have shown more dramatic changes. I think you nailed it when you said the drivers are probably loaded into memory so file deletes would have little or no impact until a restart.

rlwalker
Автор

I tried this on 7 pro about 2 years ago and fixed itself witth no problem 🐱

windowsxpprofessional
Автор

A lot of the drivers were likely loaded in the RAM of the process. Ending it removed all the drivers for good.

gFamWeb
Автор

What if instead of simply deleting the files, you corrupted them instead? As in mixing some of the binary data up to see what happens, say with Vinesauce ROM corruptor (which works on any file). Windows just crashing at the end is boring. I want to see it actually burn.

chlorobyte_projects
Автор

"Obviously not something you should do at home"
Me: well, time to go to the school i guess!

merbudd
Автор

1:58 actually device drivers are actually a computer program that allows your computer to communicate with the devices

DalmationProductions
Автор

6:33 "Virtual Studio Code" my favourite program

JoaquinPro
Автор

Yes, Window loads drivers into memory at boot so deleting the files might not have an immediate effect. This reminds me of a similar issue I had some time ago, with a 'user'. For some reason he had local admin rights on his machine. He had seen all the anti-trust stuff around Microsoft at the time. So, believing Microsoft was spying on him, he opened Regedit and went about deleting every reference to Microsoft. As you can imagine, his machine didn't live long.

magnox
Автор

ThioJoe: Dont Try This At Home
Me: OkAy I dO ThIs oUtSIdE

jenblox
Автор

For people who dont know, System32 is still called that for compatability reasons as a lot of programs are hard coded to that path. WoW64 however is acutally named like that because it stand for "Windows 32-bit On Windows 64-bit" as it is the subset of windows capable of running 32-bit applications on a 64-bit machine. So the name System32 is outdated, but it has to be called that to not let everything break down.

MsMiDC
Автор

0:10, Alright, I'm gonna try this on a virtual computer,
Also Joe is a better computer teacher than the teacher at my college

surajitsadhya
Автор

ThioJoe: "so we might break it"
Also ThioJoe: It should be fun!

itsjavii
Автор

Hardware drivers for sure are loaded into RAM upon boot. The system naturally should not be looking on the non volatile drive for drivers every time an interrupt occurs.
Deleting the source does not do anything until you reboot, but I guess you figured that out.
Actual system files is a different matter. They get loaded as per needed and some (quite a few indeed), based on complexity and range of functionality are accessed on the disk during operation, in order to minimize RAM consumption.

JGFXDK
Автор

It’s called VISUAL studio code not virtual

realczcx
Автор

Do a one on "What if you delete registry folders" I think that could boost up your viewers.

ushanbimsara
Автор

drivers are loaded into memory ( usually at startup ) and remain active even when you remove the actual files, but when you reboot ! bam the system boot process cannot find anything to load.

vizzair
Автор

The only driver I've messed with was the touchscreen, I had to disable it because my screen got cracked and trying to use my laptop would be very annoying to use.

kingdedede
Автор

If every single device is not unknown device i am gonna be disapointed

Arokhantos