MSI (s) (58:4C) [17:05:26:820]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI525A.tmp, Entrypoint: DetectVisualStudio
MSI (s) (58:18) [17:05:26:821]: Generating random cookie.
MSI (s) (58:18) [17:05:26:826]: Created Custom Action Server with PID 836 (0x344).
MSI (s) (58:20) [17:05:26:874]: Running as a service.
MSI (s) (58:C8) [17:05:26:880]: Hello, I'm your 32bit Impersonated custom action server.
Action start 17:05:26: DetectVisualStudio2017.
I just installed Fortran 2020 -- told me to look at the logs, I got a real chuckle from the 5th line
Just for grins, my favorite Microsoft humor (from a few years ago) was a boot-up error message "Keyboard not detected - press any key to continue..."
But I don't think it was intentional humor.
We can think of a wireless keyboard that is provided with an autonomous sleep function in its firmware for conserving its battery usage. A keypress could wake up the keyboard, which can then be sensed by the PC/Laptop. I have never had a wireless keyboard, so I cannot tell from experience whether this scenario actually occurs.
My daughter has a wireless keyboard - well a Logitech one -- it does not wake the computer.
Interesting if you have wake on lan - then you can wake your computer -- but it does not work on wifi so you cannot do it over a cell modem -- which is a real pain for deployed devices.
I did a search on Intel Humour and Steve turned up for his Fortran is not dead poster -- I still have my mug.
Wake on Wireless LAN is possible if the device and driver both support that feature, see https://wireless.wiki.kernel.org/en/users/documentation/wowlan , http://revolutionwifi.blogspot.com/2010/11/wake-on-wireless-lan.html , and https://docs.microsoft.com/en-us/previous-versions/windows/hardware/wireless/wake-on-wireless-lan .