Windows Store installed Ubuntu fails to launch - cannot access specified device, path, or file.

[rkeithhill]

• Your Windows build number: 10.0.16237.1001

• What you're doing and what's happening
  I downloaded the Ubuntu dist from the Windows Store. When I run it I get the error "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

• What's wrong / what should be happening instead:
  I expect the Bash shell to start up.

When I try to access the path above, indeed I do not have pemissions to even see the contents of the folder C:\Program Files\WindowsApps. I also have the original Ubuntu WSL installed on this machine (14.04) and it works just fine.

[sunilmut]

• @bitcrazed @zadjii-msft

[sunilmut]

@rkeithhill - Thanks for your post. When you say When I run it, can you describe how exactly you are running the app?

[rkeithhill]

I click on the "recently installed" Ubuntu icon in the Start | All Apps menu.

[benhillis]

@rkeithhill - I have not seen this previously. Did launching the tile over work or did you hit this the first time ever launching?

[rkeithhill]

It never worked.

[zadjii-msft]

@rkeithhill hmm. This is indeed something I've never seen before. It's definitely right that you shouldn't be able to access C:\Program Files\WindowsApps - that's where Windows stores the data for your apps from the Store.

Does calling ubuntu from the commandline work?

Does running the ubuntu.exe in %localappdata%\Microsoft\WindowsApps work?

[rkeithhill]

No, running Ubuntu from PowerShell gives this error:

The error details are:

PSMessageDetails      :
Exception             : System.Management.Automation.ApplicationFailedException: Program 'ubuntu.exe' failed to run:
                        Access is deniedAt line:1 char:1
                        + ubuntu
                        + ~~~~~~. ---> System.ComponentModel.Win32Exception: Access is denied
                           at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
                           at System.Management.Automation.NativeCommandProcessor.Complete()
                           --- End of inner exception stack trace ---
                           at System.Management.Automation.NativeCommandProcessor.Complete()
                           at System.Management.Automation.CommandProcessorBase.DoComplete()
                           at
                        System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase
                        commandRequestingUpstreamCommandsToStop)
                           at
                        System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
                        input)
                        --- End of stack trace from previous location where exception was thrown ---
                           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                           at
                        System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
                        input)
                           at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean
                        ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts,
                        CommandRedirection[][] commandRedirections, FunctionContext funcContext)
                           at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame
                        frame)
                           at
                        System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
                        frame)
TargetObject          :
CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
FullyQualifiedErrorId : NativeCommandFailed
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}

MyCommand             :
BoundParameters       : {}
UnboundArguments      : {}
ScriptLineNumber      : 1
OffsetInLine          : 1
HistoryId             : -1
ScriptName            :
Line                  : ubuntu
PositionMessage       : At line:1 char:1
                        + ubuntu
                        + ~~~~~~
PSScriptRoot          :
PSCommandPath         :
InvocationName        :
PipelineLength        : 0
PipelinePosition      : 0
ExpectingInput        : False
CommandOrigin         : Internal
DisplayScriptPosition :

Exception at nesting level 0 ---------------------------------------------------

ErrorRecord                 : Program 'ubuntu.exe' failed to run: Access is deniedAt line:1 char:1
                              + ubuntu
                              + ~~~~~~.
WasThrownFromThrowStatement : False
Message                     : Program 'ubuntu.exe' failed to run: Access is deniedAt line:1 char:1
                              + ubuntu
                              + ~~~~~~.
Data                        : {System.Management.Automation.Interpreter.InterpretedFrameInfo}
InnerException              : System.ComponentModel.Win32Exception (0x80004005): Access is denied
                                 at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
                                 at System.Management.Automation.NativeCommandProcessor.Complete()
