Author Topic: ReHIPS vs Win10 Core Isolation/Memory Integrity  (Read 528 times)

Umbra

  • Active Testers
  • Hero Member
  • *****
  • Posts: 575
  • Beta tester
ReHIPS vs Win10 Core Isolation/Memory Integrity
« on: February 01, 2019, 02:02:08 pm »
hi,

Just to say there is no problem at all  ;D ;D ;D , they are compatible (which isn't the case with many security apps)
It is in such situation that your design for ReHIPS by using Windows's mechanisms make all sense.

Cheers.

fixer

  • Administrator
  • Hero Member
  • *****
  • Posts: 1445
Re: ReHIPS vs Win10 Core Isolation/Memory Integrity
« Reply #1 on: February 01, 2019, 07:23:57 pm »
Thanks for the heads-up. We haven't thoroughly tested these features yet, but yeah, looks like it should be completely compatible.

Umbra

  • Active Testers
  • Hero Member
  • *****
  • Posts: 575
  • Beta tester
Re: ReHIPS vs Win10 Core Isolation/Memory Integrity
« Reply #2 on: February 04, 2019, 03:31:48 am »
sadly the feature is way buggy, once enabled (and it does by itself) , no way to turn it off , even using reg tricks...

Alldredge

  • Jr. Member
  • **
  • Posts: 1
Re: ReHIPS vs Win10 Core Isolation/Memory Integrity
« Reply #3 on: April 13, 2019, 04:56:49 pm »
How can it be that it can't be disabled? What do you do then, reinstall Windows?

Umbra

  • Active Testers
  • Hero Member
  • *****
  • Posts: 575
  • Beta tester
Re: ReHIPS vs Win10 Core Isolation/Memory Integrity
« Reply #4 on: May 18, 2019, 01:54:14 pm »
How can it be that it can't be disabled? What do you do then, reinstall Windows?
if you are lucky it may turns off...

HJLBX

  • Active Testers
  • Sr. Member
  • *****
  • Posts: 496
Re: ReHIPS vs Win10 Core Isolation/Memory Integrity
« Reply #5 on: May 20, 2019, 06:00:40 am »
On one build it works. Then the next build it doesn't.

Microsoft's new SaaS W10 is a disorganized rabble. I have been so advised by industry connections that Microsoft is having serious internal problems with Windows 10 - even after all these years to sort our their self-created messes.

One Microsoft division doesn't know what any of the others are doing.