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

不能访问网络位置 #8535

Closed Jesn closed 3 years ago

Jesn commented 3 years ago

image

zadjii-msft commented 3 years ago

I rough machine translation of this title gave me "Can't access network location".

Looking through our issue tracker, I'm finding the following issues:

Which have all been closed as a duplicate of #1386. Without more info, I'm inclined to do the same with this one.

/dup #1386

ghost commented 3 years ago

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

1990chs commented 3 years ago

你解决了吗？1386爬楼爬的头疼！

1990chs commented 3 years ago

@zadjii-msft How to solve this problem, The answers in #1386 are so many and I cn't find the solution

captain-lay commented 2 years ago

@zadjii-msft How to solve this problem, The answers in #1386 are so many and I cn't find the solution you can solve it as follow：

This is a dupe and what's really need is to get the diagnostic data you can generate from Feedback Hub. It's a known issue issue and is the same on a host with no Internet with Windows Firewall enabled and Defender as the only A/V (that's still domain joined). You can work around this by changing .msixbundle to .zip and extract. Then take the relevant CascadiaPackage msix (arm/x86/x64) and change that to .zip as well. Extract it. Open the folder. You'll find WindowsTerminal.exe inside. Some things will not work as intended with this method ( you can't have it launch at log in for example) but for the most part everything works.