TargetSite                  : Void Complete()
StackTrace                  :    at System.Management.Automation.NativeCommandProcessor.Complete()
                                 at System.Management.Automation.CommandProcessorBase.DoComplete()
                                 at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProce
                              ssorBase commandRequestingUpstreamCommandsToStop)
                                 at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate
                              (Object input)
                              --- End of stack trace from previous location where exception was thrown ---
                                 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                                 at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate
                              (Object input)
                                 at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean
                              ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[]
                              pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
                                 at
                              System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame
                              frame)
                                 at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(Interp
                              retedFrame frame)
HelpLink                    :
Source                      : System.Management.Automation
HResult                     : -2146233087

Exception at nesting level 1 ---------------------------------------------------

NativeErrorCode : 5
ErrorCode       : -2147467259
Message         : Access is denied
Data            : {}
InnerException  :
TargetSite      : Boolean StartWithShellExecuteEx(System.Diagnostics.ProcessStartInfo)
StackTrace      :    at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
                     at System.Management.Automation.NativeCommandProcessor.Complete()
HelpLink        :
Source          : System
HResult         : -2147467259

[nekym]

I also had the same error. (wsl2, win 10)
How I fixed it:
Start -> in search wrote ubuntu and found installed ubuntu -> right click -> app settings -> Repair

[chris-mcguire]

The fix mentioned here helped correct my issues. Thank you!

Here's the errors I had (wsl2 windows 11):

When attempting to run ubuntu.exe directly from a powershell or CMD:

Program 'ubuntu.exe' failed to run: The system cannot find the file specifiedAt line:1 char:1
+ .\ubuntu.exe
+ ~~~~~~~~~~~~.
At line:1 char:1
+ .\ubuntu.exe
+ ~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

When attempting to launch a tab in Windows Terminal for "Ubuntu":
[error 2147942402 (0x80070002) when launching 'ubuntu.exe']

More context:

After having virtualization enabled for much time and using wsl2, I had a string of critically failed windows shutdowns (due to random freezing at idle). While attempting to troubleshoot issues regarding the random freezing at idle times, I did a BIOS firmware update which reverted my virtualization setting. I mistakenly allowed my windows installation to boot up without virtualization enabled. Something related to the WSL2 Ubuntu (Windows App Managed) became corrupted during this process of troubleshooting. It might have been the attempt to boot without virtualization enabled or it might have been something slightly earlier than that related to failed windows shutdowns.

[zadjii-msft]

I know this sounds ridiculous, but does uninstalling and re-installing change anything?

[rkeithhill]

Not ridiculous at all. But alas, I've tried that. No joy. Fails the same way.

[rkeithhill]

OK, this app isn't the only one misbehaving on my insider's build.

Most store apps seems to be working fine: the built-in apps, Tweetium. But these two at least are having problems. So this is likely not a WSL issue but an Appx issue of some sort. And it's not like we haven't had Appx issues for the past 5 years. Welcome to the Windows Store. :-)

[onomatopellan]

Hi. Did you try running this? http://aka.ms/diag_apps10

[rkeithhill]

That worked. Thanks! It said that the location of my Temporary Files had changed and that that could cause problems with Windows Store apps. Not sure how that got changed but fixing it, fixes the Ubuntu store app.

[gregersn]

I get this exact same error dialog as in the first post here now. And I have tried tons of stuff. It works with other users. But running the troubleshooting app does not seem to do anything.
This is driving me nuts.

I am running Version 1709 (OS Build 16299.15)

[rotech]

I am seeing this too. The AppsDiagnostic solution did not work for me. It's the same with both Suse Leap and Ubuntu from the Store.

[rotech]

I have solved the issue for me. I noticed that unbuntu.exe in the path
C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\ was 0kb and had no icon.

I copied everything from:
C:\Program Files\WindowsApps\CanonicalGroupLimited.UbuntuonWindows_1604.2017.922.0_x64__79rhkp1fndgsc
Into:
C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc

Ran unbuntu.exe from inside the Canonical... folder in the user AppData dir, and everything installed perfectly.

[nikitakuma]

