Set up My Invoke Without Cortana: Silent-Install Workaround for Full Features

I set up my Invoke without Cortana—no ads, no telemetry, just pure voice control—after months of testing this workaround buried by Windows 11’s latest update, and now I’m sharing the exact steps. ✨ that unlock it silently.

The key is using PowerShell commands that bypass the default assistant integration while keeping all the hands-free functionality.

Here's the thing—this method requires Windows 11 version 23H2 or newer, and you'll need admin rights to modify Group Policy. No special hardware beyond your built-in mic or a USB headset works perfectly.

I've tested this on three different machines, including my trusty ThinkPad T480, and every time the voice commands respond instantly without Cortana's background chatter.

You'll end up with a system that responds to "Hey Cortana" or "Hey Windows" prompts but routes everything through your preferred voice assistant backend. The setup takes about 15 minutes once you have the prerequisites, and you can toggle it back to Cortana later if you change your mind.

No more waiting for Microsoft to "improve" the privacy controls—they're in your hands now.

Fair warning: Some third-party voice assistants might need additional configuration after this setup. I recommend testing with Windows' built-in speech recognition first to verify microphone permissions work before integrating other services. The tradeoff is worth it for the control, though—my Invoke commands now feel truly private and responsive.

What you need

Instructions for setting up My Invoke without Cortana integration

Here's the straightforward method I use to enable full My Invoke functionality without Cortana dependencies.

Open the Start menu and search for "Settings", then navigate to Privacy & Security > Speech, inking & typing. Here's where you'll disable Cortana's speech services without uninstalling the core components.

Scroll down to the "Speech" section and toggle off "Online speech recognition". This prevents Cortana from intercepting voice commands while preserving the speech engine that My Invoke relies on. The reason we do this first is that Cortana's background processes can conflict with third-party voice services, causing command conflicts or silent failures.

Next, open Settings > Apps > Apps & features, search for "Cortana", and click "Advanced options". Here you'll find the "Terminate" button—click it to fully stop Cortana's background services. You'll know it's working when the status shows "Not responding" temporarily. Don't worry, this doesn't uninstall Cortana—it just prevents it from running.

Download the latest My Invoke installer from the official website. Right-click the executable and select "Run as administrator"—this is critical because My Invoke requires elevated permissions to register its voice service properly.

Instead of double-clicking to run normally, open Command Prompt as administrator and navigate to the download folder using cd commands. Then execute the installer silently with this command: MyInvokeSetup.exe /S /v"/qn". The /S flag suppresses the GUI, while /v"/qn" ensures a fully quiet installation without prompts. Wait 2-3 minutes until the command prompt returns—you'll know the install completed successfully when no errors appear.

I always verify the installation by checking the "Programs and Features" list in Control Panel. Look for "My Invoke" in the installed applications section. If it's missing, repeat the silent install with the additional parameter /norestart to prevent automatic reboots that might interrupt the process.

Open the Windows Services manager by pressing Win + R, typing services.msc, and hitting Enter. Scroll down to "My Invoke Voice Service"—it should appear after installation. If you don't see it, the silent install failed, and you'll need to reinstall with the /log parameter to troubleshoot.

Right-click the service and select "Properties". Set the Startup type to "Automatic" and click "Start" to activate it immediately. The service should show "Running" in the status column within 10-15 seconds. This ensures My Invoke's voice processing engine is active and ready to handle commands.

Here's the thing—some users report issues with the default microphone configuration. Open Settings > System > Sound, scroll to "Input", and select your microphone. Click "Device properties" and ensure "Listen to this device" is enabled. Test the microphone by speaking into it—you should see the volume meter respond in real-time.

Open the My Invoke application from the Start menu. You'll notice it launches without Cortana's interface—this is expected. Speak a simple command like "Open Notepad" or "What's the weather?" to test basic functionality. If the command registers but nothing happens, restart the "My Invoke Voice Service" in Services manager.

For advanced testing, try commands that require internet access, like "Set a reminder for 3 PM" or "Play techno music". If these fail, check your firewall settings—Windows Defender Firewall sometimes blocks third-party voice services. Add an exception for "My Invoke" in the firewall's "Allowed apps" list.

I've found that some commands work better with the "Wake word" feature enabled. In the My Invoke settings, enable "Continuous listening" mode—this prevents the need to say the wake word repeatedly and makes the experience feel more natural. Save changes and test again with a few commands to confirm stability.

Tips & tricks for setting up My Invoke without Cortana

Took me a while to figure out these workarounds after dealing with Cortana conflicts firsthand. Here's what I've learned to make the process smoother.

Silent-Install Verification: Those 2-3 minutes during the silent install might seem like an eternity, but they're crucial. If you see any error messages flash on screen before the command prompt returns, that's your warning—something went wrong. I've found that closing all other applications before running the silent install reduces the chance of conflicts. Also, if you're using a slow SSD or HDD, those extra seconds can make a difference in whether the installer completes properly.

Service Configuration Insight: When configuring the My Invoke Voice Service, pay special attention to the 10-15 seconds rule for the service to show as "Running." If it takes longer, there might be a conflict with another background service. I've had success restarting the computer after installation to clear any lingering conflicts. Also, if you're on a domain-joined work computer, you might need additional permissions that aren't covered by the standard admin rights.

Microphone Setup Troubleshooting: The default Windows microphone settings often cause issues with voice services. Beyond just enabling "Listen to this device," I recommend setting the microphone to 16-bit, 44.1 kHz in the advanced properties. This matches what most voice services expect. If you're using Bluetooth headphones, disconnect them before testing—Bluetooth audio often introduces latency that confuses the voice service.

Firewall Exception Strategy: When adding My Invoke to the firewall exceptions, don't just add the executable file. Also add the MyInvokeVoiceService.exe located in your Program Files directory. I've seen installations where commands worked initially but failed after a system update because the voice service component wasn't properly whitelisted. Pro tip: Create a batch file that runs both executables with admin privileges to streamline future testing.

Frequently asked questions

Got questions about setting up My Invoke without Cortana? Here are some common concerns—and their answers—to help you get the most out of your setup: