Some very nice people from #pyqt freenode channel helped me to test the repo and none of them were able to reproduce the issue, the python versions and platforms they used were: Pyqt was installed on the virtualenvs using pip and the versions are these ones: > QtCore.QT_VERSION Tested with a couple of virtualenvs on win7: Output of python main.py 2: (p圓52) D:\sources\personal\python\pyqt\mcve>python main.py 2ĭ:\virtual_envs\p圓52\Scripts\python35.zip If I run python main.py 2 the process hangs (probably in a infinite loop) without giving any error.If I run python main.py 1 everything works as expected.QtWidgets.QApplication(sys.argv), let's say I got this little snippet main.py: import sys
For most users, having the WinRing0 driver installed on their computer is less of an issue compared to having an expensive gaming laptop that is completely unusable for anything more strenuous than surfing the net.I'm having troubles importing modules after the line The computer industry does not seem to understand that people have had to install ThrottleStop not because they want to but because they have to. This would allow safe access to these functions without having to use any third party software that depends on a dangerous driver to function. All of ThrottleStop's functionality could easily be built into the BIOS but OEMs like Dell, HP, Asus, etc. They depend on it so their over priced, under performing laptops are not quite so miserable. The bigger problem is that over 3 million people have downloaded ThrottleStop from TechPowerUp alone. Maybe it will force Microsoft to finally deal with this issue. Why have they not done anything? Riot Games decision to block the dangerous WinRing0 driver is a good thing.
Microsoft have known about this issue for years. I agree that the WinRing0 driver in the wrong hands has proven to be dangerous so it is up to Microsoft to block any software that tries to use or install WinRing0. That function does not allow memory access which is what anti-cheat software is trying to prevent. ThrottleStop does use the WinRing0 driver and it does access the vulnerable Wrmsr command.
0 kommentar(er)