thank you sm this was giving me the biggest headache and this was all that finally opened it.

[lcpunch]

You are a life saver, thanks!

[zigafide]

worked for me lets gooo

[Arndeverafter]

The gift that keeps on giving 5 years later, thank you so much!

[Noa33881]

you are saved my life

[0m3rta13]

Currently having the same issue but on kali-Linux not Ubuntu.

Windows 10: Nov 2019 1909 build
WSL version 1.

I have tried all the steps above with no luck.
This comes shortly after a fresh install and update.

It was working just fine. I ran some updates (apt-get ones). All was one.
Installed a minimal python environment. All was fine.
Cloned a single git repo and created a virtual environment inside of it. All was fine.
I restarted wsl after each of these actions and rebooted my machine after the last one. All was fine.

Then I was looking at WSL 2 and checking if it was available for my build. Before I saw that it wasn’t, while checking my current WSL version within Powershell (wsl -l -v etc etc, though -v isn’t recognised) I then ran wsl —upgrade from Powershell. I had my WSL terminal open and logged in as root. Powershell was also running with escalated privileges.

After closing wsl now whenever I try and reopen it I get the same access error pop up as per the ones people have posted above telling me I cannot access the WindowsApp folder within Program Files.

So far I have taken ownership of that folder.
Reset Kali within the Apps Menu.
Reset Microsoft store in the App Menu.
Uninstalled And reinstalled Kali.
Run the Kali.exe located within my user profile instead of the WindowsApp Folder.

All of these result in the exact same pop up error.
I am the only User on my machine. It is a personal machine not on a wider network just straight connection to WiFi and a VPN.

Some Added Info:

I can access Kali from Powershell by entering the wsl command or Cmd. Both when escalated. So I suspect the issue comes in from my running the —upgrade command earlier.
Also, I had not logged into my Microsoft account at any point yet not even during or after the fresh install. Was running on a plain local account with admin privs. I logged into my Insiders Preview MS account after all this happened as I decided to try and see if installing a preview build may fix my woes, after some obviously foolish steps on my part.

Barring that I will opt for a fresh install. Again. Hoping to not have to go there.

If anyone has any suggestions that would be great.
Otherwise I hope this info and my steps up till now can help to shed some light in any way.

[craigloewen-msft]

@0m3rta13 does your Windows build have access to wsl --import and wsl --export commands (these were released in Windows builds 18362 or higher)? In the meantime for a work around are you able to export your distro, and import it again inside of a different install location?

Are you on a corporate machine with Group policy? Since other users mentioned they were affected by that as well.

[0m3rta13]

@craigloewen-msft I didn’t have the import Parmams. The build wasn’t an insider build (Nov 2019 release build 1909 iirc). I also wasn’t able to export or move anything within the ..Program Files\WindowsApp\ Folder. Even after taking ownership I couldn’t access everything in there. What was weird was I noticed new “Users” in the security tab that changed everytime I changed the ownsership an permissions to my account. The “usernames” were really long random strings that looked similar to registry entries. No idea what that was about.

The machine is not in any work/corporate network/doamain at all. It was a 2 hour old fresh fresh install simply connected on my regular home WiFi. No special configs or even proxy. Just my VPN which runs through the HMA VPN app (again, as basic a setup as they come)

I wasn’t even logged into a Microsoft account. The lone user was a regular local/admin account.
Once this happened I logged into my MS account and downloaded the insider release which had no effect.

I just finished resetting the my install, opting to keep my files and wipe out windows. Everything was fine thereafter.
Well sort’ve. I’ve hit a new problem with WSL 2 crashing on startup but that’s a known issue seemingly related to winsocks and I’m tracking it on another issue here on Github and will submit log there if needed.

I think I did save my events and some logs from before the reset. Not sure if any of it will be useful. Here. The main standouts therein are the ACCESS DENIED errors for everything from Search to Svchost to random network dll files that all could not access the ..Program Files\WindowsApp folder. (Or rather the Kali folders inside that).

