MSEdgeRedirect
MSEdgeRedirect copied to clipboard
Starting DevToys is blocked
Preflight Checklist
- [X] Running
microsoft-edge:https://google.comredirects successfully - [X] Microsoft Edge is selected in any "How do you want to open this?" box
Install Type
Manual Update
Install Mode
Service Mode
Steps to reproduce
Note: MSEdgeRedirect has been installed via Scoop, but I chose manual update, because Scoop essentially just installs the installer, which then has to be executed separately. I'm not an admin and can't readily test what would happen if I were.
- Log in with a non-admin account.
- Install Scoop.
- Enable the
extrasandnonportablebuckets. - Execute
scoop install msedgeredirectto grab the installer. - Execute
$Env:userprofile\scoop\apps\msedgeredirect\current\MSEdgeRedirect.exeto properly install MSEdgeRedirect. Choose the service mode install (nothing else should work either, unless you're an admin). - Start MSEdgeRedirect and verify that it is is running.
- Execute
scoop install devtoys-npto install DevToys. - Execute command
start devtoys:(note the colon). Observe the following error message:
start : This command cannot be run due to the error: The app didn't start.
At line:1 char:1
+ start devtoys:
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException
+ FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
- Exit MSEdgeRedirect.
- Execute the command
start devtoys:again. Observe that it starts now.
Reproducibility tested with MSEdgeRedirect starrting from at least v0.7.4 up to v0.7.5.1.
✔️ Expected Behavior
MSEdgeRedirect should not interfere with using DevToys (or with any other application except the MS Edge itself).
❌ Actual Behavior
DevToys won't start at all if MSEdgeRedirect is running, neither from a PowerShell prompt (reports an InvalidOperationException) nor via Start Menu (it silently fails).
Microsoft Windows version
Windows 11 22H2 Build 22621.2283
Other Software
I'll look into this thank you
Looks like this is probably because the application is being launched by SiHost and I have SIHost being a bit aggressive in Service Mode due to essentially having such a small timeframe. #287 is also a byproduct of this. I'll look into revamping this.
Should be fixed in the latest test build. Sorry about the delay