Mirillis forum

Running a fully patched Windows 8.1 x64 installation. All AV software and access control software has been disabled while trying to diagnose the problem described below.

Action! was working fine until I tried to set an overlay image. At first, the application asked for a drive that didn't exist, so I ignored that and then the in app browser let me search around my filesystem as usual.

Once I selected the image, the application crashed.

I attempted to restart the app and was given this popup error:

[CRITICAL ERROR (101)]
Failed to initialize product. Please try reinstalling.

I looked around the windows event logs and could not locate anything regarding the error...

I uninstalled Action!, deleted the local and roaming mirillis profile data, deleted the HKEY_CURRENT_USER/Software/Mirillis registry keys and reinstalled the software only to be met with the same error.

Has anyone else ever encountered this before?

The only other prior change to the system I can think of is that I recently copied my Users folder over to a different disk to offset writes to my local SSD. C:\Users is a symbolic junction link now that points to Z:\Users

I haven't come across this myself however just a thought. Try updating the file save paths in the HKEY_CURRENT_USER/Software/Mirillis registry keys to the actual paths in your case (z:\users).

Error 101 occurs when Action.exe or dwm.exe are listed on your firewall list.

And what is the solution? Deleting Action from the whitelist everytime i start it is pretty anoying (and feels just like a bug, it should be possible to keep Action whitelisted ...)

Cu Crono

Please contact our support team about this via support@mirillis.com.

Radi is correct.

This will happen when dwm.exe is listed as a windows firewall rule. I removed the rule for dwm.exe and I can now launch Action! with no further issues. I am still able to leave Action! binaries in my exception list with no problems.

A rather annoying issues is dealing with dwm.exe. My firewall software expects me to "allow" or "deny" it but I can't simply say "ignore". Smh.

Same issue here, this is incredibly stupid. Why does Action! care that dwm is blocked? Had to abandon use of Glasswire firewall entirely as there's no quick way to search for dwm, but getting same issue with binisoft firewall. Every time I launch action I have to open firewall and remove dwm.exe rule. This is stupid and puts user security at risk.

Same issue here, this is incredibly stupid. Why does Action! care that dwm is blocked? Had to abandon use of Glasswire firewall entirely as there's no quick way to search for dwm, but getting same issue with binisoft firewall. Every time I launch action I have to open firewall and remove dwm.exe rule. This is stupid and puts user security at risk.

Hello!

We are trying to figure out how to remove this inconvenience.