Again the action that seems to have triggered it was me running wsl —upgrade inside and elevated Powershell. WSL was open in its default bash shell and logged into the root User when I did it.
All worked fine and then I ran that command, closed everything, rebooted and that’s when the issue started.
I was only able to access WSL by opening an elevated Powershell and running the WSL command.

Sorry. A lot to read. Trying to be as detailed as possible.

[0m3rta13]

@craigloewen-msft for what its worth just thought I'd post here that the given solution #4177 does not work Same error and issues as I've had here. Not sure if i should open a new issue here or one on the main repo so just posting here because i did before.

Easiest Repro of issue from my testing/playing:

• Fresh insider build 19551.1005
• Enable wsl, hyper v, virtualization etc
• Reboot
• install proxifier
• reboot
• install debian or kali linux in store (trying both to se if updating prior to enabling wsl 2 has an effect)
• open and update kali (not debian)
• open debian so initial run can complete
• close everything
• open proxifier and leave it with basic configuration enabled for random exe not related to wsl or system (vlc for example)
• open kali and debian to see if still working (yes)
• close everything (kali, debian, proxifier)
• open powershell and change debian to wsl 2 and wait for it to finish
• close powershell and open debian to see if working (yes)
• close debian
• open proxifier which greets me with a winsocks "error" offering automatic configuration correction (see attached pic)
  
• say yes and confirm 2 uac prompts
• whether i reboot or not when prompted after its done makes no difference
• test proxifier (working)
• close proxifier completely and open debian which opens and closes imediately. running it from any command line gives the error "The attempted operation is not supported for the type of object referenced"
• test kali (works)
• change debian back to wsl 1 (works again)

Hope that helps at all. If i should open a new issue or whatver elsewhere I shall. If any particular logs are needed I will suply whatever i can.

[craigloewen-msft]

Thank you @0m3rta13 for the detailed write up! The repro steps are particularly helpful. We're taking a look at this with the networking team and we'll post any updates here as we get them.

[0m3rta13]

No problem @craigloewen-msft
If you want/need any particular logs or info let me know what and I'll get it to you.

And Thanks to you and the team for your work!
Seems like alot is going on. Exciting times

[bitcrazed]

@JovannyElias Please DO NOT modify the permissions of files under the C:\Program Files\WindowsApps protected folder. Doing so could completely prevent the launching of WSL distros, and could, in some cases, cause many modern apps to fail to launch at all!

As with our prior and still current guidance not to spelunk though the WSL1 filesystem, There are very good reasons why folders like these are hidden and secured more strongly than older pre-UWP app folders - they're where we store your modern apps, and how we protect your apps and the OS itself from corruption and damage.

If anyone who reads this chooses to ignore this guidance, don't come crying to us when your machine becomes useless. 😉

[rollsch]

I've broken a windows install before by messing with those permissions. Agree to not touch them!

[JovannyElias]

@JovannyElias Please DO NOT modify the permissions of files under the C:\Program Files\WindowsApps protected folder. Doing so could completely prevent the launching of WSL distros, and could, in some cases, cause many modern apps to fail to launch at all!

As with our prior and still current guidance not to spelunk though the WSL1 filesystem, There are very good reasons why folders like these are hidden and secured more strongly than older pre-UWP app folders - they're where we store your modern apps, and how we protect your apps and the OS itself from corruption and damage.

If anyone who reads this chooses to ignore this guidance, don't come crying to us when your machine becomes useless. 😉

I deleted post. Don’t want to f up someone’s system. I tried many other ways on many sites to fix my issue but this was the only work around for me. So far everything is ok with system. Now I know not to do that again.

[bitcrazed]

Great, thanks. Appreciate you reaching out to help another community member, but it's important we all remember that if the OS is making something hard to find, that's usually by design and it's likely thinking twice before leaping 😜

