Kostas Magkos
Всего сообщений: 3
Дата регистрации: 10.07.2017
|
Создано:
10.07.2017 12:03:31
|
Greetings Forum,
When a I try to load the Actual Windows Manager I get the following error (see attached image):
"Unable to execute file in the temporary directory. Setup aborted.
Error 1260: This program is blocked by group policy. For more information, contact your system administrator."
Since I'm the system administrator, I know that this error is due to a software restriction policy blocking executables loading from %appdata% and %localappdata%.
In order to create an exception in the policy, could someone please give me the path that Actual Windows Manager is trying to load from?
Thank you in advance,
Kostas
|
Bogdan Polishchuk
Администратор
Всего сообщений: 4114
Дата регистрации: 04.04.2012
|
Создано:
13.07.2017 14:06:25
|
 |
Hello, Kostas
| Цитата |
|---|
| could someone please give me the path that Actual Windows Manager is trying to load from? |
Other temporary folder contains the following files: innocallback.dll, affiliate.dll, utils.dll, _shfoldr.dll and _RegDLL.tmp.
So, if there is ability to exclude the files by their names, then try to exclude the executable .tmp file and if it's required the .dll files.
If there is no such ability, try to temporarily change location of the System Temp folder. . The TEMP and TMP variables should be changed for the user that you run the Actual Windows Manager setup as.
Best regards.
|
Kostas Magkos
Всего сообщений: 3
Дата регистрации: 10.07.2017
|
Создано:
13.07.2017 14:53:49
|
Hi Bogdan,
Thank you for your answer.
I' not blocking DLLs, neither TMP files. Actually, I've already installed AWM, the problem appears when I try to load it.
The weird thing is that Actual Windows Manager was working just fine for some time. The problem appeared when I added JAR files in the list of designated executables.
Does Actual Windows Manager use/run any JAR file (or any other file) from %appdata% or %localappdata%, when loading?
Regards,
Kostas
|
Bogdan Polishchuk
Администратор
Всего сообщений: 4114
Дата регистрации: 04.04.2012
|
Создано:
14.07.2017 16:42:43
|
Kostas,
Actual Window Manager doesn't use any JAR files. But it stores the configuration files in this folder:
%appdata%\Actual Tools\Actual Window Manager
Could you try to enable the "Run the library from the installation folder" option (Configuration module > Options > General > Run the library from the installation folder) and see whether it solves the problem?
Best regards.
|
Kostas Magkos
Всего сообщений: 3
Дата регистрации: 10.07.2017
|
Создано:
17.07.2017 13:47:29
|
Hi Bodgan,
Well, as it turned out, it was a really nasty coincidence!
Actual Windows Manager had downloaded an new version, waiting to be installed. The previous day I had added JAR files to the block list, so when I booted and AWM tried to update itself, I got the policy block message.
I've installed the new version (8.11) and everything is back to normal.
Best regards,
Kostas
|
