It’s not because you can’t check on Windows, that it doesn’t exist ! I’m sure there are a lot of different boot issue logs in Windows, they are just hidden behind a “beautiful” Welcome page.
You’re making a huge assumption based only on the fact that Windows hides these logs from the end user.
I’ve had line of sight to those logs through a system that automatically highlights those errors and warnings for something like eight years now, for a fleet of over 1000 Windows machines at the start which is now roughly 5000 total.
In that time I’ve seen less than 200 graphics driver issues logged, and they all were on machines with failing hardware.
Yes, they are not anywhere as visible to the end user as they are on Linux, but they are also significantly less common (graphics issues in particular).
Also, if the warnings are meaningless, why display them to the end user? It’s just more noise that actual problems can sneak by in.
Let me check dmesg:
or
Let me know if more examples are needed ;)
It’s not because you can’t check on Windows, that it doesn’t exist ! I’m sure there are a lot of different boot issue logs in Windows, they are just hidden behind a “beautiful” Welcome page.
You’re making a huge assumption based only on the fact that Windows hides these logs from the end user.
I’ve had line of sight to those logs through a system that automatically highlights those errors and warnings for something like eight years now, for a fleet of over 1000 Windows machines at the start which is now roughly 5000 total.
In that time I’ve seen less than 200 graphics driver issues logged, and they all were on machines with failing hardware.
Yes, they are not anywhere as visible to the end user as they are on Linux, but they are also significantly less common (graphics issues in particular).
Also, if the warnings are meaningless, why display them to the end user? It’s just more noise that actual problems can sneak by in.