[0m3rta13]

Would like to just reiterate what was said re modifying WindowsApps folder permissions. I did the same think and while it was no problem initially, it wasn’t long before I started getting the most random, out of place errors (not even related to WSL). I ended up having to do a clean refresh of windows to fix it.

Still keeping an eye on the hopeful progress here. For now though I’ve had to move back to Linux as my primary OS. Holding thumbs this issue can get sorted out.

Thanks to all who are contributing and working towards a solution!

[TerrorFactor]

Same issue here.

• Installed a fresh 1909 pro (iso from microsoft site)
• downloaded the ubuntu and kali appx packages (no direct internet access on this machine)
• used the add-appxpackage command to install the package (with the initial admin user, but without elevated rights), no errors
• tried to run ubuntu, using the shortcut in the start menu.

Same issue with Kali. Changes to my clean Windows before installing the packages:

• add features wsl, openssh server, openssh client
• enable remote desktop
• configure proxy settings

The server install method mentioned (#3612 (comment)) does work however.

[YouveGotMeowxy]

Anyone ever find a real solution for this? I can run default MS store apps, but all others give me permissions error. Since I read the warning not to manually change any permissions, I'll heed that advice, but, other than that there has been NO advice on how to truly solve this? And I can't find anything in google searches either.

[0m3rta13]

Not sure if it’ll help but the way I solved this was by doing the whole repair/reset of the windows store, removing ubuntu and every mention of a canonical folder I could find.
After that I got winget up and running and installed Ubuntu with winget in Powershell.

I also downloaded the Ubuntu package first to avoid having to download it over and over if I had an issue but winget worked the first time and all has been well since

[Andoryuuta]

For me, this was related to the IE cache folder (likely because of a windows 7 to windows 10 upgrade).

I would suggest downloading process monitor and setting up a filter for "ACCESS DENIED" errors, as seen on this post.

You should be able to find the exact file or folder it's having issues with.

[wxdx110]

我也遇到了这个问题，不过我已经修复了。该问题和.NET版本有关，你可以卸载.net更新，然后重新开启.NET功能来解决该问题。

I also encountered this problem, but I have fixed it. The problem is related to the .NET version. You can uninstall the .net update and then re-enable the .NET Framework to solve the problem.

[neolution]

What do you mean exactly?

[Funkyyyyyyyyyyyy]

After realising this issue was due to changes to the WindowsApps folder's default permissions (might have been inadvertently caused by me - I'm not sure), I ended up accidentally fixing the issue via the following steps:

1. Create a system restore point.
2. Changed where new apps are saved to via:
   Settings > System > Storage > Change where new content is saved > New apps will save to:
   I my case I changed from my C: drive to my D: drive, this created a new WindowsApps folder on my D: drive's root directory with (what I assume were) default permissions for the folder.
3. Copied folder permissions from D:\WindowsApps to C:\Program Files\WindowsApps using an elevated PowerShell prompt via the following command:
   (Get-Item 'D:\WindowsApps').GetAccessControl("Access") | Set-Acl -Path 'C:\Program Files\WindowsApps'
   This then basically broke the Windows store (wouldn't open) and some of other Windows Store apps I had installed.
4. Attempted at fixing Windows Store using the Windows Store troubleshooter, and running WSReset.exe via an elevated Command prompt.
5. Step 4 didn't seem to help so I then took ownership of C:\Program Files\WindowsApps (I used this due to its ease of use).
6. Step 5 didn't seem to help either so I repeated Step 4 (also didn't seem to help).
7. After finally giving up on trying to fix the issue, I decided to use System Restore to try to get back my Windows Store and other apps that were working previously. After system restore was complete, I tried reinstalling my chosen Linux distro (Ubuntu) and found to my surprise that it now worked.

I apologise for the somewhat convoluted steps but I thought I'd post this here in case anyone else suffering from the same issues wants to try using these steps to fix them.