Terminal: File system error (12007)
I installed terminal with choco and I can't run it. I installed from msixbundle and I'm getting the same error.
Windows 10 1903 (18362.239)
bugproof
All 12 comments
Do you have a Windows Error Reporting bucket ID we could investigate?
Could you try deleting your profiles.json file, and re-starting the terminal, to see if that fixes it? The settings roam across PC's, so it's possible valid setting on another machine is invalid on this one. (make sure to back the profiles.json file up first, just in case).
zadjii-msft
on 29 Jul 2019
I don't have any bucket ID. There's no crash, just a message box with this error.
I don't have profiles.json file
bugproof
on 29 Jul 2019
Do you even have a screenshot of this filesystem error? This is not very much to go on.
DHowett-MSFT
on 29 Jul 2019
It's not in English but that can be translated to "File system error"
bugproof
on 29 Jul 2019
This looks like the same thing as #1538.
DHowett-MSFT
on 29 Jul 2019
I wouldn't say it's the same. I can't use the terminal doesn't matter if I run it as administrator or not. Also, the error from the issue you linked doesn't show the same error. It's funny because other UWP apps work fine.
I have the same error on 2 computers
bugproof
on 30 Jul 2019
It was an issue with a firewall and etc/hosts. It works fine now
bugproof
on 30 Jul 2019
It was an issue with a firewall and etc/hosts. It works fine now
Could you comment a little more on that? I'm having the same issue. I think I have the same problem as you.
conradolandia
on 8 Aug 2019
Yeah, I too am very interested in how those things are related.
DHowett-MSFT
on 8 Aug 2019
@conradolandia In the past, I used a tool Destroy Windows 10 Spying and it was blocking a bunch of Microsoft's addresses (Windows store app too) in the C:\Windows\System32\drivers\etc\hosts file and in the firewall. I removed those addresses from hosts and temporarily disabled the firewall and re-installed the terminal and it worked. I am suspecting it just couldn't download some default configuration or something like that which was hosted on the blocked IP and/or domain.
bugproof
on 8 Aug 2019
I know this has been closed for a while but I just ran into this issue and it wasn't immediately clear how to workaround it.
Just empty your C:\Windows\System32\drivers\etc\hosts file, open Windows Terminal once, and then put the hosts file back to normal. Since doing this, the terminal has worked correctly.
Both bugs related to this are marked as closed but this unhelpful error message is still present in the latest build. Even if this problem is caused by people blocking microsoft ip addresses it would be nice if it could fail more gracefully/helpfully.
JamesSeaward
on 17 Mar 2020
I had a same issue too. I've installed Terminal on a corporate notebook but I've tried to log in my private Live account unsuccessfully earlier. Sometimes, I've got a notification message to repair that, but it was unsuccessful. After I removed this account, it works.
shark300
on 25 May 2020
Related issues
geeksfn
路
3Comments
warpdesign
路
3Comments
mrmlnc
路
3Comments
TayYuanGeng
路
3Comments
carlos-zamora
路
3Comments
Most helpful comment
@conradolandia In the past, I used a tool Destroy Windows 10 Spying and it was blocking a bunch of Microsoft's addresses (Windows store app too) in the
C:\Windows\System32\drivers\etc\hostsfile and in the firewall. I removed those addresses from hosts and temporarily disabled the firewall and re-installed the terminal and it worked. I am suspecting it just couldn't download some default configuration or something like that which was hosted on the blocked IP and/or domain.