[Intro]
Hello! This video is a little different from the ones I release on my channel. In this video, I want to show three bugs in Windows that can be made using standard and auxiliary tools. I will be very glad to hear your feedback: whether you like it or not. Comments are always open to your opinions!
Well, I will not torment - let's get started.
The first bug is that the system can be made to think that it is not installed
Open the registry editor, follow the path: HKLM\SYSTEM\Setup And we change the value of some keys as shown in the video
Changes are not applied immediately, a reboot is required. Therefore, at first glance, nothing has changed.
After restarting, the system will start checking everything again and reboot a couple of times. Everything is as in the second stage of installation
After all the reboots have passed, the message "Please wait ..." appears, which will be displayed for a very long time. At this time, a complete editing of the system registry occurs.
And after that we are greeted by the desktop, and the system is already starting to show notifications that an error has occurred in something.
In this case, the opening of any explorer window will be accompanied by an error.
The system also loses network connectivity and sound.
Creation of folders works (at least something work) But their discovery is not available.
When you open the device manager or configure services, the system begins to noticeably "think"
But in the end, the error "The device is not ready" comes out, and the command prompt says that we are denied access.
Restarting the system or re-login into the account will not fix the situation.
If you do the same in Windows 10, then it turns out more interesting there.
The system logs in, everything is as usual. But it doesn't actually happen. The following happens behind the login screen...
The desktop restarts, starts and again in a circle, Start menu and any applications simply cannot be opened.
Okay, let's move on to the next bug.
The next bug will be in XP. We will install Explorer (explorer.exe) as the debugger for the welcome screen (LogonUI.exe)
Open the registry editor and follow the path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
Create a new section there, which we will call it the name of the file
We create the "Debugger" parameter there and write the name of any application that we want to run as a debugger to the file (as an example, we put a debugger to LogonUI.exe)
For example, I wrote Explorer.exe
And when we log out, we will not see the welcome screen, but something else...
We will see the desktop of the SYSTEM user
But launching applications will fail: the system will send an error stating that "there are not enough quotas to process the command"
Even system applications and other settings cannot be started
And the Start menu looks like this. It is immediately noticeable that we were deprived of the possibility of shutting down the system.
Rebooting the system won't change anything either. For that, we immediately see the desktop, and not the welcome screen.
Okay, let's move on to the next bug.
The next bug (or rather, probably just a feature, I don't know) is to perform actions on behalf of SYSTEM
The third-party program PsExec will help us with this. Run the command line as administrator
After we have opened the command line, go to the folder with the PsExec program and enter the following command [psexec -s -x c:\windows\system32\cmd.exe]
The command line is always executed on behalf of our user But in this case, it's a little different here.
In this case, the command line is executed as SYSTEM. This user has the highest systemic rights.
The most interesting thing is that the execution of applications through this command line it is executed secretly and on behalf of the system.
That's all I wanted to show you. I hope it was interesting. See you :)
Leave a like and subscribe to the channel ;) The names of all musical compositions are indicated in the description!