Yeah, I know, this hassle with driver signature enforcement and changing hash algos may be painful when it comes to supporting old OS-s. But unfortunately there is nothing we can do from our side. Apart from this signatures ReHIPS completely supports Windows 7. But we had to rebuild driver to workaround some Windows bugs, so had to follow new signature requirements.
Most of the changes are new features/fixes, I don't remember any serious security issues.
Thank you for your attention. I had already updated the system with those patches you sent me (I tried to run them and it said that those updates were already installed).
When I run Windows update it says the system is already up to date so i dont know if my system is actually up to date or its windows update that is bugged. Anyway, i'll probably continue to use Rehips 2.4 then or install Windows 10 LTSC.
Is Rehips 2.4 still good and secure right? And does Rehips 2.5 RC1 works on Windows 10 Enterprise LTSC?
Thank you again for your answers and attention and sorry for my english.
Most likely that's because we had to move to sha256 digital signature. In old times when Win7 was released sha1 was used and it was OK. But a while ago everyone agreed that something more secure is needed and moved to sha256. And now weaker digital signatures aren't issued, so you can't get it even if you want to. Sha256 is quite new for stock Win7 and it doesn't recognize it. But should accept it after update. I don't remember exact KB though, looks like for Windows 7 you need to install SP1 and then KB3033929 or KB4474419 or KB4054518.
P.S. Having Windows updated is one of strong requirements for ReHIPS if you want to build a secure system.
It's most probably because of the digital signature with sha256, meeting modern security standards. It is not supported by default on Win7, at least not without certain updates. Google it and you will probably find advice how to handle sha256 on Win 7.
I'm having error messages with the hipsgui64 driver on Windows 7(latest version - 7601). It says that windows could not verify the digital signature on the file. The only way to make the software work at all is to use windows in test mode (bcdedit /set testsigning off) or to disable driver signature enforcement everytime i boot the system.
Since i play some games that require battleeye anticheat system and it is not compatible with test mode, i would like to know if there is any way around this problem and if the problem is on my end or the software driver really does not have a valid signature.
I'm using Windows 7 - Version 7601 and Rehips 2.5 RC1.
Hello everyone. We proudly present to you the long-awaited ReHIPS 2.5.0 RC1 DOWNLOAD
We definitely took some time to get it ready, faced some challenges including this COVID thing. But it's all in the past now and RC is ready. Though I don't recommend installing it on critical production systems, it's really stable and most likely it'll go for release as is.
We'd like to express our sincerest and deepest gratitude to beta-testers and other guys (and gals?), who tested, reported problems, endured remote debugging sessions, gave suggestions and really helped a lot to fix issues and shape ReHIPS as it is now. Thank you all very much, we really appreciate it.
Enjoy this release. And as usual, don't hesitate to contact me if you have any questions or suggestions.
Ситуация следующая. Гуглу по неизвестной причине не нравился наш инсталлер, более подробно описано тут https://forum.rehips.com/index.php?topic=9856 Поэтому было принято решение выкладывать его на share-it и сливать окончательно оттуда, а остальные линки делают туда редирект. Но по пока неизвестной причине (идёт переписка с поддержкой) их линки перестали работать. Вообще версии всегда лежат на сайте, например последняя hxxps://rehips.com/ReHIPSSetup2.4.0.zip но из-за странной политики гугла мы стараемся не постить на них прямые линки.