That notification?
Cherry picked, indeed
Today's entry in the pantheon of public whoopsies is not so much Windows falling over as someone sticking a network connection where it possibly doesn't belong. We'd normally say that this was spotted by an eagle-eyed Register reader (which it was – thanks, Alastair), but this network notification has popped up on a giant …
This post has been deleted by its author
Well, those were the primitive bad old days, of course.
In these enlightened modern times, we have the billboarD module of systemd to do that. I think we can all agree that the extra six million lines of code, binary-only billboard config files, and a 16GB bump in the system memory requirements are a fair price to pay.
From the state of the trees outside the station it looks like late autumn (fall), or winter so I cannot imagine there would be a lot of cherries being picked anywhere in the northern hemisphere.
AU/NZ produce decent crops over the typically short season but I imagine air·freighting them to UK/EU would make the fruit a rather expensive luxury item whose sale would be restricted to specialist green grocers etc and therefore unlikely to be advertised to the polloi on billboards outside railway stations.
Or is it an advert for a shonky financial advising business whose details are conveniently obscured by a pop·up from an arguably even shonkier OS?
I know that MS Windows quite rightly gets a lots of stick over borks like these, but late last century when electronic signage was the big new thing, it wasn't uncommon for an ad display in my city centre (Perth, Western Australia) to be replaced by an Apple Mac desktop. However, being the early days of outdoor displays the harsh summer environment destroyed the display within a year or so.
May not be the same issue, but my $work laptop, which also forces Windows 11 onto me, did something similar a while back.
On investigation, I was now showing 3 network devices, in a machine that only has WiFi and a single Ethernet port! I had WiFi disabled, and the 'extra' NIC was also Ethernet, on a machine with physically just one socket.
My guess was that the Ethernet driver had somehow crashed and restarted, but now showed as a new NIC.
Rather than risking accepting changes etc. I just did a good old restart, and all was well (within Windows limitations of 'well'). Not happened since, and I have no idea what the cause was!