Error: Windows cannot find "[...] EarTrumpet.exe'. Make sure you typed the name correctly, and then try again
rurot10 opened this issue · comments
This weekend July 28th my laptop did a windows update. And it went through the regular restarts and when all was done rebooting and loading the final time Windows 10 displayed the following.
Windows cannot find "C:\Program Files\WindowsApps\40459File-New-Project_2.0.4.0_x86__1sdd7...\EarTrumpet.exe'.
Make sure you typed.....
I uninstalled EarTrumpet cleaned the registry, rebooted and reinstalled the program. Before starting the program again, I rebooted and attempted to start the program with the same message displayed.
Please advise?
John
Hi @rurot10, what build/version of Windows 10 are you using? (Start > Run > winver)
Same thing is happening to me, but a slightly different error message. It seems to happen randomly though and only a Windows restart fixes it.
Windows version is version 1803 (OS build 17134.165).
This might be related to a recently fixed Windows bug. Can you try installing the following patch?
https://support.microsoft.com/en-us/help/4340917/windows-10-update-kb4340917
I was having the same issue as rurot10, even after re-installing KB4340917.
I found a workaround by editing the security settings and making myself the owner of the WindowsApps folder as described here, then launching EarTrumpet.exe manually from the folder:
C:\Program Files\WindowsApps\40459File-New-Project.EarTrumpet_2.0.5.0_x86__1sdd7yawvg6ne\EarTrumpet
Trying to launch it through the start menu throws an error saying "The parameter is incorrect."
Hey folks, sorry to make you jump through hoops here. Can you please do the following so we can gather more data?
- Open Feedback Hub
- Click Report a Problem and use the data below to populate the fields:
- Title: Issue 274 - Windows cannot find "[...]EarTrumpet.exe"
- Body: Anything you want, a nice haiku perhaps
- Category: Problem / Apps / EarTrumpet
- Submit
Thanks! We've engaged Microsoft on this issue so should have it solved soon.
Got the same issue after updating to RS5. I installed the app on RS4 from the store originally.
"+1" on feedback hub https://aka.ms/AA2qs1y
Edit:
winver: 1809 17763.1 x64 en-us
This happens to me when I took ownership of my WindowsApps folder. It broke several programs, and I tried to give permission back to TrustedInstaller but it just caused more problems. Based on my research the only way to resolve this is a complete reinstall of Windows.
Microsoft, I own my damn computer. Let me do what I want.
Still not fixed.
I am having this issue now.
I was having the same problem. Removed the app and now I can't reinstall it. The only message I get from Microsoft Store is "Couldn't Install. We'll try again later.".
Edit:
Updated Windows and it eventually got reinstalled automatically.
@riverar did you guys found solve for the problem its been 2 years and no one fixes it!
@Irwinori This is a low occurrence non-reproducible Windows bug, sorry. Are you on an older Windows 10 release by any chance? You'll likely have better success with newer releases of Windows 10.
@riverar am at the last version of windows 10 every app in the store work fine i try to repair it but nothing
pls help i love it and i need it
@Irwinori I just sent another email to Microsoft again. In the meantime, can you use Chocolatey? choco install eartrumpet
@riverar is it save to use because it will be my first time to use it
thank u for ur hard work to making our lives easier
@Irwinori It's safe, we maintain the package ourselves. For more information, see https://chocolatey.org/packages/eartrumpet.
@riverar I install it and its working in a good way, if u can update things up and fix it that's will be cool
i think the problem with the registry
Hi there. I'm cleaning up the issues list. There's no work to be completed here so am closing this issue for now. Feel free to keep the discussion going. Thanks!
Congratulations guys, it's been 5 fucking years and the problem hasn't been fixed. I have the same thing on windows 11, it is now there.
Why close the topic if the problem is not solved?
Congratulations guys, it's been 5 fucking years and the problem hasn't been fixed.
This is a free application made in their free time. Please show some respect and drop the entitlement. You are not owed anything.
Sorry for the headaches on this one. I closed it because there's nothing actionable on our side.
@DrusTheAxe Hey Howard, I keep getting beat up on this bug, pretty sure something is broken in appmodel or centennial and now got our first Windows 11 report. Any debugging tips here? Tracing?
This happens to me when I took ownership of my WindowsApps folder. It broke several programs
Yeah. That directory and children have various ACLs crafted on them (and often weirder and more complicated than you find elsewhere in Windows). Messing with that's usually destructive (depends on the tools and exactly what was done). We've hardened the ACLs over the years to make that sort of well-intentioned-malice harder to accomplish but devs are wily and creative...
I'm not sure if there's any easy 'fix' for that. It's akin to jogging thru the C:\Windows directory tree with a blowtorch, watching Windows wilt and cry in various ways then asking for a way to 'fix' it... I'm not overly optimistic but perhaps there's a trick I'm unaware of. Will see what I can dig up.
The scenario where a user tinkers in WindowsApps is invalid, wouldn't worry about that one. But we've had a significant number of folks just fail out of the blue and at one point I thought it was a Centennial bug...
@MiRorshik Did you mess with the WindowsApp folder at all?
folks just fail out of the blue and at one point I thought it was a Centennial bug...
Hard to say. Variety of reasons things could fail. One simple check you can do is look at the Microsoft-Windows-AppxDeploymentServer/Operational eventlog in the Event Viewer (Win-X, EventViewer or eventvwr.exe)
Deployment operations typically log "starting deployment operation" event, several events about actions during that (including errors if they occur) and an "completed deployment operation" event. When errors occur one or more of those events in the middle typically have a smoking gun pointing to the root cause (or at least a steaming slingshot hinting at it).
If everything was installed fine but something was busted and only noticed when activating the app it's a bit harder as activation doesn't persist events to the eventlog (the perf impact is undesirable given how often processes launch...). Activation does report ETW events, but they're more complicated to understand or root cause. If you use FeedbackHub with the right category and enable Tracing, repro the problem and end tracing it'll collect activation ETW events (and related) and reported to Microsoft.
my app store is completely screwed up no idea why, now ear trumpet wont run because of that
anyone know of a way to run it totally independent of microsofts bullshit? or an alternative software that does the same thing?