why is XBOX live services running on windows server
You reminded me of when i was at an MSP and we had this dental client. And they had some actually pretty cool software that processed 3d X-rays and generated a 3d model and would point out various types of potential issues. Now this was like ~2014 so before photometry or AI was really a thing so it was really impressive.
But to compute that stuff in real-ish time (like under 30 seconds, so by the time the patient walked back to the exam room) you had to offload the processing to a Windows server, but that worked fine.
But like everything, Windows updates continue ever “”“forward”"’ and eventually they added the Xbox game bar. I didn’t think anything of it and just left it running. About a year later and a few updates to the dental software later I am looking at their server and figure “hey, I should disable this. Its a server after all”.
Bad mistake. Their software stops working so now they can’t take any type of scans. I’m trying to figure it out, I’ve got a team of engineers looking at this with me. We can’t figure it out. Everything looks fine except the process just won’t start. No error message, no wrong looking logs. The executable just never starts.
Well turns out at some point along the line they picked up a dependency relying on Xbox game bar for this program to run. So the solution was to just leave the service running lmao.
This is honestly more of a story about bad programming than windows server nonsense but you made me think about it. I wish I figured out what was actually depending on game bar but I left shortly after that. Actually before the patch was pushed out haha
You reminded me of when i was at an MSP and we had this dental client. And they had some actually pretty cool software that processed 3d X-rays and generated a 3d model and would point out various types of potential issues. Now this was like ~2014 so before photometry or AI was really a thing so it was really impressive.
But to compute that stuff in real-ish time (like under 30 seconds, so by the time the patient walked back to the exam room) you had to offload the processing to a Windows server, but that worked fine.
But like everything, Windows updates continue ever “”“forward”"’ and eventually they added the Xbox game bar. I didn’t think anything of it and just left it running. About a year later and a few updates to the dental software later I am looking at their server and figure “hey, I should disable this. Its a server after all”.
Bad mistake. Their software stops working so now they can’t take any type of scans. I’m trying to figure it out, I’ve got a team of engineers looking at this with me. We can’t figure it out. Everything looks fine except the process just won’t start. No error message, no wrong looking logs. The executable just never starts.
Well turns out at some point along the line they picked up a dependency relying on Xbox game bar for this program to run. So the solution was to just leave the service running lmao.
This is honestly more of a story about bad programming than windows server nonsense but you made me think about it. I wish I figured out what was actually depending on game bar but I left shortly after that. Actually before the patch was pushed out haha