Interesting, I'll need to bow to your larger sample size, though what you describe isn't my experience (sample size of 2). I'm curious though, what types of issues are common enough for you to create an MS ticket? I generally get regular updates for problems that never seem to apply to me in the home use context (with heavy duty CAD and EDA software on mine). I'd say the same for RaspiOS. With frequent updates over the years I've had a single issue that occurred when an update overwrote an RP patched Bluetooth component with an un-patched one, thus breaking Bluetooth. Issue was noted here and a workaround was offered within 24 hours (maybe less). Not bad for little SBCs that take a lot of beating.If enough people start to have the same issues, a ticket is created with MS. We probably average 2 tickets a month with MS. This includes tickets for servers too, not just desktops, but it is the same code base.
Statistics: Posted by lurk101 — Fri Feb 02, 2024 5:42 pm