Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Windows cannot access the specified device, path or file" even running in regular user #6824

Closed
ghost opened this issue Jul 8, 2020 · 9 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.

Comments

@ghost
Copy link

ghost commented Jul 8, 2020

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows [Version 10.0.18363.900]
Windows Terminal version (if applicable):
Microsoft.WindowsTerminal_1.0.1811.0_8wekyb3d8bbwe.msixbundle

Any other software?

This is a work computer inside an Active Directory domain, if that's relevant at all. I am administrator on my local machine though.

Steps to reproduce

Install Windows Terminal from the Microsoft Store.
Launch the app as regular user in Start Menu.

Expected behavior

The application starts.

Actual behavior

The application immediately throws an error: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

Extra notes

This is NOT a duplicate of #1538, as that one is about running in administrator, but mine can't even start in regular user. I can't use it at all.
The problem is the same if I use the file downloaded from GitHub Release or install from Microsoft Store.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 8, 2020
@WSLUser
Copy link
Contributor

WSLUser commented Jul 8, 2020

This is still a dupe but forget which issue number it is. Basically this is a known issue but very little to go on for troubleshooting. If you manage to find something in Event Viewer to help that would be great.

@WSLUser
Copy link
Contributor

WSLUser commented Jul 8, 2020

Note that Feedback Hub might be able to gather the necessary info but of course you typically can't use it in a work environment with AD.

@alice-n-bob
Copy link

alice-n-bob commented Jul 10, 2020

I have the same problem. Tried icacls to repair permission, 0 fail, but still cannot launch it.

Actually it may be a Microsoft Store problem. Several other recently installed apps have the same problem.

Skype launch fail and gave this error message in Event Viewer:

Failed to launch the app from PDP 9WZDNCRFJ364 : Skype
Error Code: Unknown HResult Error code: 0x80000000
Function: LaunchDefaultPackageAsync
Source: C:\BA\139\s\src\App\Helpers\PackageStatusHelper.cs (487)

ProductActionApis: Completed action 'LaunchDefault' with parameters '9WZDNCRFJ364,', Result: RanToCompletion
Function: StartAndLogOperation
Source: C:\BA\139\s\src\Tasks\WinStoreTasks\WebApis\ProductActionApis.cs (306)

@zadjii-msft
Copy link
Member

Huh. That's certainly a pretty useless error message, isn't it 😄

Out of curiosity, can you launch the Terminal as you admin account? Maybe that'll help shed some light on the problem.

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Jul 16, 2020
@alice-n-bob
Copy link

File permission issue, see here: https://answers.microsoft.com/en-us/windows/forum/all/solved-some-apps-from-microsoft-store-has/887aef4c-e912-474f-8ba2-bdd2a29d0631

@zadjii-msft
Copy link
Member

@szliu-a Does the above link help with your problem?

@ghost
Copy link
Author

ghost commented Jul 17, 2020

@zadjii-msft It's the same error if I try to run in admin account. I will try the above link.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 17, 2020
@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Aug 4, 2020
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 8, 2020
@ghost
Copy link

ghost commented Aug 8, 2020

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Aug 11, 2020
@mu88
Copy link

mu88 commented Jan 15, 2024

@zadjii-msft I'm encountering the same problem after installing Windows Terminal v1.18.3181 via Chocolatey on my fresh Win10 laptop (Version 22H2, OS build 19045.3803). I already tried fixing the permissions as described here, but unfortunately, that didn't solve the issue. As a temporary workaround, I'm using the portable version, but I'd really appreciate further help to solve this issue properly 🙏🏻

@microsoft-github-policy-service microsoft-github-policy-service bot removed the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Jan 15, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

4 participants