Co się stanie, gdy usuniesz folder "Program Files" w Windows? (film, 14 minut)
ThioJoe prowadzi kolejny komputerowy eksperyment, w którym pokazuje, co się stanie, gdy usuniemy foldery „Program Files” w systemie Windows. Dla przypomnienia, w przeszłości eksperymentował z usuwaniem krytycznych folderów, takich jak System32, co zazwyczaj kończyło się katastrofą. Tym razem skupia się na folderach Program Files i Program Files x86, które zawierają zarówno aplikacje, jak i ważne pliki systemowe. Przy użyciu maszyny wirtualnej, ThioJoe podkreśla, że nie powinno się tego robić na swoim rzeczywistym komputerze, aby nie uszkodzić systemu operacyjnego, i to w sposób humorystyczny. Co ciekawe, pomimo prób usunięcia plików i folderów przez zmianę uprawnień, na początku usunięcie niczego nie zmieniało w wydajności systemu.
Podczas badania zawartości folderu Program Files ThioJoe zauważa, że większość preinstalowanych programów nie będzie miała krytycznego wpływu po ich usunięciu. Jednak inne foldery jak Windows Defender czy Windows Apps mogą być istotne. Wraz z wzrostem liczby usuniętych folderów, niektóre programy przestają działać, ale Windows jako cały system nadal działa. ThioJoe relacjonuje, że pomimo usunięcia większości krytycznych plików, użytkownik jest w stanie wykonać niektóre podstawowe operacje, takie jak otwieranie kalkulatora czy przeglądarki Edge.
W miarę postępu eksperymentu, ThioJoe stwierdza, że mimo iż usunięcie folderów Program Data nie przynosi oczekiwanych rezultatów, komputer mimo wszystko zaczyna działać niestabilnie. Choć interfejs jest nadal dostępny, tych usuniętych programów brakuje, a inne również przestają funkcjonować, co prowadzi do „zawieszeń” systemu. Próby do działania przywracającego, takie jak uruchomienie narzędzi naprawczych jak System File Checker (SFC) czy DISM, przynoszą jedynie częściowy sukces, a system upiera się przy poprzedniej wersji Windows 10, co dodatkowo zaskakuje ThioJoe.
W rezultacie eksperymentu dochodzi do całkowitego zrujnowania obecnej wersji Windows. Ostateczne próby rozwiązania tych problemów za pomocą komend do resetowania uprawnień kończą się sukcesem częściowym - ekran logowania zaczyna wyglądać normalnie, ale niektóre aplikacje nadal są niedostępne, a komputer nie odzyskuje pełnej użyteczności. Jak zauważa ThioJoe, największy błąd popełniony podczas tego eksperymentu polegał na zmianie uprawnień folderów, co uniemożliwiło systemowi tworzenie ich ponownie. W związku z tym Twierdzi, że najlepszym rozwiązaniem w takiej sytuacji byłoby przeprowadzenie czystej instalacji systemu operacyjnego.
Na zakończenie swojego filmu, ThioJoe zaprasza widzów do wyrażenia swojej opinii w komentarzach oraz oglądania wcześniejszych filmów, w których przeprowadzał podobne eksperymenty, związane z usuwaniem innych krytycznych folderów systemowych. Osoby śledzące kanał ThioJoe na pewno znajdą wiele interesujących filmów na temat komputerów. Na czas pisania tego artykułu, film miał 583344 wyświetleń oraz 14369 „lajków”, co świadczy o jego popularności wśród widzów.
Eksperymenty ThioJoe pokazują nie tylko zabawny aspekt interakcji z technologią, ale także ostrzegają przed konsekwencjami podejmowania groźnych działań na własnych urządzeniach. To przypomnienie, że z technologią należy obchodzić się ostrożnie, a radykalne eksperymenty mogą prowadzić do nieodwracalnych skutków.
Toggle timeline summary
-
Wprowadzenie do eksperymentu komputerowego dotyczącego niebezpiecznych działań.
-
Poprzednie działania obejmują usunięcie krytycznych folderów systemowych.
-
Dyskusja na temat znaczenia folderów Program Files.
-
Ogłoszenie zamiaru usunięcia ważnych plików.
-
Zapowiedź zaskakujących wyników oczekiwanych z eksperymentu.
-
Podkreślenie przeprowadzenia eksperymentu w maszynie wirtualnej.
-
Przegląd zawartości folderów Program Files, x86 oraz Program Data.
-
Badanie wstępnie zainstalowanego oprogramowania i krytycznych funkcji.
-
Identyfikacja folderów potencjalnego znaczenia, takich jak Windows Defender.
-
Dyskusja na temat zawartości folderu Windows Apps.
-
Rozpoczęcie procesu usuwania folderu Program Files.
-
Napotykanie problemów z uprawnieniami podczas próby usunięcia plików.
-
Użycie narzędzia do uzyskania podwyższonych uprawnień do usunięcia.
-
Częściowy sukces w usunięciu folderu Program Files.
-
Sprawdzanie wpływu na funkcjonalność systemu Windows po usunięciu.
-
Zauważanie nieprawidłowo działających aplikacji, takich jak Microsoft Store i kalkulator.
-
Usuwanie zawartości Program Data w celu oceny wpływu.
-
Obserwacje krytycznych błędów i zamrażania pulpitu.
-
Próba ponownego uruchomienia Eksploratora Windows w celu przywrócenia funkcjonalności.
-
Wymuszone ponowne uruchomienie ujawnia dziwny ekran logowania.
-
Obserwacja paska zadań i interfejsu Windows 10 po ponownym uruchomieniu.
-
Zakończenie eksperymentu z deklaracją, że Windows został zrujnowany.
-
Ostrzeżenie widzów przed wykonywaniem podobnych działań na ich systemach.
-
Zachęta dla widzów do angażowania się w feedback na temat wideo.
-
Linkowanie do poprzednich eksperymentów w celu dalszego oglądania.
Transcription
Well, it's time for another computer experiment where I try to do things you should absolutely not do to your own computer. I'm ThioJoe, and in the past, I've done stuff like deleting the System32 folder, or deleting the Windows and AppData folder, stuff like that. But what about those Program Files folders you've probably seen? There's actually more to it than just programs you've installed. There's actually some important Windows files in there. So we're going to find out what happens if you delete them, while Windows is running, of course. That's the fun part. And actually, the result for this one was pretty hilarious. I was not expecting it, so I think you'll like this. As always, I am doing this in a virtual machine. So again, do not ever do this on your own computer. As you'll see, it basically will ruin it. All right, so quickly for some context, first let's take a look at what's actually in these folders. Now, I'm running Windows 11 Pro, and of course, I've enabled Hidden Files and Folders, as well as System Files and Folders, so we can see everything. So the three folders we're dealing with today are the Program Files folder, the Program Files x86 folder, which has 32-bit files in there, and then the Program Data folder, which is related. I'll explain that in a second. So first looking in the Program Files folder, this is for a clean installation of Windows. If you have other stuff installed, obviously, it's going to mess with those too. But as you can see, it's mostly just some pre-installed Windows software here. Shouldn't be too critical for most of these, like Windows Mail, Media Player, Photo Viewer. I don't think this is going to destroy Windows deleting those. But there are some other folders that seem like they might cause some issues, like Windows Defender, Windows PowerShell, the Common Files folder, which has stuff like Microsoft Shared and System. These seem kind of important. Also, Windows Apps. I can't even look into this one normally, so I had to actually set myself as the owner for these files. And it looks like there's some install packages or manifests for those pre-installed files in here. Everything from Bing News to Sticky Notes, Windows Terminal, and Notepad. One thing to note, though, is I don't believe these are installed here. It's just some manifests and info about the installation. Now, if we go to the other Program Files x86 folder, you can see it's a lot of the same stuff as the other one. We see Windows Mail again, Photo Viewer. I guess these programs have both 64 and 32-bit stuff in there, so it's in both folders. There also seems to be folders in here that look like they might be important, like Common Files, as well as the Microsoft folder, though this one just seems to have Edge browser stuff. We'll see. And finally, we can take a look at the Program Data folder, which isn't where programs are installed, but it just contains data that all users will be using in relation to a program. So it's not the installation. It's maybe where settings files and stuff will go that will apply to all users. Now, several of these are empty, like the SSH folder, the software distribution. There's this regid1991 folder, which just has one file. But there are some other interesting ones that I'm not 100% sure about. USOSHARED and USOPRIVATE seems to stand for Updated Session Orchestrator, though these are mostly empty. And then the Packages folder again. And then going back, though, we have the Microsoft folder, which seems to contain some important-looking folders that weren't in the other ones, such as the Windows folder. I would think that's important. It has stuff even, like, about the Start menu. So I think if we delete this, it might mess some stuff up with the Start menu. We'll see. And then AppRepository, this seems to be yet more packages. So let's actually get to the fun part. So first, I tried deleting program files. I tried just deleting it all at once. Of course, that's not going to be that easy. Right away, the trusted installer permissions blocked it, which is basically the highest permission level on Windows. So I figured, let's go inside, see what we can delete in there individually. And it did let me delete some when I selected all of them. I did try to delete the others individually, but again, it wouldn't let me do that. To get access, I even tried setting myself as the owner for all these files by changing the security permissions, but nope, that didn't work. So this is turning out to be tougher than I expected. But finally, I tried a tool called Advanced Run. This is a Nearsoft program which can let me run as elevated users. So I ran the command prompt as trusted installer, which we saw before, and then tried doing the command to delete common files just as a test. And boom, finally, it just went away. So then I tried the command just on the entire programs files folder, and it went through and it says some were access denied. But if we look inside, there's only a couple folders left. So it was mostly successful. We have the Windows Defender left. Not surprised, there's probably some extra protections for that folder, as well as Windows Apps. We'll deal with that later. Now, before deleting more stuff, let's click around Windows and see if anything is messed up yet. So the Start menu seems to look normal. Edge still opens up. The Microsoft Store does not open when I click it in the taskbar. All right, that's one thing to note. And trying to run stuff like the calculator from the Start menu, also not working, interestingly. So now let's take a crack at the program files x86 folder. Again, I'll just select it all and try and delete it the old fashioned way. And again, it deletes a few, but not most of them. So this time, again, I tried the take ownership thing on all folders, and it does make me do a UAC prompt for every single one. But when I tried deleting common files in here, it actually worked this time. So I was able to just delete that. And then it seems like most of the other ones are working when I delete it. The Microsoft folder won't. We can save that for later. So we're basically just left with the Microsoft folder and the Windows Defender folder. In the Microsoft folder, it's mostly Edge stuff. And it said it was in use. So I looked in the task manager, tried ending the process in there. Although it still wouldn't work. It still was in use, so I'll save that for later. And then I'm also going to leave the Defender folder. Again, I think that probably has extra permissions built in. So again, we can just kind of mess around with Windows, see if anything has changed. And more stuff seems to be not working in the start menu, like Notepad, Clock, Movies and TV. Although these might not have worked before. I didn't actually check these. Even Terminal won't start. So while the programs seem to be all broken, it seems like Windows itself is still fine and dandy. So maybe deleting Program Data will mess that up. And actually in Program Data, it let me delete a lot more than the others. There's only three folders left, Microsoft, Packages, and USOSHARED. In Packages, I was able to delete most inside. There's only a few left, probably because these are in use. So I ended the Teams app, and then I could delete that one. I ended Terminal, but still can't. It says it needs a system permission. And then in Microsoft folder, by selecting all folders, I could delete a decent amount more. There's only 11 folders left now, though it seems like most left here either need permission from system or are also in use. Going back to the Program Files x86, I wanted to see again about the Edge folder. So I noticed it says in the Task Manager that the web processes are used by the widgets. So I ended that process, and now I could delete those Edge folders. And so that's the last of the Microsoft folder. Then going back into Program Files, I was able to delete more of the Windows app folders, and seems like just Terminal is not letting me do it still. So after deleting all of that, now let's see if anything is broken in Windows. So the Start menu actually opened up for a second and looked empty, but then it immediately crashed. And now it won't open, and nothing happens when I click it. And then I realized actually the entire desktop is frozen. Clicking on nothing works, though not the entirety of Windows is frozen. I was still able to bring up the Task Manager with the shortcut for that. So I tried restarting Explorer EXE, and that actually worked. I can now even open up the Start menu again, although the taskbar seems to be missing some icons. But I wanna see if we can break it even more. So I'm gonna try running the command prompt as the system user using Advanced Run again. This still seems like it can't delete a lot, but a lot of it is because it's in use. So it seems like we will with a little bit of effort. So to deal with the files that are in use, I decided to use the Power Toys tools that is a suite of tools published by Microsoft. And specifically, one of them is called File Locksmith, which will show you what files are being used by what programs, and then lets you end those tasks. And interestingly, it still had no problem installing software, although I realized that just went into the Program Files folder that we're trying to delete, but we can leave that alone for now. So we can go back to the Search folder, for example, and File Locksmith is telling me that the Search Indexer is using that. So I ended the task, and now it actually does let me delete it. But then I realized it's gonna just keep creating it again. So I'll come back to that. I'll try some more that are in use, like the App Repository. It says it's in use by the AppX service. So I go into the list of services, stop that, and now I can delete that. There's some more in use by the State Repository service. So again, stop that and delete it. I tried to finish off the Packages folder, but it said they were in use and wouldn't tell me by what. And then I realized it was just creating those other files again. So I decided to get kind of clever and change the permissions of these folders so that I as the user was able to access it and delete it, but the system did not have permission to write to it so it can't recreate anything. So now it indeed was not recreating anything, although now the Indexer is messed up and Explorer is frozen, I guess because it can't index the files or read what's in here. I don't know, something's messed up. And then the whole desktop just keeps crashing. Can't really do much here. It basically seems stuck. So obviously nothing is working here. So I decided to do a forced reboot. And when it powers back on, there is no background to the login screen or anything. It still lets me log in though. It just took a little bit. But now once I get in, the taskbar looks kind of weird. It's the old Windows 10 taskbar. There's nothing in the system tray. I tried clicking on the Start button. It just says Critical Error. There's not even an option to cancel. It just wants me to sign out, but let's just move that dialogue box out of the way for now. I tried to open up Windows Explorer. Maybe it's working now. And I noticed something weird. This is not the Explorer I was using before. This is the Windows 10 Explorer. So for some reason it seems like Windows reverted to the Windows 10 taskbar and the Windows 10 Explorer because basically Windows 11 is built upon Windows 10, has that still in the background. So I guess it kind of reverts to it if something goes wrong. Going back into those folders, it does look like it recreated a good amount of them again. But since the search indexer was the thing that probably broke it last time, let's test and do a search. It seems to be doing it, but no results are coming up. So it probably is still not working. So then I bring up the task manager and it's the Windows 10 task manager too. We've literally broken Windows so bad that it downgraded itself to a previous version. So then I figured, all right, well, let's try one more time to keep deleting stuff. But as soon as I right clicked, it just started spinning the cursor and nothing happened. Explorer froze and stopped responding. Right click still works on the desktop. And I tried another Explorer window, maybe it was a fluke, but nope, same thing. So because I can't even right click properly, I think we can officially declare this Windows installation as ruined. But then I was thinking, I wonder if there's a way to actually recover this and fix Windows. So let's see if we can do that. First, I tried the trustee system file checker command. So the SFC slash scan now, and it did say found some files that were corrupted and said it fixed them. And when I went to look at the log file, but when I tried to hit edit, it wouldn't open a notepad because it thought that it was not installed anymore because the package manifest was gone. Although I knew notepad is still in system 32. So I went in there and opened it through that. So looking through the log file, it seems like there's a bunch of lines talking about repairing files in all the folders we messed with, like program data, program files. You can see it's repairing all of these. So I decided, all right, let's restart, see what happened. But still no background for the login. The task bar still is messed up, still can't right-click in program data, still messed up. So then I try a command called DISM. This often goes in hand-in-hand with the system file checker. Basically, it makes sure that the files that system file checker are using are correct. So I ran that, but that seems to get frozen at just 60% or so. So I closed that, ran system file checker again, but this time it said there was a bunch of files that couldn't be repaired. Then I went back and forth, trying the DISM and SFC again a couple of times, and I restarted one last time, but it doesn't seem to have any improvement. It's still all messed up. I can't even right-click on other folders that we didn't touch in here, like the Windows directory. So it's not just the ones we messed with. So the final idea I figured I'd try is since I messed with the permissions, and that seems to really have been the last straw, there is a command to reset the permissions of folders in Windows, and that is the ICACLS. And I ran it for all three of the folders, and it actually said that it succeeded on some of them and failed on the others, though maybe the failed ones were ones that were already fine. So yet again, I restart Windows and, oh, wow, there is actually a background to the login screen now. Maybe we're on the right track. The taskbar still isn't fixed, but I can actually now right-click on stuff in the Explorer again, but it still looks like the apps are missing too. So then I run SFC again, and this time it says no integrity violations found. That's kind of odd. I run DISM again, then SFC again. Both of them think it's all good. However, it still obviously is messed up. For example, when I run the Start menu, it still says critical error, that sort of thing. So I am officially out of ideas on how to fix this. I'm gonna declare it ruined. So basically, even though Windows was able to keep running through all this, it was not really usable by the end of it, but I still find it really funny that it started just looking like Windows 10 again. I didn't expect that. Definitely the point that really messed with it was when I was changing the permissions, which didn't allow it to recreate the files that I was deleting, and I think that really tripped it up. But it's really weird that even after running System File Checker and DISM, which I thought would fix permissions anyway, I thought it did that, and then I explicitly ran the fix permissions command, even though it improved it, it still didn't fix it completely. So yeah, obviously don't do this. You'd probably have to do a clean install to fix it for sure. So anyway, if you enjoyed this video, definitely give it a big thumbs up and let me know down in the comments what you thought, and if you have any ideas for stuff I should try in a future video. If you want to keep watching, I'll put a couple of previous what if videos here, like where I deleted System32, as well as the app data folders. Those are pretty fun as well. So you can just click on those right there. So thanks so much for watching and I'll see you in the next one.