ActionUri OOP Server: What is it and why does it keep running in the background?

The ‘ActionUri OOP Server’ process sometimes shows up in Task Manager, using memory and CPU even if you’re not using Cortana. This process is a real part of Windows and helps Cortana handle certain types of commands called URI (Uniform Resource Identifier) commands.

It usually runs in the background because Cortana is turned on by default in many versions of Windows. Even if you turn off Cortana, you might still see this process for a short time because of leftover background services.

In this article, we will discuss different ways to close this process.

1. Disable Cortana via Local Group Policy Editor

You can disable Cortana using the Local Group Policy Editor. This will remove all Cortana-related processes, including ActionUri OOP Server. This is the best option for users who don’t use or want Cortana.

1. Hold the Windows key and press R.
2. Type gpedit.msc and press Enter.

3. Navigate to Computer Configuration > Administrative Templates > Windows Components > Search. If you’re unsure how to get there, follow these steps:
   1. Double-click Computer Configuration in the left panel.
   2. Double-click Administrative Templates.
   3. Double-click Windows Components.

4. Click Search in the left panel.
5. Double-click Allow Cortana in the right panel.

6. Select Disabled.
7. Click Apply and then OK.

8. Double-click Do not allow web search in the right panel.

9. Select Enabled.
10. Click Apply and then OK.

11. Double-click Don’t search the web or display web results in Search in the right panel.

12. Select Enabled.
13. Click Apply and then OK.

That’s it! Cortana should now be disabled on your system. Restart your computer to apply the changes.

Note: This method only disables Cortana, the digital assistant. The Cortana process (SearchUI.exe) used for Windows Search will still be visible in Task Manager, which is normal. However, the ActionUri OOP Server process should not run anymore, and other related processes should use minimal resources.

2. Disable Cortana via Registry Editor

You can also disable Cortana using the Registry Editor. The previous method works for certain editions of Windows, but if you don’t have access to the Local Group Policy Editor, use this approach.

1. Hold the Windows key and press R.
2. Type regedit and press Enter.

3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search. If you’re unsure how to get there, follow these steps:
   1. Double-click HKEY_LOCAL_MACHINE in the left panel.
   2. Double-click SOFTWARE.
   3. Double-click Policies.
   4. Double-click Microsoft.
   5. Double-click Windows.

4. Click Windows Search in the left panel. Note: If you don’t see Windows Search, you’ll need to create it:
   • Right-click Windows (in the left panel), select New > Key, and name it Windows Search.
   • Then right-click in the right panel, select New > DWORD (32-bit) Value, and name it AllowCortana.
5. Double-click AllowCortana in the right panel.

6. In the Value data box, type 0 and click OK.

Once you’re done, restart your computer and see if the problem is resolved.

Note: This turns off Cortana, but the Windows Search element (SearchUI.exe) is still present, which is normal. The ActionUri OOP Server process should no longer appear, and any other Cortana-related activity will use minimal resources.

3. Block ActionUri with Windows Firewall

Since the ActionUri OOP Server is started when Cortana sends and receives data over the internet, you can stop it from connecting by creating rules in Windows Firewall. This can help minimize its system usage. Note, however, that this will also stop Cortana from performing web searches.

1. Hold the Windows key and press R.
2. Type firewall.cpl and press Enter.

3. Click Advanced settings.

4. Click Inbound Rules in the left panel.
5. Select New Rule….

6. Select Program and click Next.

7. Choose This program path:
8. Enter: %SystemRoot%\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\ActionUriServer.exe. You can also click Browse and navigate to C Drive > Windows > SystemApps > Microsoft.Windows.Cortana_cw5n1h2txyewy > ActionUriServer.exe.
9. Click Next.

10. Select Block the connection and click Next.

11. Check all boxes (Domain, Private, and Public) and click Next.

12. Give the rule any name (for example, “Block ActionUri OOP Server”) and click Finish.

14. Now, click Outbound Rules in the left panel.
15. Repeat steps 5-13 to block outgoing connections for the ActionUri OOP Server.

When finished, you should see these block rules at the top of your Windows Firewall rule list.

Note: You can also follow these steps to block other applications (such as Reminders WinRT OOP Server). Just use the right program file (for example, ReminderServer.exe) in step 8 instead of ActionUriServer.exe.

4. Rename the Cortana Folder

Warning: This method might cause your Start menu or other features that depend on Cortana to stop working. Only proceed if you’re aware of and accept this risk.

If nothing else has worked, and you want Cortana and its related processes completely gone, you can rename or move the Cortana system folder. This disables Cortana and its search features.

Note: If you update Windows after doing this, the changes will likely be undone. If you want to keep Cortana disabled after a Windows update, repeat these steps.

Before making any changes, you need to take ownership of the Cortana folder. The following steps will help you quickly add a “Take Ownership” option to your right-click menu, making this process easier in the future. (You can remove this context menu entry later if you want.)

1. Hold Windows key and press R.
2. Type regedit and press Enter.

3. Double-click HKEY_CLASSES_ROOT from the left panel.
4. Double-click * entry from the left panel.
5. Double-click shell from the left panel.

6. Right-click shell and select New > Key. Name it runas.

7. Make sure runas is selected, then double-click (Default) in the right panel.
8. Type Take Ownership in the Value data field and click OK.

9. Right-click an empty space in the right panel, select New > String Value.
10. Name the new string NoWorkingDirectory.

11. Right-click runas, select New > Key, and name it command.
12. Double-click (Default) in the right panel for command.
13. Type cmd.exe /c takeown /f “%1” && icacls “%1” /grant administrators:F in Value data and click OK.
14. Right-click empty space in the right panel, select New > String Value, and name it IsolatedCommand.
15. Double-click IsolatedCommand, type cmd.exe /c takeown /f “%1” && icacls “%1” /grant administrators:F in Value data, and click OK.

16. Now repeat these steps for the Directory \ shell key:
    • Go to HKEY_CLASSES_ROOT \ Directory \ shell.
    • Add a key called runas if it doesn’t already exist.
    • Name the default value Take Ownership.
    • Add a NoWorkingDirectory string value.
    • Create a command key under runas, and in its default value type cmd.exe /c takeown /f “%1” /r /d y && icacls “%1” /grant administrators:F /t.
    • Add an IsolatedCommand string value and type cmd.exe /c takeown /f “%1” /r /d y && icacls “%1” /grant administrators:F /t.

Now you have a “Take Ownership” option in your context menu.

Next, rename the Cortana folder:

1. Hold the Windows key and press R.
2. Type C:\Windows and press Enter.

3. Create a backup folder by right-clicking in an empty space, selecting New > Folder, and naming it SystemApps.bak.
4. Open the SystemApps folder.
5. Right-click the Microsoft.Windows.Cortana_cw5n1h2txyewy folder and select Take Ownership.
6. Cut the Microsoft.Windows.Cortana_cw5n1h2txyewy folder (select the folder and press CTRL + X).
7. Go back to the Windows directory, open the SystemApps.bak folder you created, and paste the Cortana folder there (press CTRL + V).
8. If you see a permissions dialog, open Task Manager (hold CTRL + SHIFT + ESC), find SearchUI.exe, Cortana, and ActionUri OOP Server processes, and end them. Then complete the copy/move action.

The Cortana folder should now be moved to your backup folder, effectively disabling Cortana. If you ever want Cortana back, just copy or move the folder back to the original SystemApps directory.