Effects are disabled after ReShade GUI is closed.

(First time posting)
Title. I installed ReShade 3.1.2 for Warframe after deleting an existing 3.0.8 installation (On a side note, the installer says that it fails to extract the downloaded archive, even though it succeeds. I tested the older 3.0.8 installer as well, and it also suddenly had this issue.)

Now, after launching Warframe, I press Shift+F2 and everything works well, except that I have to set the paths for the Shader and Texture directories manually (possibly due to the installer error?). But after closing the gui, pressing Shift+F2 again, all effects are disabled. I also tested using the exit button in the GUI, and it has the same effect. This isn't as simple as me having accidentally set the Effects Toggle Key as Shift+F2. I tried a few different keys for it, in fact, but to no effect.

Here's what dxgi.log has to say:
pastebin.com/zfnkRkuD
A few warnings for some shaders, but I can't say whether they're relevant here.

Sorry if this is already a known issue, didn't see anything about it in the forums.
Thanks in advance.

My solution isn't really a solution, but it's the best I can offer:
Turn down the opacity of the window to its minimum setting and then make the window as small as you can. You won't notice it if it's small and placed in a corner, and you'll still have the effects.
I know many games have this issue, and I have no idea how to fix it.

I guess that's a possible workaround. Still, it's very strange, as ReShade used to function properly with Warframe, so I don't think it's the game itself that is the problem.

I'm having this exact same issue for ReShade in FFXI, if anyone knows of a solution other than moving the GUI to the corner this would be awesome. I don't really want to do this every time I log in. Thanks!

Somberyu wrote: I guess that's a possible workaround. Still, it's very strange, as ReShade used to function properly with Warframe, so I don't think it's the game itself that is the problem.

Yeah it's a bad workaround, but at least it works.
I know games that have been working with previous ReShade versions before, but after testing older versions, the same issue is still there. Perhaps a driver issue or a game update?

Does this happen if you enable the FPS or time display in the settings too?

crosire wrote: Does this happen if you enable the FPS or time display in the settings too?

... It doesn't. Nice.
I assume that having them on forces the program to stay on?

Have you accidentally turned the toggle key to Shift F2? because you can accidentally do that.

HadouGun wrote: Have you accidentally turned the toggle key to Shift F2? because you can accidentally do that.

Just noticed I've got the same issue in The Witcher 3, just didn't notice it because I had fps displayed all the time. Also, unfortunately it's not the toggle.

HadouGun wrote: Have you accidentally turned the toggle key to Shift F2? because you can accidentally do that.

You didn't read the OP well enough...

I think I had a similar problem not that long ago, the causes was a shader had to be lowered in the pipeline order to correct the issue.

It was Magic Bloom IIRC.

Zexen wrote: I think I had a similar problem not that long ago, the causes was a shader had to be lowered in the pipeline order to correct the issue.

It was Magic Bloom IIRC.

Hey, nice one, it helped with Witcher 3. Had to drag it all the way to the top instead of the bottom, but thanks for the input (but maybe that's what you meant with "lowered in the pipeline" in the first place).