It's definitely something to look into if you're in a larger environment. There are several around and they're expensive but you can whitelist applications to run as admin with all kinds of options. If you have money to spend, you can also look into a Privileged Access Manager. It was specifically designed for this by Microsoft but you'll have to download the zip file from webarchive because the original download link doesn't work. The best program for this is called LuaBuglight. You may be able to get it to work with additional shims or you may need to grant write access to specific folders or registry values. If it doesn't run with the app then you'll need to work on figuring out what it's trying to access. It just tell the program to stop asking for them. This isn't a security risk because it does not grant admin rights. ![]() You could alternately just import the reg file and let users run apps that way. Once a shim is imported on a PC you can just double click the app and it will run with whatever settings you applied. If it works you can create shims using the Application Compatibility Toolkit from Microsoft for each application. From there you can make it run as the user, interactive, with highest privileges, and there won't be a UAC prompt. The only way to do this is to create a Task using Task Scheduler. Windows Registry Editor Version without privilege /min /C \"set _COMPAT_LAYER=RUNASINVOKER & start \"\" \"%1\"\"" And if that is the case, then why not just create the task and set startup as parameter. It will add a right click option "Run without privilege elevation" that will run the app with limited user rights. Just writing to confirm that these steps work! I had this exact issue and it was driving me nuts.Test the app without admin rights. ![]() Just writing to confirm that these steps work! I had this exact issue and it was driving me nuts. Found the fix so to bypass the pesky UAC prompt. Originally posted by Easy_Gamer82:Oh, happy day. Just run the game and you'll notice the UAC prompt will no longer show up.ever. ![]() Once you do so, save the file and close the text editor. Type a name for the task that you want to create. In the Actions pane on the right, click Create Task. Search for the line with the name of the troublesome Runtime and delete that line. Launch Task Scheduler ( taskschd.msc) Right-click Task Scheduler Library category in the left, and choose New Folder. In that folder, you should see a small file named 'uplay_install.state' Open that file with a text editor - I recommend Notepad++. Once you determine the runtime that is causing the issue, go to that game's install directory. Right-click on Command Prompt and select Run as Administrator. With UAC, each application that requires the administrator access token must prompt the end user for consent. This article describes how UAC works and how it interacts with the end-users. You can check which Runtime program is causing the problem - after running and exiting the game - by scrolling to the bottom of the 'service_log.txt' file found in the 'logs' folder on your UPlay install location. Create an elevated shortcut to bypass UAC. UAC reduces the risk of malware by limiting the ability of malicious code to execute with administrator privileges. So, if you've started a game more than once but that Windows UAC prompt just keeps nagging you, it's because UPlay is trying to install a Support Runtime for that game and, failing miserably at it. Probably has a parallel to other game clients, like Steam, Origin and so on.I don't know. This only applies to UPlay-activated/bought games. ![]() Ubisoft should fix UPlay games' Install Scripts as this is an unnecessary nuisance. Therefore, the game's Install Script cannot complete itself. NET Framework 4 Client as this is already imbued with Windows 10. Unfortunately, this didn't work with Assassin's Creed - Black Flag. Uninstalled the versions I had, allowing UplayService to install the one included with the game. I managed to fix this for Anno 1404 - History Edition (it was failing to install an old VC C++ 2015 version). Effectively, the next time you start the game, it will jump straight into the game. In other words, the Install Script should run only once and, if the game starts - even if one or more of its dependencies had failed to install -, the Install Script should run no more for that game. My advice for Ubi is for the UPlayService.exe install script to be less rigid. Therefore, unless the UPlayService.exe successfully installs all the dependencies for a given game, it will always try to install the one(s) that failed. NET runtimes) every single time, should any of these fail to install. Figured what the problem is regarding the UAC prompts when starting an UPlay game:Īpparently, UPlay tries to brute force install a game's dependencies (DirectX, VC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |