I guess you'll just have to be "shocked" then!*sigh* I would be shocked to discover that you even tried Linux in the last 5 years.
I guess you'll just have to be "shocked" then!*sigh* I would be shocked to discover that you even tried Linux in the last 5 years.
1. Most people neither know nor care what 'version' they have. They use whatever came with the PC they bought.
2. If the system is not natively Win 11 compatible, it will be 8, almost 9 years old by Oct 2025 when Win 10 falls off support. It would need to be 7th Gen Intel or similar AMD.
Agree with you and I have the same doubts.The question I asked myself was slightly different: "How can this even work a little bit?"
or
"How can this possibly come anywhere near to what people might expect this to do for them?"
I remember old mainframe operators going misty eyed on how they managed to hot-patch around some vendor stupidity by simply stopping the machine from the front panel, and entering instructions and data manually via the front panel switches to jump around them and then having it resume without it.
So that's binary patching without vendor consent about 60 years ago.
On mainframes with perhaps 48K words of ferrite core RAM.
These patch service companies aren't going to get Microsoft or 3rd party source code. They can't proactively eliminate newly discovered vulnerability patterns across the entire OS code base. At the very best they can patch a vulnerability that has been exploited actively enough to come to wider attention, and your main hope would be that it wasn't you, as perhaps the most attractive and biggest target, which created that attention by going down big time.
They also won't get source code for the drivers and the many services and run-time libraries that get included into what today is called an OS, while the patching service might in fact be offered only on the kernel and perhaps one or two other services listed in an addendum you'd have to read very, very carefully to check if that covers a significant part of what you need.
Anyone contemplating this needs to be truly desperate. And thus in no proper mind to make sound decisions.
So, you guys don't know how 3rd party support works??? None of you have ever called Microsoft before and got a non-English speaking support agent on the line??? Really?Agree with you and I have the same doubts.
I am also very scared that nobody in this forum wondered how this could be technically viable. And I'm disappointed that the author of the article, as often happens, wrote a simple press communicate without asking details to "0Patch".
Did you try turning it off and back on again?
Oh, we're wondering...lol.I am also very scared that nobody in this forum wondered how this could be technically viable.
I just ran in to an industrial control system this afternoon that's running WinXP under the hood. I was told once a system is deployed and certified it's not allowed to be updated in any way.There are appliances out there (esp. in the medical world) that are hideously expensive, run Windows at the core and are certified only in their exact shipping config. I've never really understood why the manufacturers of those things don't have upgrade packages (sometimes they do), but the prospect of replacing a $100k+ device just isn't an option sometimes. It can be cheaper to build SCADA like security around the networks those things are on. It why you still see so many installs of Win7 running in hospitals.
Sure, there are many such cases. However, those devices should never be internet accessible for securities sake.I just ran in to an industrial control system this afternoon that's running WinXP under the hood. I was told once a system is deployed and certified it's not allowed to be updated in any way.