In a recent move aimed at enhancing Windows security, Microsoft has banned Winring0 for a few days, a low-level driver extensively used by many monitoring, system information and overclocking tools made by the community, allowing them to access low-level information. This change has stunned many, discovering their favorite software didn't function anymore.
At OCCT, we believe that innovation must continue, even in the face of industry-wide disruptions. That's why we've taken proactive measures to provide a fully compliant, legitimate, and free driver replacement. Let's dive into what this change means, and how we're turning it into an opportunity to better serve the community.
Why Did Microsoft Ban Winring0?
The decision to ban Winring0 is part of Microsoft's ongoing commitment to enhancing the overall security of Windows.
WinRing0 isn't malicious by itself. However, it allows anyone to access any low-level function as they please, defeating any kind of security Microsoft implemented in Windows relatively recently. Drivers must be contained to their own devices/purposes, and WinRing0 is giving you access to everything.
While precious and very valuable for every tinkerer and enthusiast out there, it is a gaping wound Microsoft is trying to close forcefully. As this driver was used by a lot of applications - even by some big companies under the hood for its ease of use and to gain some development time - the grace period is coming to an end.
OCCT's Response: A Safe and Compliant Alternative
At OCBASE, we understand this risk, and actually foreshadowed it in our latest video, recorded right before the ban and covering this issue. We don't want to stay inactive when some of our beloved software are in danger.
With the Linux release of OCCT, we created our own monitoring engine. To bring it to Windows, we needed a driver. The decision was simple : make a version of that driver that can replace Winring0 all while complying with Microsoft's security policy.
We already have the certificates needed to develop this driver, and development was planned to start soon. We propose to make it available to others so they can use it themselves.
The driver will be completely free for the community. We stand firmly by our values : if you're not making money with your application, or even just pocket change or covering your costs, we will offer it for free. However, if you are a company, or if you start making a chunk of money with your app, we will ask you to help fund the development.
As always with our development, and also for security purposes, the driver will be closed source. We know that may be a disappointment to many, but we believe strongly that having an option here, albeit imperfect, is better than stopping the development.
Collaboration opportunities and gaining access to the driver
First, development is just started, so there will be some time for us to finalize it, and get it approved by Microsoft. If you're interested, please contact us so we can have a chat and see what we can do together !
Contact usMicrosoft's decision to ban Winring0 marks a pivotal moment for the performance monitoring and testing community. We, at OCCT, are dedicated to provide a robust, compliant, and accessible solution for everyone affected by this change. We were born from the overclocking and tinkerers community. We received a lot over those 20 years. We will continue to give !
