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

clicking Launch after install complete " File System Error (12002) " #11813

Closed
AkooRedline opened this issue Nov 23, 2021 · 8 comments
Closed
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. 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

@AkooRedline
Copy link

Windows Terminal version

Microsoft.WindowsTerminalPreview_1.12.2931.0_8wekyb3d8bbwe.msixbundle

Windows build number

10.0.19043.1348

Other Software

No response

Steps to reproduce

1-modify visuale studio community 2022 added .NET desktop development
2- restart VS update ML.NET Model Builder 2022
3- install Power Shell 7.2 via windows power shell using Winget " winget install --id Microsoft.Powershell --source winget "
4- download the windows Terminal Preview from assets by clicking on it.
5- after download right click the file select install, when finnished you get Launch i clicked it and nothing happend.
closed the installation window went back to browse internet and after some time the error window popped up.
so far no pc reboot yet...i rebooted pc at this stage and tried to launch windows Terminal i see it is installed but it refuses to RUN or bugged no clue.

Expected Behavior

after rebooting pc i expected that error be gone but no.

Actual Behavior

Screenshot 2021-11-23 205833

i opend cmd and typed wt hit enter
Screenshot 2021-11-23 210957

while trying to post this issue i stumpled upon wierd behavior, first my network activity as i noticed during installation that windows terminal require access to my bandwidth connection
Screenshot 2021-11-23 213451
.

second wierd behavior is when i browse my HDD folders when i open File explorer clicking on a Drive or A folder the mouse pointer turns to undless blue circle loop cant click anywhere in file explorer window i lose control over it cant even move the window a round.

while everything else in windows normal i presume!!
someone posted last year same error but hence he didnt add anymore input about it you couldnt do much about it which is understandable..IF he only did i may not have been here posting it a year later, Thats why i will hang on to the steps i did so far waiting if you have any questions or steps i do on my end so we resolve this issue for the sake of everyone else for now and FUTURE.

@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 Nov 23, 2021
@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 Nov 23, 2021
@AkooRedline
Copy link
Author

zadjii-msft what feedback you want ?

@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 Nov 23, 2021
@zadjii-msft
Copy link
Member

12002 is ERROR_INTERNET_TIMEOUT. Is your machine connected to the internet? I'm guessing that the store is trying to validate the license for the Terminal package, and failing to do so, as described in #6010.

Can you install the Terminal from the Store directly? (not using the msixbundle)?

Can you run the Terminal unpackaged, following the steps in this comment?

#11176, #7351 are related.

@zadjii-msft
Copy link
Member

(that was weird, I swear I posted that, glad the tab was still available in recently closed tabs 😅)

@AkooRedline
Copy link
Author

AkooRedline commented Nov 23, 2021 via email

@AkooRedline
Copy link
Author

Screenshot 2021-11-24 012138

the way i installed windows terminal preview is valid as Store recognize it which adds more confusing STORE behaviour. really MR store whats your problem ?!?!?!?!

@AkooRedline
Copy link
Author

2 diffrent screenshots is Terminal installed or ready for install ??? Clicking Launch from inside microsoft store same result nothing happens and after some time the same error msg appears.
Screenshot 2021-11-24 014311
Screenshot 2021-11-24 014406

@zadjii-msft
Copy link
Member

"Windows Terminal" and "Windows Terminal Preview" are two separate apps in the store. They're each slightly different versions of the Terminal. Everything in here makes me think this is #6010. You hadn't connected to the internet yet, so the OS couldn't validate the signature of the msix when you installed it. Now that you have connected to the internet, the Store can complete the lookup, and knows that the certificate is good, and will let you launch it. The msixbundle you get from the GitHub releases page is the same thing you install from the Store - same signing, same ID, everything, but the OS still needs to make sure it's legit (since it's signed with a Microsoft cert).

@AkooRedline
Copy link
Author

Thats the confusing part... i understand all what you said but all i did was while direct connection to internet .
the store is connecting to internet EXCEPT this " completing the lookup " which is not happening .
i have the most stupid ISP, i tried vpn and clicked Launch from microsoft store AND IT LAUNCHED.
why a direct connection to microsoft store be considerd PORN policy by my ISP that needs to be partially blocked either block it entirly so i can know or whitelist it. imagin the turn of events as all this trouble coz of ISP Throttling.
Thank you Mike been alot of help i dont imagin i would think of using vpn for such thing which really un related issue and should be a problem cause not a problem solver, IF you warent involving with me in this conversation MANY THANKS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. 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

2 participants