search

microsoft / terminal

The new Windows Terminal and the original Windows console host, all in the same place!
MIT License
95.24k stars 8.27k forks source link

File system error (12007) #2129

Closed bugproof closed 5 years ago

bugproof commented 5 years ago

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)

https://github.com/microsoft/terminal/issues/2022

zadjii-msft commented 5 years ago

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).

bugproof commented 5 years ago

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

DHowett-MSFT commented 5 years ago

Do you even have a screenshot of this filesystem error? This is not very much to go on.

bugproof commented 5 years ago

It's not in English but that can be translated to "File system error"

image

DHowett-MSFT commented 5 years ago

This looks like the same thing as #1538.

bugproof commented 5 years ago

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 commented 5 years ago

It was an issue with a firewall and etc/hosts. It works fine now

conradolandia commented 5 years ago

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.

DHowett-MSFT commented 5 years ago

Yeah, I too am very interested in how those things are related.

bugproof commented 5 years ago

@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.

JamesSeaward commented 4 years ago

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.

shark300 commented 4 years ago

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.

zszen commented 2 years ago

I have the same problem. Because I install it with offline network. It's ok.

zhro commented 2 years ago

I just did a clean format and reinstall of Windows 10 and got this error after installing the Minecraft launcher. I can't log in either, with it reporting some "Deep Ocean" error.

after-installation

launcher

DHowett commented 2 years ago

This is very interesting! Your Minecraft issue probably has the same root cause as the Terminal issue you're commenting on, but we haven't been able to solve either of them. Huh.

sylveon commented 1 year ago

This is happening to users of my app that try to install the app on their debloated system. They're forced to downgrade to a 4 years old version :(

I'm trying to be a good citizen of the platform and adopt appinstaller, but it's hard when you get these kinds of strange reports every other week... Not to mention some of them removed the app installer app so they have to use powershell to even be able to install the app, ugh.

zadjii-msft commented 1 year ago

try to install the app on their debloated system

perhaps, some of that stuff they removed as "bloat" was actually important. Crazy idea, I know 🤔 /s

In all seriousness, I don't think any of us on the Terminal team can really help with this. Maybe you'd have more luck getting traction over on the WASDK repo. Not sure where the internal bug report went, or what the status of that is ATM - I'm sure I could find it if I looked hard enough.

I appreciate the effort in being a good citizen - it's something we deal with every day here on the Terminal, and we do try our best to make sure the papercuts we experience are escalated as we see 'em. It's annoying when we've got to deal with them, but it outright sucks when any 3p devs have to deal with them too.

niekvb commented 1 year ago

I experienced the same issue while having blocked MS telemetry endpoints. The app needs to phone home to activate it's license so temporarily lifting the blocked endpoints (I suspect licensing.mp.microsoft.com) should resolve the issue.

savchenko commented 8 months ago

The app needs to phone home to activate it's license

Which is an issue in itself. @zadjii-msft ?

zadjii-msft commented 8 months ago

Not... really? The Terminal is a packaged app like any other packaged app on Windows. We (the Terminal) don't do any extra validation of our license beyond what the OS / Store already do. You can of course always grab an unpackaged terminal .zip off our Releases page as an alternative.

savchenko commented 8 months ago

@zadjii-msft , thanks.

For anyone finding this via Google, Duckduckgo, etc. Have a look: https://github.com/microsoft/terminal/issues/6010#issuecomment-793771455

TL;DR - This is how modern MS Windows operates, seemingly (some?) appx packages must be verified online before installation.

On the bright side, there is a .ZIP file you can use instead. Unpack and run wt.exe.

sylveon commented 8 months ago

Yes, store signed-apps need a license to run, whether they're free or not.

Speaking of @DHowett @zadjii-msft, but is there a way for a third party store dev to also get an offline license to deploy on offline machines, like you did in the preinstallation kit? Some of my users don't have access to the MS store for business and neither do I (I'm a solo independent dev).

I would try using the appLicensing capability to avoid this (since AFAIk it should bypass the store license stuff) but people I know tried this already and their store submissions where rejected and they were told to use the store for business :\

DHowett commented 8 months ago

@savchenko You can also download the "Preinstallation Kit" from any of our release artifacts, which contains an offline license provisioning file. As of today, it's the best we can do for making sure a Terminal package install doesn't require internet access. I don't love it either.

@sylveon Watch this space (re appLicensing). We're about to go bother the Partner Center folks to make sure people don't get rejected for it. Grabbing a preinstall kit should be possible for any developer with partner center access, though... Manage packages -> Get Windows 10 Package -> Download Windows 10 Package.

If that's not available for you, then I'm all "question marks guy" meme over here.

sylveon commented 8 months ago

Yeah there doesn't seem to be a download option:

image

Gonna watch for the appLicensing stuff though 👀

daltzctr commented 4 months ago

@DHowett

Is there any update on

Watch this space (re appLicensing). We're about to go bother the Partner Center folks to make sure people don't get rejected for it.

I just submitted an app with appLicensing enabled to improve support for enterprise type scenarios (IE the above), and it got rejected saying the capability is not approved.

image