I love how the classic theme has been so ingrained into Windows that it's the lowest layer of GUI Windows can load, giving us 3 rings of GUI: 1. Whatever normal Metro-like GUI comes with your system 2. Aero Basic 3. Classic It's literally the first thing that can pop up on Windows when the GUI is deployed for the first time, or when whatever would normally run the GUI gets so fucked you're left with something from 20 years ago
@Spoon974 ай бұрын
Theres a software from windows (iirc it's a server thingy) that has gui from the windows 3-ish era
@lemonadesnake2 жыл бұрын
I find it funny how in windows nt 4-xp, it would crash the entire os, in vista-8.1 it would just log you off and in 10 and 11 it makes the windows have a weird glitchy vista safe mode classic theme and logs you off at a later time
@SkylerIsAGoner2 жыл бұрын
@Soumodeep Guha I know it looks nice but performance just ew
@SkylerIsAGoner2 жыл бұрын
@kinan YT gamer legendary 🕹️🥇 WDYM YPOU CAN'T WHAT I CAN'T SAY THE PERFORMANCE IS BAD?
@TsunamicBug2 жыл бұрын
@@SkylerIsAGoner you should be saying that for windows 10/11 windows vista is blazing fast because it's effectively the same as 7.
@SkylerIsAGoner2 жыл бұрын
@@TsunamicBug gurl/sir I am talking about the crashes NOT the speed
@polytelus2 жыл бұрын
@@SkylerIsAGoner You said "performance". Crashes have to do with stability, performance almost always means speed.
@user-lc6lo7zr9k2 жыл бұрын
Windows Vista and above systems have rewritten the NT kernel code, so the c0000021a blue screen of death will not appear when ending the winlogon.exe process, but will log out directly.
@alexbalan_56232 жыл бұрын
I think I understand why Windows 95-XP can't handle/work without winlogon.exe (it's like Windows 10/11 can't work without csrss.exe)
@_eesports2 жыл бұрын
Explans why it wouldn’t crash the second the process is killed.
@TheLukasz0322 жыл бұрын
That's because the load chain for Winlogon was changed entirely. Now ntoskrnl.exe launches wininit.exe, which then launches winlogon.exe (and is responsible for relaunching it in case of its failure). It's simply another abstraction layer for security tokens between Ring 0 (kernel space) and Ring 3 (user space), created for the sole role not to give Winlogon sensitive tokens that can be used by old-era rootkits and also for privilege escalation attacks. Now Winlogon is responsible for the current login state, but user sessions are created from Wininit. Fun fact: if you kill Wininit (or csrss), the kernel will bugcheck instantly the same way it did with NT/2K/XP systems. This is because with their termination, a part of cross-ring IPC communication APIs instantly cease to exist, and user space programs can no longer do any I/O, so the control switches to kernel space. And, the cost of patching memory of all running processes to address any newly created IPC is simply too high to even think about running now potentially unstable processes in the user space (what about fixing dangling mutexes, sockets and hardware queues?) The system termination/forced reboot is just the safest way out there. Yeah, killing those processes is the exact Windows counterpart of killing init or systemd in POSIX systems.
@timmy9222 жыл бұрын
*Weird Ending unlocked: Windows *10* and *11* traveled back into 2000s
@rosemaryholloway4141 Жыл бұрын
It doesn't do that
@waynenathanieltheanimator2 жыл бұрын
Oh Yeah The Very Rare Windows 11 Classic theme is Here. So Interesting
@DohiMissed3442 жыл бұрын
its kinda like killing the process of dwm
@auroradotrocks2 жыл бұрын
stop Talking Like This
@sayaaep2 жыл бұрын
I like all content of Nobel tech
@waynenathanieltheanimator2 жыл бұрын
@@auroradotrocks I am a Plotagoner By The Way. I am a Plotagon user. Haha Better watch my vids to learn more
@lemonadesnake2 жыл бұрын
@@waynenathanieltheanimator doesn’t give you the right to talk like like a weirdo
@merbudd2 жыл бұрын
<a href="#" class="seekto" data-time="146">2:26</a> ah yes my favorite program included with windows, *Tas*
@alexbalan_56232 жыл бұрын
It got glitched so that's why (it was about to log off, and then it logs in for you)
NT 4-XP: Emergency shutdown (makes sure no process does harm) Vista-8.1: Emergency logoff (makes sure no user program does harm) 10-11: Failsafe logoff (makes sure the programs exit gracefully) Winlogon supplies a basic theme for the Windows Shell to render properly. Otherwise, you would have nothing as themes load after you log in. DWM and Explorer has failsafes for this since Windows 8 (as UWP toolkit needs DWM).
@0xEARTH2 жыл бұрын
so the reason it takes a bit for 10 and 11 for seeming bugged before logging off is because it's properly exiting programs, but doesn't have the proper information to render themes etc. properly?
@AshcroftConnorYTwillbetaken2 жыл бұрын
The announcement of Windows 11 just made Martin focus more on Windows content rather than Apple content
@C-Midori2 жыл бұрын
<a href="#" class="seekto" data-time="59">0:59</a> The process of Windows XP terminating into the BSOD is pretty ominous. Comes to show how fast crap can hit the fan!
@christiankm88202 жыл бұрын
"crap can hit the fan" i've never heard that before
@catwacatwa Жыл бұрын
if you pause it right on time before it bsod it shows the classic theme with bigger taskbar
@andremckenna20079 ай бұрын
@@catwacatwai saw it without pausing
@davidhalasz19742 жыл бұрын
Windows 11 in the rare classic theme.
@atsizbalik2 жыл бұрын
with glitchy
@Narobloxx2 жыл бұрын
Are you talking about me?
@Narobloxx2 жыл бұрын
@Google Account bruh
@Narobloxx2 жыл бұрын
@Google Account he’s my brother
@Narobloxx2 жыл бұрын
@Akhilesh Sattanathan yea I changed my name so I have to change my logo
@worldknowledgepost47052 жыл бұрын
Wow that is awesome man!
@Ruangames3682 жыл бұрын
for the first time vista didn't got a blue screen ending a critical process
@akm_anisuzzaman Жыл бұрын
suuui
@phauloriquelme26572 жыл бұрын
Ending winlogon.exe on Windows XP and earlier, can show a bsod (Blue Screen of Death). Ending winlogon.exe on Windows Vista and later, you can be logged off.
@aanjaneya_meaow2 жыл бұрын
so what i noticed in windows xp+ is that the theme reverts to classic theme for a millisecond and then causes bsod/logs off the user it also happened in win vista/7 but it was much more tough to notice it
@user-jk4zt3lc8d2 жыл бұрын
And the background changes on xp
@DavidTPOTTheGreatGuy Жыл бұрын
The exact times were: XP: A 3rd of a second (20 frames) Vista: 5% of a second (3 frames) 7: Roughly 12% of a second (7 frames)
@greenknight90002 жыл бұрын
It's quite interesting seeing Windows XP actually show the process of entering Text Only mode as the drivers get disabled for the Bluescreen
@TheLukasz0322 жыл бұрын
@@kreuner11 - that is happening because on these systems GUI relies on the presence of DWM, which cannot function without Winlogon and also casually stops. (DWM handles window compositing and UX theming beginning with Windows Vista and requires exclusive GPU control.) And also, beginning from Vista, Winlogon no longer maintains cross-ring APIs (Wininit handles them now), so its death won't do much to the core system stability.
@QuantumScratcher2 жыл бұрын
Windows NT 4.0 to XP: blue screen of death Windows Vista and 7: logs out Windows 8.1: 'shuts down' and logs out Windows 10: 'shuts down' and breaks UI; windows in Classic theme Windows 11: same as Windows 10 but no icons on taskbar
@therobloxianstar46892 жыл бұрын
thanks.
@trailie21 Жыл бұрын
Interesting things happened differently. Windows NT 4.0 - Windows XP was a blue screen. Windows Vista to Windows 8/8.1 logs off the user. Windows 10, 11 just blacks out the wallpaper plus the taskbar doesnt work perfectly. Then the windows look like themes in Windows 10 when you end DWM (i guess it is the same or not)
@What00054 Жыл бұрын
You also get logged off on windows 10 or 11 you just see classic theme for 10 second
@andremckenna20079 ай бұрын
And right after, it also logs off the user but it takes more time than vista/7/8.x that is instantly
@lenni-builder2 жыл бұрын
I think the moon icon of winlogon.exe in older versions is from the NT 4.0 "Safe to turn off comouter" message, isn't it?
@FoxyVulpes2 жыл бұрын
yup!
@lenni-builder2 жыл бұрын
@@FoxyVulpes Why was it removed :( Looked cool
@FoxyVulpes2 жыл бұрын
@@lenni-builder update & modernisation - I had Windows NT 4 on a Pentium 3, and that message didn’t show up - instead, my PC shuts off, like a modern PC today. (yup, Windows NT 4 CAN do that, if you know, how!)
@XTRgames20242 жыл бұрын
if you don't like correction don't click "*Read more*. *computer
@FoxyVulpes Жыл бұрын
@commie-tdn actually, it was APM, not ACPI
@eduardocrafts Жыл бұрын
Your new channel icon is soo cool
@NikobellicGTA2 жыл бұрын
Nt 4.0 to XP: Entire OS crashed/BSOD Vista to 11: Logs you off sometimes glitching vista safe mode👉👈
@notsilv3rАй бұрын
winlogin literally went from making your computer die and give you a fatal error to signing you out. thanks windows vista!
@AstralSnowstorm61572 жыл бұрын
Windows NT 4.0 - Windows XP : SYSTEM HALT Windows Vista - Windows 8 : Logging off... Windows 10 & 11 : Congrats, you totally borked visual themes, Logging off in a few seconds...
@KauH92 жыл бұрын
Vista-11 OK its fine just.... Windows 11: *My Theme Glitched*
@masonjess9972 жыл бұрын
I love your videos
@m2chip2 жыл бұрын
Whenever I end it on windows xp, it just goes to classic theme for a second then shuts down
@alexbalan_56232 жыл бұрын
It will crash instantly and your PC will experience BSOD
@lukeonuke2 жыл бұрын
SP2?
@m2chip2 жыл бұрын
@@lukeonuke SP3
@brianbuddy2ACP5 ай бұрын
If you're using VirtualBox like I do, then, it has a weird issue that might even be a long standing bug that doesn't allow the short BSOD to display. If one occurs in a VM, it just shuts down the VM. IDK why. FTR, the long BSOD will display no problem, and both VMWare and Virtual PC 2007 can display short BSODs without issue. Though it should be noted that in VPC, if automatic restart on system crash is enabled, which it is by default in Windows XP and newer, it won't show the BSOD, and just go straight to a restart.
@StopNalvaCardozoTeam Жыл бұрын
Hi, Martin! You are my favourite KZbinr
@VistaSE60042 жыл бұрын
After ending "winlogon.exe", every Windows OS (NT 4.0 - XP) gets a blue screen of death from Windows Server 2003 until Windows Vista - 11, because, if you end "winlogon.exe", you will go back to the logon screen.
@Nicholas_Steel2 жыл бұрын
So in older Windows, the computer will crash if you close it. In Vista and newer the computer will log you out. the DWM.exe process is tied to Winlogon.exe, if you close the latter the former will also close. If you start winlogon.exe dwm.exe will also start. One of the tricks people had for forcing the old UI without the DWM handling vsync was to suspend winlogon.exe and close dwm.exe, then resume winlogon.exe. This would prevent winlogon.exe from automatically restarting dwm.exe... the problem is that a major Windows 10 update in 2018 resulted in suspending winlogon.exe deadlocking the computer, so this trick no longer worked.
@arkak420 Жыл бұрын
i love how all windows have errors and stuff but Vista, 7 and 8 just log you off
@AbbyHaffizi2 жыл бұрын
1 word for xp: Legend
@veto_real2 жыл бұрын
Thegend?
@chipdacat2 жыл бұрын
2 word for xp: Poor
@Joshwoakes2 жыл бұрын
Since when does Windows XP BSOD when you kill winlogon.exe? For me everytime I have killed winlogon.exe in Windows XP it just continues running for like a few seconds and then abruptly shuts down completely with no BSOD. like the entire system just powers off or in the case of a virtual machine, it just closes the virtual machine. However if you kill smss.exe and then kill winlogon.exe then the system will continue running and somewhat function normally but with no theming or sound and no way to shut down without force. Unless that's virtualbox only thing or a version specific thing?
@TheLukasz0322 жыл бұрын
> "somewhat function normally" Press X to doubt. This way you eliminate half of the IPC API between user and kernel space, which has implications every program you have opened doesn't have access to the hardware (no I/O, no proper privilege separation, etc.). This is called an unstable state - if you achieve an unstable state and continue operating, the system may behave unexpectedly, including hardware damage (on physical machines) or a virtualization platform complaining someone overstepped the boundaries.
@Joshwoakes2 жыл бұрын
@@TheLukasz032 When I said somewhat function normally. I meant the OS will be in a broken and unstable state but you can still do stuff, atleast in a VM although be it limited and glitchy. As for real hardware, i was tempted to try it on an old laptop that i don't care about much but I decided not to as there is some data on there that I didn't want to risk losing at the time. However I did try killing the winlogon.exe process on that laptop shortly after posting that comment. And yeah Windows XP does actually blue screen unlike in virtual box where it just shuts down the VM abruptly if smss.exe is still running. Also I personally wouldn't even recommend anyone attempt to force an OS or any software to run in a broken and unstable state outside of a VM due to the risk of losing data or possible damage.
@bimoloverivi6 ай бұрын
On Windows Vista-8.1 ending winlogon.exe equals to Emergency logoff
@_shevakadu52122 жыл бұрын
Windows XP is satisfying
@waynenathanieltheanimator2 жыл бұрын
The same. Because it has The Animation as well
@pinstripecool342 жыл бұрын
Yea even to this day I still think XP is the best looking version of Windows its so clean yet simple.
@KnoxieOS2 жыл бұрын
With windows so when he kills it you can see the theme pretty much die off
@JasonPegasus Жыл бұрын
if you kill the process in Windows 10 while in the login page, it Will login and Will corrupt all fonts weirdly, it's curious
@_IceCreamBunny_ Жыл бұрын
the ones where they blue screen say fatal error. now we should have a evolution of fatal error screens
@meowindows10422 жыл бұрын
I see old versions of windows to windows XP when I turn off winlogon.exe, I don't know if it goes to windows like vista to 10
@therobloxianstar46892 жыл бұрын
Next: Ending ntoskernel.exe in different Windows versions!
@chipdacat2 жыл бұрын
Yea
@Kiki79250CoC2 жыл бұрын
It's like stopping your heart, so i'm 101% sure it will crash the system.
@lawrenceclementeshorts4892 жыл бұрын
I don't know why did the fatal error screen came out when you end it's task in older versions on windows
@Daventent2 жыл бұрын
Interestingly, on Windows XP, I never saw a BSOD while on Windows 10 about 10 times
@marcelohidalgo77132 жыл бұрын
Does this little Action affect my System deeper? I use Windows 10.
@gasmaskedcitizen2 жыл бұрын
tld;drNo, it does not affect your system. Winlogon.exe is an application that holds and manages the current session, but not with the methods you think it does. It stores an important flag that basically means "This person has logged in and is using the PC.". When you exit your session, shut down your computer or just lock it, winlogon is also terminated. If you terminate the app using Task Manager, it will act accordingly and lock your session because there is no application that would hold the flag "This person has logged in and is using the PC". You can then continue and use the PC normally.
@snowmaske27 күн бұрын
Classic theme on the XAML taskbar? interesting..... <a href="#" class="seekto" data-time="171">2:51</a>
@robsontetsuo9817 Жыл бұрын
I liked your video
@Aaa967632 жыл бұрын
How do you delete winlogon.exe anyway? When I click end process while it’s highlighted, it says “This task can’t be ended because this is a critical task”.
@kirilvelinov77742 жыл бұрын
Ultra OS(2003-2017) end winlogon.exe Shows black screen of death Ultra OS XP(2010-) end winlogon.exe Actually logs off the user
@kirilvelinov77742 жыл бұрын
Your computer unexpectedly logged off Ultra OS is restarting...
@samyirnatene19682 жыл бұрын
<a href="#" class="seekto" data-time="113">1:53</a> wow you got poweriso cool bro
@rosedantas9295 Жыл бұрын
Finnaly a fast way to logoff
@kernel3782 жыл бұрын
I once ended Winlogon.exe on Windows 7. It logged me off, but there were no user accounts until I restarted
@AKASHIMAINCHANNEL2 жыл бұрын
Its safe in vista,7,8,8.x,10,11
@DohiMissed3442 жыл бұрын
<a href="#" class="seekto" data-time="16">0:16</a> when i run literally anything on my computer:
@therobloxianstar46892 жыл бұрын
BSOD 💀
@SatuD120kmk Жыл бұрын
on Windows Vista, 7, 8, 8.1, 10 and 11, when you end Logon.exe, you basically Logoff
@75rxREDSTONE2 жыл бұрын
Next video: Deleting CONHOST.EXE on different versions of Windows
@SomeRandomPiggo2 жыл бұрын
that will just break cmd wont it?
@windowsxp7expert-official6262 жыл бұрын
Winlogon.exe ended process in log off <a href="#" class="seekto" data-time="78">1:18</a>
@christiankm88202 жыл бұрын
well you can tell windows is getting more resistant...
@alexbalan_56232 жыл бұрын
Me: Can you handle without winlogon.exe? Windows 95-XP: NO, it will break SYSTEM >:( (Crashes and BSOD occurs) Windows Vista 7-11: YES, it's fine as long as you don't mess up the SYSTEM :) (it will automatically log you off instead of crashing) (Windows 10 and 11 got glitched for some reason as well as interface with explorer.exe and taskbar - It will log you off anyway without data loss or BSOD and it will let you log in without major problems) Note: Ending winlogon.exe is like ending csrss.exe (for Windows 95-XP)
@alexbalan_56232 жыл бұрын
Idk why Windows 95-XP cannot handle/work without Winlogon.exe (All Windows versions can't work without csrss.exe)
@alexbalan_56232 жыл бұрын
Speaking of winlogon.exe, fake csrss.exe can be ended or deleted without making it crash (it may be a virus or fake execution file which is fake)
@TheLukasz0322 жыл бұрын
@@alexbalan_5623 - that's because Winlogon (until Vista) was ran directly by the NT kernel and had the duty to expose cross-ring APIs to the user space. On x86 protected mode (kernel and user space separation) programs all do their job (communicating with hardware, displaying UI, reading/writing files, etc.) via exposed kernel space APIs. Without those in place, the whole program operation was meaningless, including system processes - only kernel and drivers could operate.
@x-a-12382 жыл бұрын
this is an advantage for malwares
@matheussimoes8309 Жыл бұрын
This Windows 10 classic which logon application, what happens exist?
@libertyernie2 жыл бұрын
The reason the window borders are so thick in Windows 10/11 in classic theme is probably to make them easier to grab and drag. I think I changed mine once to be narrower and then when I rebooted and went back to normal, they were harder to grab.
@DanielClear22 жыл бұрын
They are that thick because those are the values used by the Aero Basic theme. It doesn't actually switch to Windows Classic theme. It just uses the last available theming layer [DWM Compositor (Aero Glass) > Visual Style (Aero Basic/Luna) > Color Scheme (Classic)].
@tflsh2 жыл бұрын
I think because WinLogon has a ThemeSection handle, and if it is closed programs use classic theme after the handle is closed. Programs left open remain the same.
@ANormalWintrovert2 жыл бұрын
Can anyone please send me the link to the "process explorer" for windows nt 4.0? I really need it...
@coolplayer8322 жыл бұрын
When you end winlogon.exe,DWM will also ended.
@Ruangames3682 жыл бұрын
windows xp just got a dark blue background and internet explorer suddenly spawned in the desktop,that is why peoples love xp?
@a7dje07vw2 жыл бұрын
I just found out that Windows 11 has it
@lalithadityabaggam Жыл бұрын
mac lovers are loving this!
@SlavchoGamerLegend112 жыл бұрын
on my windows 7 i crashed Winlogon.exe and it showed the lock screen
@AYUKO_OFICIAL2 жыл бұрын
How to kill the windows XP: Trow the "my computer" on the Ribbish Bin
@arieeka812 жыл бұрын
Request Ending Winlogon.exe in beta version of windows
@artosik_pc Жыл бұрын
<a href="#" class="seekto" data-time="145">2:25</a> classic theme on windows 10😳
@nfshp2mwgaming5 ай бұрын
ending windows winlogon.exe suddenly bsod:nt 4.0-windows xp have the must login again:windows vista-present os
<a href="#" class="seekto" data-time="33">0:33</a> Windows 2000 <a href="#" class="seekto" data-time="69">1:09</a> Windows Vista <a href="#" class="seekto" data-time="122">2:02</a> Windows 10
@user-hepgon2 жыл бұрын
WOWW
@AD-HTP Жыл бұрын
You always love the first song?
@maxlee69962 жыл бұрын
What XP theme are you using? It looks great.
@cristianospohr692 жыл бұрын
Theme of the gods
@blue_dragonized_dolphin2 жыл бұрын
Royale (Energy Blue)
@chennyoechenjeh6 ай бұрын
Luna
@NotThatEpic7492 Жыл бұрын
all killing winlogon.exe does is kill the user session winlogon.exe was running on i dont get why it would cause a bsod up to windows xp
@hung3011official Жыл бұрын
Excuse me, In WINDOWS Vista,7,8,8.1,10,11, if we Ending Winlogon.exe, what happen?
@danut7330 Жыл бұрын
It simply logs off
@iamsodumbtoday9374 Жыл бұрын
Windows nt4-xp: IF IM DYING YOU'RE DYING WITH ME Windows 7-8.1: could've clicked log out but whatever Windows 10-11: you lost your data btw here's a vista safe mode desktop because why tf not
@WindowsSeven76017 ай бұрын
In Windows 10 1709 it make logon unusable (like deleting authui.dll)
@Go_8834 Жыл бұрын
XP goes Buh bye
@EpicnoobieREBOOTAGAIN Жыл бұрын
NT 4.0-XP : Blue screen of death Vista-8.1 : Can't login 10 And 11 : Completely black and automatic login
@chistosito515 Жыл бұрын
man can you help me? I cant enter to windows 10 because of winlogon
@thiemnguyen7052 жыл бұрын
In my pc its deletes my account if i restart, my pc in a boot delete.
@UrlocalViviana Жыл бұрын
The Best way to get bsod c000021a on windows nt 4, 2000and XP
@mariodykstra65552 жыл бұрын
There’s an “eep” in the URL!
@pawer_themaw2 жыл бұрын
Really interesting that Vista+ don't BSOD, just log you out. Pretty good if, for some reason, your Start Menu doesn't work and you have to shut down the PC.
@Seoul4083 Жыл бұрын
Windows NT 4.0 (<a href="#" class="seekto" data-time="11">0:11</a>)~Windows XP (<a href="#" class="seekto" data-time="58">0:58</a>) if you end winlogon.exe without BSOD, kill other process (exclude winlogon.exe, csrss.exe, System Idle Process, explorer.exe) then kill winlogon.exe
@AngeloAcevesEN11 ай бұрын
*Windows 95, 98, ME, & Server 2003 has left the chat*
@samyirnatene19682 жыл бұрын
AAAAAAAAAAAAAAAAH! HAVE YOU LOST YOUR MIND!!!! I WILL NEVER DO THIS IN WINDOWS XP IN VIRTUAL BOX
@thisisa2 жыл бұрын
It is not permanent damage
@_xwtk2 жыл бұрын
Kid calm down.
@thiluongtran1582 жыл бұрын
WOW!
@thisisbup2 жыл бұрын
error bup.exe has unexpectley been terminated. restarting...
@TechnikTil2 жыл бұрын
<a href="#" class="seekto" data-time="60">1:00</a> a blue screen as the desktop background for a sec
@quzsewiti.0_02 жыл бұрын
i tested it on Windows Longhorn 4074 and its just logged off
@robsontetsuo9817 Жыл бұрын
You can use windows vista ultimate for me🥺
@amenbahroun.8694 Жыл бұрын
Plzzz how to fix that i accidently do it on my windows 8.1 😔😔😢
@canceltheuttparmy2 жыл бұрын
noic
@SylviaMC_2 жыл бұрын
Let's try
@sangitachakraborty2465 Жыл бұрын
I love how windows 11 has 100% cpu usage lol
@matheussimoes8309 Жыл бұрын
Ending winlogon.exe windows NT 4.0 to xp bsod logon(Crash to this Login) and windows Vista to 11 this login. Windows 10 and 11 glitchy to Windows Classic the task manager.
@KiaK7Electric2 жыл бұрын
Before vista: bsod After vista: lock screen
@PKXDWINDOWS321MC_REAL2 ай бұрын
UMM I'VE BEEN SUBED BEFORE NOBEL TECH WAS VEFIFIED