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

Cannot register Windows 10 device with Azure Console using Windows Terminal. #2581

Closed
plbyrd opened this issue Aug 28, 2019 · 2 comments
Closed
Labels
Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Product-Terminal The new Windows Terminal.

Comments

@plbyrd
Copy link

plbyrd commented Aug 28, 2019

Environment

OS Name:                   Microsoft Windows 10 Home Insider Preview
OS Version:                10.0.18965 N/A Build 18965
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Product ID:                00325-96577-39554-AAOEM
Original Install Date:     8/26/2019, 7:32:00 AM
System Boot Time:          8/26/2019, 8:55:52 AM
System Manufacturer:       HP
System Model:              HP ENVY x360 Convertible 15m-dr0xxx
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~1792 Mhz
BIOS Version:              Insyde F.06, 5/15/2019
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-06:00) Central Time (US & Canada)
Total Physical Memory:     7,982 MB
Available Physical Memory: 1,091 MB
Virtual Memory: Max Size:  12,168 MB
Virtual Memory: Available: 1,690 MB
Virtual Memory: In Use:    10,478 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Hotfix(s):                 2 Hotfix(s) Installed.
                           [01]: KB4517789
                           [02]: KB4517787
Network Card(s):           2 NIC(s) Installed.
                           [01]: Intel(R) Wireless-AC 9560 160MHz
                                 Connection Name: Wi-Fi
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.7
                                 [02]: fe80::60ab:5698:33b8:a6e1
                           [02]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection
                                 Status:          Media disconnected
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

  1. Open Windows Terminal 0.4.2382.0 from store.
  2. Select Azure Cloud Shell.
  3. Navigate to https://microsoft.com/devicelogin
  4. Enter code displayed in Windows Terminal

Expected behavior

Successful registration

Actual behavior

Site responds with "That code didn't work. Check the code and try again."

@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 Aug 28, 2019
@DHowett-MSFT
Copy link
Contributor

Actually, is this the same as #2588? If you make the window larger before you open an Azure session, does it work? You should get more of the code message.

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Sep 3, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Sep 3, 2019
@DHowett-MSFT DHowett-MSFT added Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels Sep 3, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Sep 3, 2019
@ghost
Copy link

ghost commented Sep 7, 2019

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

2 participants